[SOLVED] Generic and custom kernel work in 14.0, but I have a question about initrd.

tfrei · 10-01-2012, 04:38 PM

Feeling fancy with my new installation of Slackware 14.0, I switched to the generic kernel creating an initrd in the process and it worked. Then I created a custom kernel (following directions at http://tinyurl.com/ygyot6j ) and everything also worked. I'm curious however why the custom kernel [label= shuttle ] works without an initrd. See my lilo lines below. These lines give me a choice upon start-up: either generic or custom [label=shuttle] and both now work. Why don't I need an initrd in the second choice below?

Quote:

image = /boot/vmlinuz-generic-smp-3.2.29-smp
initrd = /boot/initrd.gz
root = /dev/sda2
label = generic
read-only
# Linux bootable partition config ends
image = /boot/vmlinuz
root = /dev/sda2
label= shuttle
read-only

vulcan59 · 10-01-2012, 05:23 PM

Presumably your custom kernel has all the device drivers and filesystems needed to boot your system compiled in. Therefore no initrd is needed.

dr.s · 10-01-2012, 06:01 PM

Quote:

Originally Posted by tfrei

...Then I created a custom kernel (following directions at http://tinyurl.com/ygyot6j ) and everything also worked. I'm curious however why the custom kernel [label= shuttle ] works without an initrd.

Assuming you closely followed the directions in that guide, the step in section D (quoted below) took care of compiling the needed filesystem module into the kernel, as Vulcan59 has stated.

Quote:

d. Compile-in your root file system
...Go back to the main menu and head down into the “File systems” submenu. Find your file system in the list and once it’s highlighted, press “y” to ensure that it’s compiled-in[*] rather than compiled as a module [m] or not compiled at all [ ]...

tfrei · 10-02-2012, 09:28 AM

Thanks Dr.S and Vulcan59. I simply didn't know enough about the purpose of an initrd and your answers helped me out. Since the file system is compiled in the kernel, there is no need for an initrd. Thanks again.