|
|
|
|
|
by chazeon
1250 days ago
|
|
I am confused about this: > Haiku, like BeOS before it, is not a Unix. If you actively like Unix, and what you want to do already works well on Unix – any Unix, and that includes macOS, as well as Linux and FreeBSD – then you probably won't see much appeal here. Don’t they support the same set of terminal command as in other Unix-like systems? From what I saw [1] there aren’t much difference. Well that is what what people care about unix, right? [1]: https://www.haiku-os.org/docs/userguide/en/applications/list... |
|
It's debatable whether or not BeOS was a UNIX, but I think by most standards it is: the `fork()`-based process model, UNIX-style file descriptors (but no `mmap`), etc.
Haiku has all the bits BeOS had, of course, but we have far extended our POSIX compliance: of course we have mmap, but also pthreads, and /dev/ (including all the staples, like /dev/null, etc.) These aren't mere compatibility wrappers, but often the "native" APIs; some of the Be APIs are implemented on Haiku using them (while others use lower-level APIs.) There is no "POSIX compatibility layer" in the kernel, it's just natively POSIX all the way down.