Linked by Thom Holwerda on Fri 27th Apr 2012 22:00 UTC, submitted by koki
BeOS & Derivatives "Ultimately, Haiku represents a different way of viewing your personal computer. If you think that software shouldn't be riddled with bugs and incompatibilities and inefficiencies, if you hate being forced to swap out your hardware and software every few years because 'upgrades' have rendered them obsolete, and if you find that the idea of using an operating system that's fast, responsive, and simple is refreshingly novel and appealing, then maybe, just maybe, Haiku is for you." What fascinates me the most is that Haiku's not working on a tablet version. How delightfully quaint.
Thread beginning with comment 516126
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Uh what
by zlynx on Sat 28th Apr 2012 22:40 UTC in reply to "RE[6]: Uh what"
zlynx
Member since:
2005-07-20

I just grabbed the Haiku source (It's available via git) and here is a sample of some of the thread functions available from the kernel:

extern thread_id spawn_thread(thread_func, const char *name, int32 priority,
void *data);
extern status_t kill_thread(thread_id thread);
extern status_t resume_thread(thread_id thread);
extern status_t suspend_thread(thread_id thread);

Do those look like POSIX?

The Haiku file interfaces do use open, close, fcntl. The socket interface does use socket, bind, listen.

But that doesn't make it POSIX.

Reply Parent Score: 3

RE[8]: Uh what
by umccullough on Sun 29th Apr 2012 01:42 in reply to "RE[7]: Uh what"
umccullough Member since:
2006-01-26

I just grabbed the Haiku source (It's available via git) and here is a sample of some of the thread functions available from the kernel:


I thought that POSIX defined a userland API...

In any case, Haiku has native pthread support, and it is indeed a first class citizen, not some "bolted on" crap like was done in BeOS.

http://cgit.haiku-os.org/haiku/tree/headers/posix

Reply Parent Score: 5

RE[9]: Uh what
by moondevil on Sun 29th Apr 2012 07:58 in reply to "RE[8]: Uh what"
moondevil Member since:
2005-07-08

I thought that POSIX defined a userland API...


Certain POSIX APIs like fork() and exec(), have special kernel behaviour expectations. You cannot have them just as userland.

Anyway as I already mentioned, only if a system is POSIX certified, you can be sure that it really has proper POSIX support.

Reply Parent Score: 2

RE[9]: Uh what
by Vanders on Sun 29th Apr 2012 11:40 in reply to "RE[8]: Uh what"
Vanders Member since:
2005-07-06

I thought that POSIX defined a userland API...


POSIX/Single Unix Specification defines an API, but makes no reference to "kernel" or "user", or indeed even to "syscalls". How the API implemented is implementation specific.

Reply Parent Score: 2

RE[8]: Uh what
by Vanders on Sun 29th Apr 2012 11:39 in reply to "RE[7]: Uh what"
Vanders Member since:
2005-07-06

Do those look like POSIX?


The presence of non-POSIX API's does not negate the POSIX parts. Linux has a bunch of non-POSIX calls, too.

The Haiku file interfaces do use open, close, fcntl. The socket interface does use socket, bind, listen.

But that doesn't make it POSIX.


Um, yes it does. Or at least, it makes the API close enough to POSIX that it's entirely appropriate to describe Haiku as "a POSIX system".

Reply Parent Score: 3