HaikuOS Hits Kernel Milestone
Professor Cool Linux writes "HaikuOS kernel team has a working implementation of fork(), exec(), and waitpid(), as well as a TTY layer. 'Despite some minor issues (you still don't see what you type), we can now have a fully functional bash running on our kernel. A lot of other shell commands, even those using our own libbe.so are working, as well.'Things are really moving."
BeOS still has some interesting features that other systems lack, and an open-source implementation of it will allow the whole world to improve it and benefit from it.
Kudos to Michael and the other hard-working people.
Please correct me if I got my facts wrong.
Looks like it's more functional than DOS already.
Also check out Cosmoe, which is a port of the AtheOS API (similar to BeOS's) to Linux. I think it's a really cool idea that is not getting the attention it deserves. It shares some code with HaikuOS, so you can help both by helping one.
Please correct me if I got my facts wrong.
Noth that HaikuOS is actually much further along than the kernel, broken keyboard driver, and shell. They are basically approaching a complete system from all directions, and have application server, media kit, etc. already in various degrees of completion. Before you know it will all fall into place and there will be a fully open-source BeOS clone, binary compatible with the original.
Please correct me if I got my facts wrong.
"Things are really moving."
That may be true, but they're still a long, long way away from their destination. They still don't have an alpha-quality kernel or interface kit, 3 years after work began. There's a heck of a lot of work to be done, by a pretty small team. Also, the developers are trying to clone BeOS 5, an OS released in 2000 - so when they finally get something usable and stable, at a guess sometime in 2006, they'll have a copy of an OS that is over six years old. Sure, there will be some differences, but that is the gist of it. Tiger will be out by then, Longhorn will possibly be out in that timeframe, and GNOME and KDE will be more advanced than ever. Meanwhile, Haiku will still be single-user!
I hate to be such a pessimist, BeOS was a great OS for its time, but it seems circumstance will relegate Haiku to the fringe, used only by hobbyists. It's a shame really that they were so ambitious (maintaining binary compatibility, pretty much doing it all from scratch), and that the efforts to implement the Be API over a Linux kernel stalled.
This OS is free
Like the autumn wind and leaves
Why another though?
Like stars in the sky
Open-source OSes shine
Too many to count.
Bold and daring though
Like the lion in its den
HaikuOS lives.
Reflecting the sun
Haiku's website shines, I hope
The OS does too.
With their lofty goals,
Like the eagle, they will soar
If success they find.
As the seasons pass
I have no time to try out
Every new OS.
Promising and new
As in spring the world will be?
Maybe, maybe not.
One complaint I have
The article does not say
What HaikuOS is.
A BeOS clone
That is what I've determined
Kudos! Keep it up.
(Ok, those last two weren't really related to nature, but it's late. Bedtime. For more information on what goes into making better haikus than I have made here, check out the Wikipedia entry on the topic)
Despite some minor issues (you still don't see what you type)
Despite some minor issues (your vaccum cleaner wont suck)
Come on, BeOS' (geek-) appeal will not go away because it's so old. Good stuff is on the way for release 2 of Haiku - we now need a solid base of development (Haiku will replace all Be-owned code with MIT licensed one) and ideas on overcoming BeOS' hurdles like single-user, poor hardware support, etc. Give me an updated and live BeOS clone and I'll take it, really! Every one who has ever coded something for the BeOS will tell you that it's API is God's gift to coders... Release 1 will come out and, with it's MIT like license, vendors WILL take it and expand it. It reminds me of kernel 2.6 - people only started using it after the 2.6.0 release and even after that, Linux stated that 2.6.0 was just another RC release. People react strangely to contents, but per-determinedly to release numbers. Also, we need a few good coders, so if you have some spare time, let us know!