Choosing a kernel for Slackware 12 and is an initrd needed?
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.
Note that there's really no reason to leave the non-smp kernels available for most people; I only do that for testing purposes.
Also notice that I use the same initrd.gz file for both the smp and non-smp generic kernels; if you don't pass the -c switch to the second run of mkinitrd, it will add the non-smp modules to the existing initrd tree and recreate it. In other words, you can have support for as many different generic kernels as you'd like in one initrd.
Last edited by rworkman; 01-05-2008 at 02:05 AM.
Reason: Added info
Thanks for the advice folks. First of all, my vmlinuz was pointing to the generic SMP kernel, and it was booting. So, the JFS file system must be compiled in the kernel. There's no other explanation that I can find.
However, I did create an initrd and point it to the generic SMP kernel. So now I'm doing it correctly, even if it was accidentally working before.
Lufbery, I never saw where you posted your lilo.conf? Would it make sense to see your ftsab file also. I think that will tell us what your root file systems is formated as, ext3 or JFS.
On the topic of the generic vs huge kernels, I'm curious if anyone get's a peformance boost from the generic kernel? I know loading only the needed modules saves memory, but does it really matter in this case?
I finally got around to installing the new hard drive in my laptop and installing Slackware 12 on it. So far, I've got just two questions.
First, did I change kernels correctly? -- I've read here, and in the readmes the recommendation to use the generic SMP kernel for day-to-day operations. I did a full installation and the default kernel is the huge smp kernel. So, I went to the boot directory and changed the System.map, bzImage, and config symbolic links to link to the corresponding generic SMP files. The laptop boots correctly and everything seems to work, but is there anything else I need to do?
Second, why would I need to make an initrd? The ANNOUNCE.12_0 file states:
But I'm using the generic kernel and haven't made an initrd yet. Why is it necessary? Aren't modules loaded with rc.M?