Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
When you start the computer, a "boot loader" runs to let you choose which system you want to start. If you choose Linux, the boot loader has to locate the kernel-image that needs to be brought into memory. That's "vmlinuz."
Now... why the "z?" Well, that refers obscurely to the fact that the kernel-image is compressed. The kernel-image file is first loaded into memory, then it automagically un-compresses itself.
Once the kernel-image is loaded into memory (and uncompressed), the boot loader hands-over control to it.
thanks for your reply!
when I installed virtual linux in XP,I met two files---vmlinuz &initrd.img.
what's the meaning of initrd.img?
i always think it is the bootloader in linux.
Is it true? why ? Who can explain it?
thanks!
When a "distro" writer is putting together their system, the thing they've got to figure-out is just how to make their distro "run on anything." (And, oh yeah, "make it look easy.")
So... they might need to be able to do things before Linux, itself, actually starts booting. They might need to detect hardware and load some device-drivers, for example, just so that Linux will be able to locate and access "this particular hard-drive." And so it goes.
So... what the kernel folks came up with is, believe it or not, "a virtual 'boot floppy.'" It's a tiny, absolutely-stripped-down environment that can run before Linux itself does, in a "John the Baptist sort of way," to "prepare the way for the Linux."
That's initrd. It's the one that puts up that very nice-looking splash screen, by the way, that you see during most of the time that a typical Linux-distro boots. (Wanna get technical? OS/X and Windows do it the same way, too.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.