SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well I've been in the process of trying to build kernel 2.6.16.13 for a while but when I last built it my Madwifi wouldn't co-operate, anyways! Reading some material I've read a lot about needing to make this initrd disk to boot the 2.6 kernels from if you aren't using an ext2 filesystem. However I read somewhere else that if you build in your filesystem to the kernel and not load it as a module, you don't need the initrd. I'm using reiserfs and the reason I ask is because I've tried building the initrd but I always get an error while doing the following
Code:
root@terminal:/boot# mkinitrd -c -k 2.6.16.13 -m reiserfs
WARNING: Could not find module for "reiserfs"
root@terminal:/boot#
Is this step even necessary for me as I have opted to build reiserfs into my kernel. Thanks.
I assume ReiserFS is your root filesystem? And no, if you build the FS into the kernel (not as a module) then you do not need an initrd image (at least I have never had to).
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I am not sure but I thought when you did the ' make install ' command it created the initrd file and installs to /boot as well as adding to your grub boot manager. I is possiable the make does it. I build so many kernels as long as there is no errors I just ignore what it shows. If the first couple build okay in a version level I just use the command after the xconfig. ' make ; make modules install ; make install ; make rpm '
The make rpm is for redhat distros since I have a few machines with the same setup. No need to build on each, just make an rpm and install on them and reboot.
make xconfig
make
make modules_install
make install
If the fs support is compiled into the kernel instead of as a module no initrd is needed. initrd is just a way to get the fs module loaded if it isn't already in the kernel.
compiling a kernel doesn't create an initrd image.
Not quite right, mkinitrd is then method to get a kernel to load a module early into a temporary ramdisk. Normal module loading has a chicken and eggs problem that the kernel cannot read the filesystem to load the module to read the filesystem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.