On Tue, 11 Aug 1998, Twylite wrote:
-> -filesystems, only sectors. Short of creating an storing a table of
-> -sectors
-> you'd have to store it in the mbr, any other place and it's likely to get
-> messed around with, besides, to write into an existing Filesystems space
-> would require : finding some free space of required size, writing to it,
-> telling the filesystem that the space is now used, and all that is filesystem
-> specific.
-
-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?
--
>> I Like England Just Fine, But I Ain't Eating Any Of That Beef <<
<< MailTo: root <at> kermit "dot" globalnet /dot\ co 'dot' uk >>
>> De Chelonian Mobile <<
