Updating Lilo.conf

I want to install new kernel version 2.2.13 prior downloading the file a warning message come up " You must update your /etc/lilo.conf by hand in order to boot on your new kernel which I understand but when I try in root directory it prompt me by a denied permission msg??? Why if I'm in root directory it should'nt denied me permission

I install mandrake version 6.5 without any problems
Please help me from a newbie
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You have to be root to run lilo, not just be in the root directory. Also the new kernel has to be where /etc/lilo.conf tells lilo to look for the kernel and the file name (of the compressed kernel image) in lilo.conf has to be correct. Ownership of the kernel files probably matters also.

If everything otherwise looks okay, try running "lilo -v" and see where it complains.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dbiss111599Author Commented:
thanks, would you tell me how to be in root instead of dir
Is it a command I have to type explain thanks again
Being root means logging as root or executing "su" and supplying root's password. This gives you root priviledges on the system which is required for almost all operations that affect data outside of an ordinary user's directory.

Since the root user on a Unix machine has full authority to modify or delete anything, you don't want to be root needlessly. For instance, if you're root and cd'd to / and you accidentally execute chmod -R 755 * (thinking you are in a different directory and meaning to make all the files therein executable), you'll destroy your operating system as the command will change every file and dir on the entire system to mode 755. Unix/Linux depends on certain files have certain modes set and won't run if those modes aren't correct.

It's best to always log on as an ordinary user and become root only for a specific task that requires root privs and to return to user privs as soon as possible.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.