As described in my post at http://haiku-os.org/documents/dev/installing_haiku_to_a_partition_from_linux, I installed Haiku on my SATA HD (it boots only in RAID mode). It runs fine, but, as I expected, it does not see my DVD drive and my Ethernet card, since their drivers are not in the supported list. Unfortunately, it does not see my other partitions either (I have fat32, ntfs, ext2 and ext3 partitions). Is there any tools or workaround out there to open a window for Haiku?
Thanks in advance for any feedback.
The DVD drive should work - you probably have to have the disc in it before you start up Haiku though since I believe it can only mount volumes that are present at boot time (this is a current limitation). I think only ISO9660 discs current work, not UDF - but I could be mistaken.
As for the ethernet, what chipset do you have? what’s the vendorid/deviceid? (you can get this by running listdev)
I don’t think any of the other partition formats you mentioned are yet working in Haiku. There is a “fat” filesystem driver, but I’m not sure it works properly yet. You may have to try mounting it manually from a commandline.
Keep in mind that Haiku is far from complete - expect disappointment at this stage
The same here I’m going to burn a CD with drivers from BeBits…
But how can I store my settings to reset them after a “svn and make” update?
If you are installing it to a native partition using the “install-haiku” jam target, it will not erase the drive, it will simply refresh all the targets. Since the settings files are generally additional files, they usually remain on the partition.
I can’t figure out how to exactly do this
I followed Getting Linux Developer Tools to get the developer tools, and then Installing Haiku to a partition from Linux. At the moment, I just do a svn-update and then jam -q. What do I have to change?
Thank you for your help!
Ok, so you’re actually generating an image directly to a partition using Linux… that’s different. For some reason I was expecting you to be using BeOS R5 or Zeta (my mistake).
There’s an “update-image” target also IIRC, which just mounts the existing image and updates it.
I’m not entirely sure on the usage, but I think there’s also a setting in the UserBuildConfig to tell the build system to not re-create the entire image each time… you’ll probably have to do some investigation as I’m not as familiar with building the image on Linux as I am on BeOS.