Haiku OS Ported To Intel 64-Bit Architecture
An anonymous reader writes "The BeOS-compatible Haiku OS operating system has been ported to x86_64. As part of the Google Summer of Code, a student made a 64-bit port of the kernel and user-space and it's now working. However, not all of the BeOS apps and drivers are yet working in 64-bit mode."
now I can run a text editor with more than 3.1 gigs of ram
I am always a fan of BeOS
Now it can fail twice.
The correct term for x86_64 is AMD64, not "Intel 64-bit architecture". AMD developed it, and licenses the patent to Intel. Intel64 is Itanium, to which Haiku has NOT been ported.
x86 is Intel but x86_64 was developed by AMD and adopted by Intel. How is it now Intel's 64 bit architecture. Did I miss something or am I wrong? I didn't RTFA.
Summary got it wrong, think the correct term is AMD64.
If only the community of software developers could conquer a community of designers and graphics people to collaborate without charge on a free operating system.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
...but, I can't be. Yeah, BeOS *was* awesome and I really *wanted* to see BeOS 5 (I remember one of the versions had a nifty menu system where the selector followed your selections as you drilled down).
But, come on, it's 2012. Maybe it's time to call it a day.
Actually, I take that back. I think this is just some Google summer of code project. Great for the student who ported the kernel! Not really big news outside of that, though...
PS: I don't reply to ACs.
So ... is everything still requiring GCC 2.95?
x86_64 == AMD64 == AMD extension to the 32 bit Intel arch
Intel 64 == IA64 == Itanium
Just wait. Now we'll see
Everyone posting haikus
Typical Slashdot.
File under 'M' for 'Manic ranting'
I adored BeOS back in the day. Although I've long since taken refuge with Mac OS X, I'd love to build a box specifically to run Haiku on native hardware. While Haiku is usable in a VM, it loses the snappiness that only bare metal can bring.
I'd love to relegate my Mac for work-only, and build a Haiku box for fun/the rest of life/as a hobby/to hack on/to help the Haiku Project. There's more than enough software out there to get by on, and new stuff hits all the time. I'm just sick of being stuck in a VM!
I wish I could confidently go and buy a motherboard, a CPU and RAM, a graphics card, put it together, and know Haiku will work with them. I don't mind what, I'm happy to build from scratch, but the Haiku Project is totally vague about what hardware works. It's taken a third-party - Haikuware - to put together a hardware database, but it's an out-of-date mess and wildly inaccurate (so many video cards are listed as supported, until you dive a little deeper and see they're all just VESA. That's not really 'support').
So, yes, I wish I could build a Haiku box and know it would work. Otherwise, I love the project and how far it's come!
What am I missing? Sixty four bits sounds too long Seventeen sounds right
Just got Slashdotted
... do they have a decent selection of NIC and video drivers yet?
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
I also was a big fan of BeOS. Loved it. Used it exclusively for a couple of years. Over a decade ago. Before it died.
But why exactly do we keep having articles about a BeOS clone operating system that is still basically in a nearly useless pre-alpha state after a decade of work? How is this useful to anyone besides the people working on Haiku? Where are all the articles every other week about how well GNU HURD is progressing? Because they are both just about equally useless at this point, until some sort of significant progress is made. There are dozens of other obscure in-progress experimental operating systems out there in various states of development, and there are places to go to read about them. I know, because I used to go to those places to read about all the obscure alternative operating systems.
I'm sure Haiku OS is great fun for the people who spend time working on it, and I wish them joy of it. But I'll bet that pretty much all the people who would ever want to hear about it are already on their mailing list.
What are they doing about secure boot? Game over. Sucks.
I wrote the LoseThos Operating System. It's been 64-bit since 2007. It's a free, 100% open source, public domain, ring-0-only, idenity-mapped, multi-tasking, multi-cored, non-networked, x86_64 operating system. It includes a 64-bit kernel, 64-bit compiler, assembler, debugger, graphics library, editor, boot loaders, tools... 135,000 lines of code written entirely from scratch over the last 9 years, full-time.
and build a Haiku box for fun/the rest of life/as a hobby/to hack on/to help the Haiku Project.
Acch, that's damn hard to read! You tend to see it as "fun/the"..."life/as"..."hobby/to"..."on/to" pairs.
How about: "and build a Haiku box for fun, the rest of life, as a hobby, to hack on, or to help the Haiku Project."
Exactly. Why don't these people rather put their energy to collaborating on Linux? Please tell me.
"Haiku OS" is a misnomer. The correct name is just "Haiku".
If I'm not mistaken Haiku and BeOS aren't *nix, much less Linux. The article has been incorrectly tagged as Linux.
Because Linux is the operating system for AIDS-infected faggots who are too poor to buy Macs. Haiku is for dudes he bang 10 pussies a night.
Really, in this day and age. why do we need separate device drivers for every device. Surely there are only a few ways in which data are transferred and parameters are updated for almost all possible devices. I can see the need for a device driver for really specialized and rarely found hardware, but almost everything else should have had standard interfaces defined for it by now, at least so far as the kernel is concerned.
Nullius in verba