I wrote: > IMHO putting critical boot software in an "unallocated" area that > other software will (not unreasonably) assume contains nothing > important is a loony idea.
Arno Schuring writes: > It's not any more loony than hardcoding the disk sectors in which the > kernel file resides. Like Grub, Lilo hardcodes the location at which it's next stage code resides in the MBR. However, it puts that code in the Linux file system rather than in the "gap". The MBR boot code _must_ use BIOS calls and a hardcoded disk location: there isn't room for anything else. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762gdvt0u....@thumper.dhh.gt.org
