To view parent comment, click here.
To read all comments associated with this story, please click here.
Fair enough. I'd really like to see more sites (including Haiku's) start using OpenID for this type of stuff - then no matter where you go, you just authenticate with your single OpenID from <insert_preferred_openid_provider> and not worry about registering everywhere.
Still, please understand that it's in the interest of everyone to report any issues you have and help the Haiku project volunteers to help make it better for testers and end users.
Don't get me wrong - I fully agree with you. The problem is simply that Haiku LiveCDs currently suck, and provide a somewhat disappointing experience. I didn't even mention above that hardware support is still an issue. Sometimes the kernel/drivers simply can't find the CD/BFS image and die in the middle of booting. There are still problems where SATA controllers screw up the original IDE driver, and there's a new IDE driver in the works (ata) but it doesn't have ATAPI support yet and only works in PIO mode still.
Thus, long story short (too late?) - Haiku isn't ready to be distributed via LiveCD yet.
I would strongly advise AGAINST running Haiku on any system which currently has any existing partition.
I made the mistake of creating a Haiku partition and building an install onto it.
Any other BFS partition I accessed ( I have four hard drives, all with BFS partitions ( 7 total ) ) had to be recovered very carefully.
Haiku could read the data fine, but BeOS could not. So I spent a week with a very buggy Haiku install creating ISOs & zip files of the data I needed, and copying them to a FAT32 partitioned hard drive.
Once I was done with that, I thought I was done, but no!
Not only did I need to recreate the file systems and structures manually ( because the BFS recover tool couldn't do it ), I had to remove every BFS image which was opened within Haiku, create numerous PhOS installs, and wipe out any file system which had come into contact with the Haiku-tainted BFS.
Of course, I guess I could have just re-imaged my drives from backup, but where is the lesson in that? :-)
I still cannot figure out how the problems actually arose. The superblocks were clean, and I regenerated new ones to be certain.
I used my advanced partitioning software to manually edit the partition tables, and I even ran sanity checks through the "corrupted" structures.
The best I can come up with has to do with incompatible "btrees" which were used to describe the contents on the partition. That would explain why BFS recover couldn't handle the task.
The oddity was that Haiku could access EVERYTHING just fine, but SkyOS's "BFS Viewer for Windows" could only read those which Haiku had tainted excepting a few which were beyond its capabilities anyway ( the program cannot properly access some partitions due to a some unintentional limitation ).
Oh well, next time I'll use one drive in the system with four BFS partitions, a PhOS install on two of them, a Scratch partition for testing, and of course the Haiku partition pre-made.
If all goes well I may re-consider keeping a more live copy on the actual machine.
Post in short:
Don't use Haiku on raw hardware unless your prepared and knowledgeable enough to manually recover your system in the event a bug occurs ( this is a standard caveat anyway, but most never pay any real attention ).
--The loon
BTW, I just discovered about a week ago ( now about 6 months after all this ) that I had to destroy the original partition on which Haiku was installed because PhOS/BeOS was messing up because of it ( I was blaming the issues on my hardware changes ).
So now, the system is finally proper again. My next move is to install MacOS X :-) If it ever finishes downloading... ( I am willing to buy MacOS X, BTW, if I can get it to work. EULAs have no legal bearing, and I'm legally allowed to do whatever I choose to make it work on my system, so all is good. :-) )
EDIT: forgot to actually type some words here and there.
Edited 2008-04-19 02:27 UTC
Would much prefer an image of Haiku that could be run off a bootable flash thumb drive. Bootable CD's really do not do any OS they present any favours as the data transfer capabilities are lack luster.
Much prefer a flash thumb drive version which would
1. be fast and
2. allow for read and write capabilities for the OS.
A 2Gig flash thumb drive would suit a Haiku install nicely with room to spare for playing around and doing things with the OS. It also would show the real wow factor of the OS with regards to responsiveness.
Waiting patiently for Haiku to arise and the VMWare Imge, although working ok didn't allow for me to mount any Hard Drives and didn't at the time provide any apps to use on Haiku i.e. Firefox.







Member since:
2005-08-07
For me, on my internet connection using *buntu, it takes maybe an hour to setup a Haiku build environment that is capable of creating an image - then you can create the first track for the CD (an ISO with a compressed boot floppy/El Torito) with a separate jam rule that was added to the build system in the recent months.
I looked into it and decided it was way too time consuming to waste a day on at that point.
/me turns in his geek card
Still, with you saying it only took about an hour, I might give it a try after all!
I didn't feel like having to register for yet another site. Incidentally this is also the reason I haven't bothered to get a Ubuntu Launchpad account. I dunno may be it wouldn't have required me to login or create an account, but I just didn't feel like dealing with it after I'd gone through the hassle of installing and uninstalling both VMWare Server and VirtualBox.
Thanks for the note, obviously I should have searched harder.
Still I think my base point remains valid--there are a lot of people who'd love to see what progress has been made with Haiku and they'd rather do it via live disc than any other way.
--bornagainpenguin