On Mon, 20 Dec 2004, Dan Kaspi wrote:
> >The bootloader loads the initrd file from disk to memory so it knows
> >exactly where it starts and it knows the end of it which is the start
> >address + size of file. The boot loader puts this information into PARAM
> >block which is a block
> >of memory
AIL PROTECTED]>
To: guy keren <[EMAIL PROTECTED]>
CC: Dan Kaspi <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Initrd entry in grub.conf and loading initrd in the kernel
code
Date: Fri, 17 Dec 2004 10:09:54 +0200
4. the question that remans - how does the boot loader know where to fin
4. the question that remans - how does the boot loader know where to find
initrd_start and initrd_end? does it look their location directly in the
kernel's elf file and updates their contents? naah... this is done in the
architecture-specific code (e.g. for i386, in arch/i386/kernel/setup.c -
look
On Wed, 15 Dec 2004, Dan Kaspi wrote:
> I tried to understand the correlarion between initrd in grub.conf and the
> call to initrd_load() in the kernel (under init subtree).
> My question is : when we do not use initrd in grub (meaning there is no
> entry for initrd in grub.conf), does the kernel
Hello,
I tried to understand the correlarion between initrd in grub.conf and the
call to initrd_load() in the kernel (under init subtree).
My question is : when we do not use initrd in grub (meaning there is no
entry for initrd in grub.conf), does the kernel still calls load_initrd()?
Or does it se
