Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Hi: I use lilo as the boot loader. When control passes to the boot loader, I can type 'lin', the label of the OS to boot, supposedly followed by some paramenter. Suppose the lilo prompt is 'lilo ' (I do not remember well). Then
lilo lin abcd
will be accepted by lilo. I.e., it accepts anything. I've writen a valid parameter name, but with no effect at all. How do I pass the kernel a parameter at boot time?
Generally parameters not recognised are ignored and passed on. This is true of grub, and presumably lilo (which I haven't used in years).
Likewise the kernel will ignore anything passed to it if it doesn't recognise it - parameters change as kernels develop; new parameters come in, sometimes (rarely) old ones get removed.
I've writen a valid parameter name, but with no effect at all
Surely. The kernel is monolithic, but as options are compiled in they bring with them code to handle their own parameters.
If that option isn't there, the parameter isn't "valid" (as no code recognises it), and it gets ignored.
This makes sense - it is possible (common) to pass parameters to initscripts via the boot arguments; they just get ignored by everybody until the initscript processes them.