SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
the whole idea of having the symlink vmlinuz seems unneccessary to me, to be honest. isn't it clearer and simpler to just use the name of the kernel image you want to boot in lilo.conf? does anyone know the history behind this tradition? the only time i can see it coming in useful is to have only two entries in lilo.conf like this:
image = /boot/vmlinuz-2.4.26
label = stable
image = /boot/vmlinuz
label = unstable
and then have vmlinuz point to whichever unstable kernel you feel like testing that day. it could theoretically save you the trouble of changing the lilo.conf file, but instead you have the trouble of constantly changing the symlink. also, would that even work? i seem to remember not being able to boot a new kernel after trying something like that...but it was late at night after recompiling for like the third time, so i don't know if it was due to that or not.