Linked by Thom Holwerda on Wed 13th Dec 2017 23:54 UTC
BeOS & Derivatives

I've now turned my attention to preparation for beta1. Already talk has resumed on the mailing list of a tentative schedule; there still remains too much to do to expect it before the new year, but with the list of blockers now reduced effectively to two (one relating to installing source packages on the actual release image, which I intend to look into solving soon; the other is about clashing mime supertype declaration and may prove trickier to solve), the actual "release branch" is hopefully not more than a month away.

I've already begun drafting release notes and making build system cleanups as part of preparation. There is finally light at the end of the tunnel - don't give up hope yet. :)

I'm just putting it out there that if all goes according to plan, I'll be spending lots of time in a nice Haiku virtual machine over the coming weeks to get a really good look at the state of the continuation of the best operating system ever made.

It's time.

Thread beginning with comment 651994
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Go Native Thom!
by Thom_Holwerda on Thu 14th Dec 2017 11:56 UTC in reply to "Go Native Thom!"
Thom_Holwerda
Member since:
2005-06-29

I'd love to go native, but aside from not having the hardware to do so, I want to make sure I get an impression of *Haiku*, not its hardware support.

Reply Parent Score: 3

RE[2]: Go Native Thom!
by The123king on Thu 14th Dec 2017 12:21 in reply to "RE: Go Native Thom!"
The123king Member since:
2009-05-28

The VESA driver is very good for what it is. Sound support is pretty extensive, due to the OSS driver wrapper. Network hardware is well supported, due to the FreeBSD networking API wrapper (required for wireless drivers and their binary blobs). It's USB drivers are solid, and i myself have had no problem running Haiku natively on any hardware i've tried. I even had it booting natively on a 2011 MBP, and the only hardware not working was the wireless and bluetooth. Wired worked perfectly.

With Haiku, the true authentic experience is on real hardware. VM's provide a much more limited view of the OS, and don't allow you to truly experience how impressive Haiku actually is. If it had better application support, i'd switch from macOS in a heartbeat.

And of course, if you find hardware that's not supported, report it! Hardware support can only be improved by knowing what works and what doesn't!

Reply Parent Score: 1

RE[2]: Go Native Thom!
by Alfman on Thu 14th Dec 2017 14:38 in reply to "RE: Go Native Thom!"
Alfman Member since:
2011-01-28

Thom Holwerda,

I'd love to go native, but aside from not having the hardware to do so, I want to make sure I get an impression of *Haiku*, not its hardware support.


If you are going to be using/reviewing Haiku for a couple weeks anyways, I also think it's important for you to have some experience going native. Your experiences and feedback will be more valuable to the Haiku community if you are running on bare hardware than if you are running in a VM.

Do you have a spare harddrive you can use? Or external media you can boot from? If not then IMHO you should buy one, it's useful to have anyways. If I lived closer, I'd lend you those so you could do a proper review on bare metal as an OS is meant to be.

With linux distros I frequently use a partitioned multiboot setup with no problems, going so far as to install linux into LVM volumes (yay!). But as you know there's inherent risk to other operating systems this way and I personally don't have experience multibooting Haiku on a separate partition.

Reply Parent Score: 3

RE[2]: Go Native Thom!
by tidux on Thu 14th Dec 2017 17:46 in reply to "RE: Go Native Thom!"
tidux Member since:
2011-08-13

Get an old netbook or nettop with one of the early Atoms on it. I ran Haiku on an Eee PC 1005PE years ago, and it already ran rings around Linux for most things.

Reply Parent Score: 2

RE[2]: Go Native Thom!
by jua_ on Thu 14th Dec 2017 19:09 in reply to "RE: Go Native Thom!"
jua_ Member since:
2011-08-27

Note though that the usage experience in a VM will not be optimal. Unforunately, we currently don't have much in terms of VM guest additions. There is e.g. no guest graphics driver for VirtualBox, and VBox's VESA emulation is quite slow, so don't expect the UI to be very responsive. Further issues might be things like sound not working.
We'd love to have all these things working nicely in VMs, but that won't be the case until Beta1 at least (unless some volunteer jumps up now to implement it!). For now, the focus has always been in getting it to run well directly on hardware.

Reply Parent Score: 3