SoylentNews is people
SoylentNews
posted by
martyb
on Sunday September 30 2018, @07:27AM
from the the-nightly-images-are-good-too dept.
from the the-nightly-images-are-good-too dept.
After nearly 6 years since R1/alpha4, Haiku R1/beta1 has been released.
[...] This release sees the addition of official x86_64 images, alongside the existing x86 32-bit ones.
[...] By far the largest change in this release is the addition of a complete package management system.
I'm very happy to see the progress alternative open source operating systems have made in recent years.
[Haiku -- an OS,
development continues,
open source is good.
Try your own --Ed.]
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
McDonald's -- Because you're worth it.
(Score: 2) by PartTimeZombie on Monday October 01 2018, @12:28AM (1 child)
I'm back baby!
No success. I ran the Haiku installer after booting from a USB drive. It boots up nice and quickly, then prompts to create a partition on my (blank) disc, which I do, accepting the defaults.
Reboot. Invalid Partition Table. Bugger.
I can either trawl through the install docs to figure out what went wrong, or give up. I might have another look later in the week. Maybe.
On the other hand, I installed and configured a NextCloud server running on Linux yesterday. It took a couple of hours and several beers, and was a doddle compared to Haiku.
(Score: 1, Informative) by Anonymous Coward on Monday October 01 2018, @03:40AM
From tonights faffing around, I *think* there's two gotchas to possibly watch for
1. Partition Table Type: something about MBR-msdos/GPT-GUID caused me some initial aggro, even though the disk I used had an existing MBR Table and I was reusing one of the primary partitions as the destination for Haiku, I had set something in the partitioner to MBR-msdos on my machine during install, it then seemed to go ok.
2. Partition ID: Even though during the install I changed the ID, formatted the partition as a BeOS one and then installed the OS to it, it borked on reboot. Make sure the ID/type *is* eb/BeOS, for some reason on my disk it ended up remaining 83/Linux, the original ID. Despite the installer being told to change it, it hadn't, so to make bloody sure I changed the partition ID to eb using fdisk from Linux then reinstalled...sweetness and light...It's now been up and running for just under 5 hours..
Time now for some booze, then snooze..