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.
would it be feasible to set up my initrd to load all modules used by my system - at least all the modules loaded needed for the single-user section, before going multi-user?
I've done some google-work on the subject of initrd, but everyone seems to take two routes: just the bare minimum needed to mount the root filesystem, or use it as the root filesystem. I don't see anything related to what I want to accomplish.
all input is greatly appreciated.
Click here to see the post LQ members have rated as the most helpful post in this thread.
I want to have the Init Ramdisk load all modules, then mount the root partition, and run startup scripts.
My old Computer Science teacher used to regularly terrorise his students with a question, and now I'm going to ask it to you: Why?
I'm not trying to discourage you. If you want to scratch that itch then by all means go for it, that's what linux is all about, but if you can't answer "why?" any other way than "because I want to" then that might explain why you don't find anyone else doing it that way. I suspect anyone who wanted those kernel features ready from the get-go would just configure the kernel to have them as built-ins and avoid the need to muck about with modules and initrds completely.
"have the Init Ramdisk load all modules, then mount the root partition" This is exactly what happens with the standard boot-initrd -except for the 'all' part. But, I think it will load all the modules that you put in the initrd. The real 'root' gets mounted after the initrd finishes.
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
practical? probably not
1) the other modules aren't necessary until AFTER the initrd is done
2) i believe the modules loaded by initrd are eventually unloaded and replaced by the version on the drive anyways (could be wrong so don't quote me on this)
3) it's probably more trouble than it's worth
4) if I'm not mistaken, initrd is to some extent optional nowadays if the necessary drivers for initial boot are compiled as built-in.
you should use a stopwatch to check the boot speed before you use this initrd and after, also check the amount of RAM being used while idle. Id be interested if this would have any bearing on performance or memory usage. Also, at least for me, it would make more sense just to build all these modules into your kernel, particularly your filesystem. It seems like a cleaner option.