Opened 17 years ago
Closed 17 years ago
#1289 closed enhancement (fixed)
Haiku does not yet have 'bootman".
Reported by: | bouncer | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I run my Haiku from a physical installation. Booting it on real hardware. It has been several months now - and I want to boot the other OS I have installed on this same disk.
In order to get it working - I need to re-install the "bootman". And therein lies my problem. a) It seems that Haiku does not yet have its own 'bootman' (or equiv). b) If run from BeOS, 'bootman' refuses to access the 'Haiku' disk. c) If I start up Haiku - and attempt to run BeOS's 'bootman' binary - it puts out the following error message on the terminal.
/ROOT/beos/bin>bootman elf_resolve symbol 'VolumeNameC9Partition' resolve symbol "VolumeNameC9Partition" returned: -2147478780 runtime_loader: troubles relocating: 0x80001304 (image: bootman) /ROOT/beos/bin>
I realize that everyone is busy. And has lots of other things to work on. So - I am definatly not demanding an instant resolution.
But I would appreciate a word on whether something like 'bootman' is in the works. And if it is not to be, what the thinking for a substitute might be.
AFAIK there's no boot loader for Haiku in the works, ATM. The BeOS bootman won't work under Haiku, since it seems to use a private API, that we won't provide.
Apart from that, every other boot manager -- including BeOS' bootman -- should be able to boot Haiku (via chain loading), if the partition has been made bootable correctly (via makebootable -- in doubt use Haiku's version).