[openbeos] Re: bootloader?

> Are the BeOS boot loader (which you get from makebootable) and the Haiku boot 
> loader still interchangable? I thought we have our own boot sector now?
> 
> Could you try to check out the Haiku svn, mount your partition "Haiku" and 
> then do a "jam install-haiku"? IIRC, the jam scripts default to installing on 
> a mounted volume "Haiku". Ah, and type "configure" once before trying to run 
> jam for the first time. And of course you need to install Olivers GCC with 
> all the optional stuff (like libstdc++.r4 and headers). And you need to 
> install our version of jam. That should be it.
> 
> HTH & Best regards,
> -Stephan

I finally got around to actually compiling it this way, but I ran into this:

...skipped udp for lack of kernel.so...
...skipped 
<HaikuImage>haiku.image-copy-files-dummy-beos/system/add-ons/kernel/network/protocols
 for lack of icmp...
...skipped Haiku for lack of libbe.so...
...skipped <HaikuImage>haiku.image-copy-files-dummy-beos/system/add-ons/Screen 
Savers for lack of Haiku...
...skipped install-haiku for lack of <HaikuImage>haiku.image-init-vars...
...failed updating 3 target(s)...
...skipped 423 target(s)...
...updated 673 target(s)... 

To make matters worse, at some point, a cabinet icon has appeared on the 
desktop (the kind ImageMounter uses, I think) with no label.  When I try to 
delete it, I get:

While
Moving to Trash

The
npipe (from /)

Information:
Moving to the Trash failed!


If I try to delete it anyway, it doesn't move anywhere.  Launching it doesn't 
seem to do anything.  And I see "flock_server" running (having launched it or 
not) when I press Ctrl-Alt-Delete, which didn't used to be the case.  This may 
not have anything to do with compiling Haiku though...I can't remember exactly 
when over the last couple days this appeared.  :(  (I'm also having some 
problems with the new Multiaudio MediaAddon, so maybe monkeying around with 
that has done something.)

> In theory they should work in either combination, but I had problems with the 
> BeOS boot loader and a volume initialized by our BFS code.
> 
> Also note, that our makebootable doesn't really work on mounted partitions. 
> Well, it writes the boot code to the partition, but when the volume is 
> unmounted, BFS writes back the superblock and thus overwrites the boot block 
> with the previous version. I suppose Be's makebootable uses some private BFS 
> ioctl(). On an unmounted partition our makebootable works fine, though.
> 
> CU, Ingo

Just with the images, the way things had been working before, though, if I run 
the Haiku makebootable, when I boot, I get no boot menu like the other way, 
just a plain text message in the upper left, something to the effect of not 
being able to load the OS.  Pressing enter kicks back to the bios, which then 
kicks back to bootman.  It didn't seem to matter whether I had run it mounted 
or on /dev/disk/..., same result.

If I run the normal makebootable, the boot menu that comes up says 'Haiku' in 
different places, but looks like the R5 one, except that it finds no drives, 
not even my R5 partition, whereas R5's booting on my R5 partition finds just 
the R5 partition and not the Haiku one.

Kev

Other related posts: