Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
hm, initrd is part of lilo I believe, did you deleate old one?
if by vmlinux you are refering to kernel image it is in:
/usr/src/linux[or path to kernel source dir]/arch/i386/boot/bzImage that is usually copied to /boot/vmlinuz
oh, initrd is not part of lilo, it stands for initial root disk and contains some config info for booting. it isnt really needed and in gentoo if you compile your own kernel you wont make one (it even tell you that you will leave the initrd line out of the <brand-name>.conf file (where brand-name is lilo or grub).
so basically, you SHOULDNT need one but i dont know much about the 2.6 kernel.
The last part [2.6-xxx] refers to /lib/modules/2.6-xxx dir.
The mkinitrd is located in /sbin or /usr/sbin dir [which one?].
But as far as I know the kernel compilation for 2.6 has some command to install all those files (initrd, vmlinuz and the other one [I can't check it now since I'm using windows on public computer]) in the /boot dir.
But the way to make initrd that described above is for 2.4. Is it the same as for 2.6?
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
hmm, i'm not sure how to make initrd images, i usually end up doing without them, i'm not sure they're required in fact they support for initial ram disks can even be compiled out of the kernel. as for vmlinuz files, that's done by recompiling the kernel
<Oh! arent initrd images the splash screen ? like in suse/redhat where it has a background image for lilo?>
Nope - INITial RamDisk. I think the original point of them was that, when booting linux, the filesystems were first mounted read-only, so the initial ram disk provides a file system where temporary files can be written to, until the filesystems are remounted as read/write.
They don't seem always to be necessary; I've compiled kernels and used them without OK, although I tend to use them by default because Mandrake uses them and, if I compile a kernel and do "make install," it creates an initrd image automatically and tells lilo to use it.