Bruno G. Albuquerque was the first to submit the big news on OpenBeOS. According to the OpenBeOS website, “With the latest round of changes made to the runtime linker, the startup code, and libroot.so, we are now finally able to load and run native BeOS applications. Of course, only simple one will work right now (since we only have (most of the) parts of libroot.so implemented), but I was able to run the same application under BeOS and OpenBeOS simultaneously. We can now make our first tests to prove binary and functional compatibility between both operating systems.“
OpenBeOS Supports BeOS Executables
About The Author
Adam Scheinberg
Technology Executive • Web Developer • Father • Foodie • Music Snob • OS enthusiast
Follow me on Mastodon @[email protected]
Launching BeOS apps on the actual thing gives a completely different light to it all, doesn’t it? I am really excited.
I guess that just goes to show the skill of the reversers for BeOS.
REMEMBER: Reversing for compatibility is legal! 😉
–The loon
Welcome news, keep up the good work!
Very important milestone they’ve reached there. Congrats you guys. Now where’s that PayPal account I can donate to?
That was really quick!I guess all of us who thought OBOS was vapor (myself included) have to eat some crow.
Kudos!
Try it breaded with a light tempura batter, deep fried and served with some nice panzu sauce. That’s the best way I’ve found to eat crow 🙂
I can’t wait until the first full-system beta comes out!
Those guys made my day once again. Good news is always appreciated.
Visit http://www.inorganic.de
Wow!
So amazing.
Now, what does this exactly mean?
What can it run exactly? Simple “hello world” apps?
Is it gonna be extremely difficult to make bigger apps run?
How integrated are the other projects? I mean, is it possible to have the kernel with the Be FS running at the same time?
Congratulations, again.
I admit that when obos first started I wasn’t sure if it would ever go anywhere. I was so excited by the possibility,however, that I bet a friend that at some point it would at least run a few native beos programs. I guess I’ll have to wait for second test program to collect, but I’m very excited.
Why don’t you think at the bad side?
OpenBeOS always had the possibility to go over BeOS (I know that some kits are better than the originals!). Making it binary compatible could just have messed up things.
Remember the basis of BeOS philosophy: reliability and no footprint.
We (community) should not let OpenBeOS become a mess like Windows that in its latest version still supports programs of the jurassic!!
It is not needed at all: code compatibility is better.
OpenBeOS R1 goal is to be source and bginary compatible to BeOS which means all (or most, a least) current BeOS apps will run on it. It does not mean OpenBeOS is limited by what BeOS R5 is as we *WILL* be adding stuff that R5 does not have, like mmap (in the kernel), search on non-indexed attributes (in OpenBFS), and more stuff on other kits. Where we will go from there is a completelly different story.
-Bruno
what a wonderful bunch of committed, good quality developers!
And we’ll reserve the middle fingers for the naysayers.
Thank you axel and your team for doing this!
Maybe the paypal isnt that bad idea after all…
I know that you are a student.. so =) You drink beers…
/Konrad
How long will it be before we get an idea as to how many apps this thing can run?
This is indeed a major step. Things will only get more interesting from here. I’ll be excited to hear when OBOS can run Be’s app_server (and of course more excited when the OBOS team releases their app_server replacement)
This is the best news all year
Am I the only one that doesnt understand what the runtime linker, the startup code, and libroot accually do? Are they major parts of the kernel or what?
How much of R5 is needed to do this, is it still just substituting a few libs and how soon might OBOS be selfstanding on NewOS but just able to run at this level?
Excellent news all the same!
None of R5 is needed to execute the BeOS binary by the OpenBeOS kernel. The executable is loaded into the filesystem on the floppy and it is able to be executed entirely under OpenBeOS. Hope this answers your question and demonstrates how incredibly cool this is.
Regards,
Maverick
Fantastic!
Very nice progress. This will be a big year, with Zeta imminant and probably a feature complete OBOS beta by the years end. My initial estimate for OBOS beta was 20-24 months, and I still stick by my estimate.
screenshots? 😉
From the small steps come the great leaps. Congrats to BGA and all OBOS hackers.
Ah, the renewed promise that Open BeOS offers… Hearing of tentative binary compatibility makes me very happy, like watching a much beloved neighbor’s child take its first steps. Congratulations guys, and keep up the good work. Your baby may be the last true desktop OS.
What does small mean? Is it close to where ReactOS is with regard to Windows like running console apps well, but just a few GUI apps or what?
Are you sure that adding binary compatibility hadn’t enlarged the whole thing a lot?
Wouldn’t it be faster, simpler and smaller without it?
Read the last article here on OsNews: the future of operating systems is simplicity!
Who cares if software need to be recompiled, I prefer a small and fast OS.
Hey good job, great accomplishment. Just know that there is a rather large following here in one of California’s top engineering universities. Keep up the good work