Rohit wrote:
>
> Sachin Garg wrote:
> > I think that LILO need *not* understand the Filesystem on which it is
> > installed in order to load the kernel.
>
> Let us see in yout mail...
>
> > LILO stands for LInux LOader. It is supposed to load linux or nay other
> > kernel u pass to it.
>
> Agreed. Thanks for expanding the abbreviation.
>
> > The funda is simple:
>
> How simple? Let us go ahead with the rest of the mail.
>
> > There is an MBR (Master Boot Record) on every HDD.
>
> Is this first 512 bytes of the HDD? Or something else? Binand,
> better interfere and thoda aur bol.
Each partition has a boot record of the first 512 bytes.
> > Let us say that u
> > have installed LILO on the MBR. The BIOS transfers control to the code
> > located in this portion of the HDD.
>
> That is, track 0, cylinder 0. Fine.
>
> > LILO maintains an *absolute* record of where any kernel is located.
>
> That is the catch. If LILO maintains an absolute record of the kernel
> then it needs to find out where the kernel is located. For that it
> needs kernel's name, am I right? That means it needs to read the
> filesystem
> record to find out where the kernel is sitting right now. That means it
> needs to read from that Filesystem. That would mean that LILO code
> needs to understand ReiserFS if it wishes to locate a kernel which has
> been copied on ReiserFS. Am I right?
When i meant *absolute*, I meant *absolute* i.e. CHS format. The kernel
that runs LILO needs to understand the FS, but LILO itself need not
since it has an absolute location. After all, u can't install very large
kernels, right?
sachin
-----------------------------------------------------------------------
For information on this and other Linux India mailing lists check out
http://lists.linux-india.org/
