On Sun, 26 Mar 2006, Doug Koobs wrote:
>> Sorry for rambling, but I hope this has answered your current
>> questions (and a number of followup ones).
>
> Daniel & Eben,
>
> Ramble on :) Thanks for the help, I have a better understanding of what
> needs to happen. I'll read up on initrd, and see if I can get GRUB to use
> it.
In lilo it's
image=/vmlinuz
label=Linux
read-only
initrd=/initrd.img
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
initrd=/initrd.img.old
etc. Don't know how to do it in GRUB, but if you google on |grub.conf initrd|
you'll find out how it's done.
> I'm not sure how this all works, though... The system needs to have the
> module loaded to access the drive, yet it needs to access the drive to
> load the module. Regardless of whether the module is built into the
> kernel, or loaded dynamically, it's still on the drive, which can't be
> accessed until the module or kernel is loaded... Even if initrd puts the
> module in memory, wouldn't it have to access the drive to get the module?
> Maybe there is some magic in the boot loader I don't yet understand.
For the kernel, I think a minimal driver (maybe just a BIOS subroutine
number) and block number is stored in the bootloader. Maybe the same is
done for an initrd.
-- The powers in charge keep us in a continuous stampede of patriotic fervor with the cry of national emergency. Always there has been some terrible evil to gobble us up if we did not furnish the exorbitant sums demanded. Yet, in retro- spect, these disasters seem never to have been quite real. -- Gen. D. MacArthur ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:05:51 EDT