Robert P. J. Day wrote:
i'm sure i'm going to regret asking this only seconds after i hit
Probably, a little later than a few seconds:-)
ENTER, but at what point during the boot process does the kernel's
corresponding /boot/initrd.img file kick in and get used?
i'm following along reading the logic of initramfs and early
userspace, and can see where a compressed cpio archive can be
incorporated into the kernel image itself. fair enough.
but how does the /boot/initrd.img (which is itself a compressed cpio
image) get processed during boot? it's certainly not passed as an
argument to the kernel as i can see via /proc/cmdline. so how does it
affect the boot sequence? thanks.
What interprets these?
title Scientific Linux SL (2.6.18-8.1.15.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-8.1.15.el5
module /vmlinuz-2.6.18-8.1.15.el5xen ro
root=/dev/VolGroup00/LogVol00
module /initrd-2.6.18-8.1.15.el5xen.img
savedefault
The bootloader loads it, of course. That's how multiboot works.
For the grubby details, you'll need to read the kernel and/or bootloads
source.
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
