Installer installs bootman automatically when it should not, corrupting install.
|Reported by:||agildehaus||Owned by:||korli|
|Has a Patch:||no||Platform:||All|
DriveSetup has the capability of creating a Haiku volume without using an Intel partition map. You can make the entire drive a Haiku volume.
In fact, I was not aware it could. I thought when selecting the drive and using the menus Partition > Initialize > Be File System that I was creating an Intel partition map on that drive with the first partition taking up the entire space. Unsure if this is a usability issue or just me, but I digress.
Should you wind up creating a Haiku volume spanning the entire drive with no partition map, Haiku will happily install to it. This is fine. What's not fine is that Installer will happily install the boot manager to the drive, automatically, at the end of the file copy procedure. This corrupts the volume.
Rebooting I am presented with a boot manager that sees no Haiku volumes.