boot haiku natively

From Linux, there are two steps involved.

1) You 'dd' haiku image to a partition
2) You run 'makebootable' on that partition

Search for 'makebootable' in these forum posts for further details:
http://www.haiku-os.org/documents/dev/installing_haiku_to_a_partition_fr...
http://www.haiku-os.org/community/forum/tired_of_running_haiku_under_vms

Yep, dd to the entire disk *should* work (although, I've seen it fail on a couple occasions as well).

The raw images are basically just full disk image with no partition map on them - so the offset in the boot block to the physical location where the partition starts is known and always correct when used this way, and the boot block of the partition lands in the MBR.

If you dd the raw image to a single partition anywhere on a disk, you'll need to change this offset and also add your own chainloading bootloader into the MBR (the GRUB info tonestone57 provided is basically what I use here as well).

Generally, the easiest way I've found to install Haiku to a partition is to simply setup a build environment on Linux (32bit preferably) and just build your images directly to the partition.

Instructions to do that are available:

I recommend the following articles - once you've completed and succeeded with the first one, then you can move onto the second one. Both should have a healthy number of related comments you can peruse as well:

http://www.haiku-os.org/documents/dev/building_haiku_on_ubuntu_linux_ste...

http://www.haiku-os.org/documents/dev/installing_haiku_to_a_partition_fr...

Ok richard - good one. I thought you could do it in Qemu but wasn't sure how. Now I know but I'll give a little better explanation because yours has little details ( hard to follow ).

This is an easy way to run makebootable inside Qemu on Linux with Haiku image.

Download haiku.image.bz2, unzip it.
Run: qemu -hda haiku.image.r26269 -hdb /dev/hda

haiku.image.r26269 should refer to the actual Haiku version you're using
/dev/hda should be the drive with the Haiku partition

Qemu will run haiku.image.r26269. You'll be able to mount your physical Haiku partition inside of Qemu.

Use Haiku's menu & mount physical Haiku partition in Qemu.

In terminal, run makebootable on your physical Haiku partition.

makebootable -full /haiku

/haiku should refer to your mounted physical Haiku partition ( yours may be named differently )

Now you should be able to boot the Haiku partition with Grub ( or NT loader ) and run the OS natively.

I use "makebootable -full" in BeOS but I believe -full switch is ignored in Haiku.

In terminal, "cd /", then "ls"
mount your physical haiku partition with the menu

in terminal, type "ls" again in /; you'll see a new directory that wasn't there before - your mounted partition.

BeOS & Haiku mount disk partitions in /

So when I run Qemu & mount Haiku & BeOS partitions I have /Haiku (haiku image), /haiku (disk partition 3), /BeOS (disk partition 1).

To make partition 3 bootable, I'd type:
makebootable /haiku
For partition 1, I'd type:
makebootable /BeOS

Yes, those applications in Senryu were made for BeOS. Senryu lets you see many of the programs available for Haiku without having to download them off of Bebits or look around at other sites to find them.

Richard, syntax is: makebootable /"haiku_partition_you_mounted"

You said, that you ran " makebootable -full / "
That won't work - different from what I said. You must mount the drive partition where you dd'ed the image to; the partition will mount in / but will have a *name*; my Haiku mounts as /haiku but yours might have another name.

1) dd haiku image to a partition.
2) In Linux, do what I said above with Qemu
3) mount the haiku partition ( you dd'ed to )
4) run makebootable /"mounted_partition_name"

You'll see the mounted_partition_name in / if you do a "ls" before and after mounting the partition. You'll have a new folder added for the mounted partition.

Yes, I have BeOS & Haiku on drive partitions. It isn't booting BeOS or Haiku from drive because I have Grub installed so I'd know & newer Haiku is booting up which I only have as image file. So, I'm certain haiku image file is booting. I haven't tested out Haiku's makebootable to see if that works ( it should ).

The method I described above allows you to boot from haiku image file. hda = haiku image ( boot drive ), hdb = physical disk drive. This will let you mount your physical haiku partition and run makebootable.

makebootable -full /dev/disk/0/ata/slave/raw
is not right because you're not selecting a specific partition - I'll explain in a bit. I have 7 partitions on /dev/hda.

So, I decided to try it out myself and see what happens. What I did:
1) dd if=haiku.image.r26269 of=/dev/hda2
2) qemu /dev/hda; tried to boot /hda2 with Grub & got message Failed to load OS ( good b/c I wanted to be sure it wouldn't boot )
3) qemu -hda haiku.image.r26269 -hdb /dev/hda
4) Mounted haiku partition from menu - it mounted as /Haiku1
5) makebootable /Haiku1 ; resulted in:
Error: Failed to open my executable file ("makebootable": No such file or directory
6) cd /dev/disk/ata/0/slave
7) ls ; see there are 7 partitions
8) makebootable /dev/disk/ata/0/slave/1 ; gives same error as in 5 - also tried with a different partition ...../2 but again with the error.
9) Mount my BeOS partition. cd to beos/bin & try with BeOS makebootable ( /Haiku1 ) - I get error:
Cannot find the BIOS drive id for:
/dev/disk/ata/0/slave/1

makebootable: error writing boot block information to /dev/disk/ata/0/slave/1 ; I also tried with ..../2 but had same error

Conclusion: makebootable is not able to work in Qemu

Sorry about that. I thought it would work but after testing this method out myself it looks like it doesn't. So it seems that makebootable will only work from BeOS LiveCD or partition ( or Zeta LiveCD may work too depending if they left mount & makebootable intact ).

@cb88
I have to choose -hda haiku.image because Qemu boots from -hda. Might be a way to change it to boot from -hdb.

I believe makebootable doesn't work because it can't figure out the drive's geometry in Qemu.

@richard

I couldn't see your pictures. Are the links correct? Do they work for you?

dd'ing to a partition or drive is no good b/c you're limited to size of Haiku image ( 250 MB ) even if partition is 10, 20, 50 GB, etc.

I always use BeOS to mount the Haiku image file, copy over the files/folders to the BFS partition. This is easier and gives me full access to the entire partition size.

Zeta LiveCD should work. All you really need is mkdir, mount, makebootable & DriveSetup.

Ok, figured it out. In your previous post you stated they were named image1-7.tiff when they're actually 1-7.tiff ( no image in the name ).
WRONG:
http://www.rjasmin.net/haiku/image1.tiff
http://www.rjasmin.net/haiku/image2.tiff

RIGHT
http://www.rjasmin.net/haiku/1.tiff

I'm going to look through the tiffs b/c I'm curious what you were getting.

For boot manager type "bootman" at command prompt. That'll allow you to install it.

You can change the language to English in the LiveCD if you go to Preferences. Can't remember what it's called.

Here is an Idea if you want to boot it native on a standalone system and not a duel boot with any other loaders then the one haiku has.

Add it to a BartPE setup with Roadkils disk image http://www.roadkil.net/program.php?ProgramID=12 as plugin there is one out there and then have the raw disk image used by that disk to add it to current disk and then reboot and it works.

There will surely be a bootable CD once the alpha stage is reached.
The developers want that the people have a first good impression with the first release.
Even if we're close to the alpha, it would be a bad idea to have an official release which leave a bad impression to normal users.