Hi,
Sachin Garg typed:
> 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?
Does LILO load vmlinuz at the start? Or some other smaller file first?
Because I was wondering - when the kernel file (say 500 KB) is
fragmented in the filesystem, how does LILO load it? In this case it
has to understand the filesystem, isn't it? But /usr/doc/lilo/README
clearly says:
LILO does not know how to read a file system. Instead, the map
installer asks the kernel for the physical location of files (e.g. the
kernel image(s)) and records that information. This allows LILO to
work with most file systems that are supported by Linux.
So how does it deal with a fragmented kernel? Does linux have any way
of ensuring that the kernel remains unfragmented?
--
Mrinal Kalakrishnan <[EMAIL PROTECTED]> http://mrinal.dhs.org/
Linux 2.2.16 || PGP:B1E86F5B || Mutt 1.3.4i (2000-06-19) || VIM 5.6
--
"What you end up with, after running an operating system concept through
these many marketing coffee filters, is something not unlike plain hot
water."
(By Matt Welsh)
-----------------------------------------------------------------------
Check out the 'What to do before posting to the list' site
for a list of things to try before posting. The site is
at http://botsie.tripod.com/beforeposting/
