[openbeos] Re: *don't hurt me* jam'ing to partitions...

On 2007-03-30 at 00:36:50 [+0200], Steven Hoefel <stevenhoefel@xxxxxxxxxxx> 
wrote:
> Guys, I know this had been spoken about over and over...
>  
> I've been trying to get a 'stable' development environment for Haiku for 
> around a month now... failing miserably.
> First it was on my Fujitsu LOOX (Crusoe 533mhz + 112mb RAM) and that failed 
> on compile under BeOSMAXv3* due to ram limitations.
> Second was an install of Gentoo on my P2.4D... the compile failed under 
> linux and I couldn't work out what the hell was going down... now that I 
> think of it, it was probably GCC being an incorrect version, etc... I might 
> check that out again...

If following ReadMe and ReadMe.cross-compile doesn't help, drop us a mail 
with what exactly goes wrong (ideally with the produced output).

> Third, I managed to install BeOSMAXv4b1 on the P2.4D, through magical bios 
> settings and adding an IDE 10g drive since SATA wasn't an option (disk > 
> 160gb)... anyway... compile finished this morning, have a 1gb partition on 
> this disk for Haiku... attempted:
> HAIKU_INSTALL_DIR=/dev/disk/ide/ata/0/slave/0_1 jam haiku_image
> ...Said that it had written all sorts of stuff to the disk, no errors... 
> but no luck... the partition still mounted fine and I had the usual 'Trash' 
> folder (from when I first initialised it when installed BeOSMAX). ... And I 
> hadn't seemed to have trashed any other partition?
>  
> ...Anyway, my question is: What is the correct syntax for jam'ing Haiku 
> direct to a partition on BeOSMAXv4b1. It's the second partition on 
> IDE:0:SLAVE.

HAIKU_INSTALL_DIR has no effect for target "haiku_image" (or "haiku-image"). 
You would want to decompose the path and set HAIKU_IMAGE_DIR 
("/dev/disk/ide/ata/0/slave") and HAIKU_IMAGE_NAME ("0_1") which would do the 
trick. I've never tested it under BeOS, I think. A drawback is that the BeOS 
volume will only be as big as specified by HAIKU_IMAGE_SIZE (100 MB). 
Increasing the value will help, but will also take longer, since the build 
script zeros out the image.

A more efficient way in your case is to install Haiku into a directory. You 
use the target "install-haiku" (instead of "haiku-image") and set 
HAIKU_INSTALL_DIR to the root directory of your mounted Haiku partition 
("/Haiku" or whatever). Use makebootable to make the partition bootable (once 
after formatting suffices).

CU, Ingo

Other related posts: