James wrote:
> -Not exactly: Lilo and many other boot managers use the same system. You have
> -a minimal bootstrap code in the MBR (its all you can really house there), and
> -a map file somewhere on the disk. From an OS (in this case Linux) you run
> -the install which creates the map file, writes it to a file in the Linux (or
> -whatever OS) filesystem, and then determines the absolute starting sector of
> -the file. Next it makes sure that the file is contiguous, otherwise the
> -install must fail. Now as long as you don't delete that file or run
> -something like a defrag on the disk, you're fine. If you *do*, you're in trouble
> -...
>
> where is this file in Linux? Is it the kernel image itself, which is why
> you have to re-run Lilo every time you compile a new kernel, even though
> the filename is the same?
According to the lilo(8) and lilo.conf(5) manpages, it's /boot/map.
You have to re-run lilo so that it can create the map file and the
boot loader.
--
Glynn Clements <[EMAIL PROTECTED]>
