Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 01-08-2004, 04:36 PM   #1
Registered: Sep 2003
Location: Sydney
Distribution: Debian
Posts: 70

Rep: Reputation: 15
mkinitrd doesnt exist in slackware? Newbie kernel compile question!

I am just going about recompiling my 2.4.22 kernel and I just done a "make bzImage"
I have changed my EXTRAVERSION to -09Jan so that when I do a "make modules" the modules will be compiled to /lib/modules/2.4.22-09Jan (right?) Then once I am done I am supposed to to a "mkinitrd" to generate the initrd-2.4.22-09Jan.img file that I should put in LILO.

Well, thats what I was supposed to do in RedHat! But there is not a mkinitrd command in my slackware install. How do I tell LILO which modules version to use?

I did follow the guide in this forum, which did work, but I like the idea of having to copy all the files to the /boot directory etc yourself.

Old 01-08-2004, 04:58 PM   #2
Registered: Dec 2003
Location: Layer 7 =D
Distribution: Slackware, LFS, Rock Linux
Posts: 165

Rep: Reputation: 30
although there _is a_ kernel compile guide at the very top of this nice forum...

compile your kernel and modules ->
cd /usr/src/linux/
make dep clean bzImage modules modules_install

install your kernel image ->
cp /boot/
cat arch/i386/boot/bzImage > /boot/vmlinuz

update lilo ->

no, to my knowlege make modules won't copy you're modules to /lib/modules/<version> ...
thats what make modules_install does...
your system knows what kernel to use from the lilo.conf ->
image = /boot/vmlinuz
  root = /dev/hda1
  label = slack
your kernel knows it's version and of course which modules to load if I'm not wrong....
and by the way....I would use 2.4.24 since 2.4.22 and 2.4.23 have some serious security flaws ->

Last edited by poison; 01-08-2004 at 05:16 PM.
Old 01-08-2004, 05:56 PM   #3
Registered: Nov 2003
Distribution: slackware 14
Posts: 542

Rep: Reputation: 33
Initrd image is not necessary unless you have some hardware for which you compiled the drivers as modules that must be used at boot.
ie you have a scsi hard disk on which you have your operating system installed and you have compiled the scsi drivers as modules, and of course they are not available at boot.
Slackware doesn't provide any automatic "generator" of initrd images.
You must set them up manually and trust me .... is a mess.
I had a list of the necessary files to set up an initrd image on Slack but I can't find it at the moment.
I will post it as soon as I catch it. (may be tomorrow if I can)
Old 01-08-2004, 06:22 PM   #4
Registered: Sep 2003
Location: Sydney
Distribution: Debian
Posts: 70

Original Poster
Rep: Reputation: 15
Cool - I didnt really know what initrd.img file was! I dont think I need to worry about that then!



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
tun interface does not exist in slackware 10.1 with kernel antken Linux - Networking 1 05-29-2005 09:10 PM
kernel 2.6.8 compile error mkinitrd failed mcalizo Linux - Software 0 11-30-2004 01:58 AM
mkinitrd kernel-related question Tino27 Slackware 1 03-26-2004 11:14 PM
MLDonkey_gui doesnt exist fedivh Linux - Software 34 02-07-2004 04:40 PM
mkinitrd problem - kernel upgrade newbie irvken Linux - Newbie 31 12-23-2003 12:03 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:59 AM.

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