LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-01-2012, 04:38 PM   #1
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Rep: Reputation: 16
Generic and custom kernel work in 14.0, but I have a question about initrd.


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
 
Old 10-01-2012, 05:23 PM   #2
vulcan59
Member
 
Registered: Sep 2007
Location: UK
Distribution: Slackware 13.37 & 14.0
Posts: 71

Rep: Reputation: 24
Presumably your custom kernel has all the device drivers and filesystems needed to boot your system compiled in. Therefore no initrd is needed.
 
Old 10-01-2012, 06:01 PM   #3
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 126

Rep: Reputation: 19
Quote:
Originally Posted by tfrei View Post
...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 [ ]...
 
Old 10-02-2012, 09:28 AM   #4
tfrei
Member
 
Registered: Dec 2004
Location: Fargo
Distribution: slackware 13.37
Posts: 63

Original Poster
Rep: Reputation: 16
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] initrd / generic kernel --> won't boot. What am I forgetting? chexmix Slackware 6 09-30-2012 02:43 PM
[SOLVED] setting up initrd / generic kernel in Grub2...can't load generic Ubunoob001 Slackware 8 01-05-2011 11:37 PM
[SOLVED] initrd and generic kernel fails to boot with errors after using mkinitrd generator adamschock Slackware 8 06-26-2010 02:30 PM
Generic kernel + initrd not working rpedrica Slackware 12 06-22-2010 10:17 AM
Generic SMP kernel with no initrd? songangel Slackware 8 03-26-2009 06:12 PM


All times are GMT -5. The time now is 05:41 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration