Bug#38403: (boot-floppies: would like to have an "i _really_ mean it" option while installing lilo to logical drive)
On Mon, Apr 24, 2000 at 02:48:49AM -0000, Debian Bug Tracking System wrote:
> > dbootstrap denies installing lilo into a logical drive
> > and insists on installing it into the extended partition instead.
>
> LILO documentation supports this too. If your root file system is a
> logical partition, the fact is that lilo must be placed on the
> extended partition. Then you need a boot manager in the boot sector.
I'm sorry, but that "fact" is incorrect. LILO documentation allows for
the possibilty of installing LILO in the logical partition. Of course,
as you correctly say, a boot manager must be used in this scenario.
<quote>
"* LILO can be forced to put the boot sector on such a partition by using
the -b option or the BOOT variable. However, only few programs that
operate as master boot records support booting from a logical
partition."
</quote>
In fact, that text is wrong becuse it works fine without the -b switch.
And a bit further on in the LILO doc's:
<quote>
"One disk, Linux on a logical partition
- - - - - - - - - - - - - - - - - - -
If no primary partition is available for Linux, but at least one logical
partition of an extended partition on the first hard disk contains a Linux
file system, the LILO boot sector should be stored in the partition sector
of the extended partition and it should be booted by the original master
boot record or by a program like BOOTACTV.
+--------------------------+
| MBR /dev/hda |
| +------------------------|
| | MS-DOS /dev/hda1 |
| |------------------------|
--> | | Extended /dev/hda2 |
| | +----------------------|
| | | Linux /dev/hda5 |
| | |----------------------|
| | | ... /dev/hda6 |
+--------------------------+
Because many disk partitioning programs refuse to make an extended
partition (in our example /dev/hda2) active, you might have to use
activate, which comes with the LILO distribution.
OS/2 BootManager should be able to boot LILO boot sectors from logical
partitions. The installation on the extended partition itself is not
necessary in this case.
</quote>
> > The reason is that the standard MBR bootstrap code can't load lilo
> > from a logical drive. Some boot managers (most notably my favorite,
> > xfdisk) can indeed boot from a logical drive. So I have to manually
> > edit /target/etc/lilo.conf and re-invoke lilo to correct
> > dbootstrap's assumption.
>
> > I strongly feel that dbootstrap has a point in reminding me that I won't
> > be able to boot my system using standard mechanisms, but shouldn't
> > deny me my wish. There should be an "I mean it, really" option with
> > dbootstrap.
>
> Yes, this has been fixed. Now if rootfs is a logical partition, lilo
> goes on the extended partition, and it prompts you to install mbr for
> your boot sector.
I think you missed the point. The original submitter doesn't want LILO
in the extended partition. He wants it in the logical partition which
your current changes to dbootstrap do not allow.
I agree with the original submitter. It would be nice to allow LILO to
be installed in a logical partition, but only if you know what you are
doing. Do we have an expert mode?
Maybe this could be an option for "verbose".
Booting multiple OS's is more prevalent than ever and bootmanagers are
everywhere. The current behaviour is just making life more difficult
for some folks.
I'd like to re-open this wishlist bug.
Greg
Reply to: