Linked by Thom Holwerda on Thu 6th Dec 2012 18:03 UTC, submitted by kragil

Thread beginning with comment 544601
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Actually the "Duke Nukem of OSes" is...
by looncraz on Mon 10th Dec 2012 19:42
in reply to "RE[4]: Actually the "Duke Nukem of OSes" is..."
The Linux kernel is a monolithic kernel and doesn't fit well into the BeOS micro-kernel mold.
NewOS was a near-perfect fit.
Audio, networking, even screen-drawing are user-mode activities. The kernel just gets a basic environment setup and handles the earliest stages of identification.
The Linux kernel would have had to be heavily butchered and altered to the point of no longer being Linux for this to work.
That takes time and man-power, the NewOS kernel was almost already compatible as it was and there was no need for the kernel ABI to be wholly compatible with BeOS since Haiku was re-writing all of the servers and drivers as well.
I think Haiku made the right choice with NewOS!
--The loon
RE[6]: Actually the "Duke Nukem of OSes" is...
by Jack Burton on Tue 11th Dec 2012 07:40
in reply to "RE[5]: Actually the "Duke Nukem of OSes" is..."
The Linux kernel is a monolithic kernel and doesn't fit well into the BeOS micro-kernel mold.
NewOS was a near-perfect fit.
Audio, networking, even screen-drawing are user-mode activities. The kernel just gets a basic environment setup and handles the earliest stages of identification.
NewOS was a near-perfect fit.
Audio, networking, even screen-drawing are user-mode activities. The kernel just gets a basic environment setup and handles the earliest stages of identification.
Actually networking lives in the kernel.
Member since:
2005-07-06
Also there are Linux distributions which brings something really different: NixOS(functional package manager), GoboLinux(simpler FHS), Ubuntu(Unity) for example.