Linked by Thom Holwerda on Thu 22nd Aug 2013 21:00 UTC
BeOS & Derivatives

Although I have been a lazy blogger lately we haven't been lazy working on our remaining tasks at all. So, unsurprisingly, since my previous post we have reached and passed a few nice milestones. The latest one is that we're finally able to build the gcc2/gcc4 hybrid Haiku images again, including all the software needed for the official release.

While that in itself isn't a particularly impressive feat - after all we were already able to build the complete gcc 2 part before - the interesting aspect is how we are doing it.

Interesting progress for Haiku.

Permalink for comment 570452
To read all comments associated with this story, please click here.
RE: Finally Haiku news :)
by alphaseinor on Fri 23rd Aug 2013 16:38 UTC in reply to "Finally Haiku news :)"
alphaseinor
Member since:
2012-01-11

The kernel has had thousands (millions?) of improvements since it was called NewOS.

Here's the bug tracker on TRIM support
http://dev.haiku-os.org/ticket/7876

in a (pseudo) microkernel as haiku's is, generally we don't put this kind of support into the kernel. we usually prefer to run it in userspace, although it can be implemented at the kernel level (gotta love opensource).

GNU (never separate the two) Linux is a monolithic kernel, so drivers and kernel extensions run in kernel space, although it could be considered modular as well as some exceptions run in user space.

Monolithic versus micro, versus modular was bikesheded to death in the 2002-2005 Walter/OpenBeOS/Haiku era...

Reply Parent Score: 2