Opened 10 years ago

Closed 10 years ago

#3778 closed enhancement (invalid)

Bootstrapping Haiku from BeOS now requires a boot floppy image

Reported by: haiqu Owned by: haiku-web
Priority: normal Milestone: R1
Component: Website Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

Since the change of tree structure and renaming of zbeos to haiku_loader, the makebootable utility in BeOS is no longer adequate for bootstrapping a new system.

We need a Haiku boot floppy image with the new makebootable utility to be made available on the website.

Change History (9)

comment:1 by haiqu, 10 years ago

Alternative solutions:

  1. A BeOS utility which scans for the name "haiku_loader".
  2. Explicit and detailed instructions on how to modify the sources to change the name back to "zbeos" temporarily for the initial build.

comment:2 by stippi, 10 years ago

You just have to build the Haiku "makebootable" tool from the Haiku sources. I leave this bug open since, it's really about the website instructions.

comment:3 by mmadia, 10 years ago

In my limited attempts to do so, makebootable failed to build on Haiku, even with just a plain old 'jam -a' invocation. Though, I didn't bother trying to find the error message. iirc, jam makebootable did not work.

comment:4 by umccullough, 10 years ago

You could also theoretically just dd the first block from a raw haiku image to the beginning of your partition, and then use makebootabletiny (for beos) to change the partition offset.

comment:5 by mmlr, 10 years ago

The correct way to do this is to use the build platform built makebootable using the jam run target like this:

jam run ":<build>makebootable" /dev/disk/path/to/partition

This works under Haiku and should also work under BeOS.

comment:6 by haiqu, 10 years ago

That assumes you can create a Haiku makebootable that runs in BeOS.

The other way of course is to download the latest .iso image and install from there, once the installer app is working. The trouble with that idea is that ALL the links on BeBits to copies of cdrecord/mkisofs are broken, which is why I downloaded the latest sources and started building it a few days ago.

comment:7 by haiqu, 10 years ago

FYI I tried building and using makebootabletiny from BeOS and the partition didn't boot. It's still looking for the wrong file and in the wrong location. If I'd built it from Haiku it probably would have worked, but this report is about bootstrapping into a new system so that option wouldn't be available.

in reply to:  7 comment:8 by umccullough, 10 years ago

Replying to haiqu:

FYI I tried building and using makebootabletiny from BeOS and the partition didn't boot. It's still looking for the wrong file and in the wrong location. If I'd built it from Haiku it probably would have worked, but this report is about bootstrapping into a new system so that option wouldn't be available.

makebootabletiny does nothing more than change the partition offset - it doesn't set the path, which is why I suggested dd'ing the entire first block of a haiku IMAGE to your partition and then running makebootabletiny on it...but anyhow, i'm sure you'll find more creative ways.

comment:9 by nielx, 10 years ago

Resolution: invalid
Status: newclosed

Closing as there has not been activity for six months. Furthermore, http://www.haiku-os.org/guides doesn't seem to mention building from BeOS at all, so this discussion/issue doesn't seem to be relevant.

Please reopen if you think otherwise.

Note: See TracTickets for help on using tickets.