Slashdot Mirror
BeOS Ready for a Comeback as Zeta OS
Anil Kandangath writes "BeOS, the operating system that could have been the foundation for Mac OS X, but almost died, instead has returned as Zeta OS -- which is supposed to be fast, stable, media centric and boot within 15 seconds. Zeta is being released by yellowTAB of Germany and has applications such as an office suite and the Firefox browser bundled with it. Most BeOS applications will also run as-is. Screenshots are available." According to the NewsForge story linked there, the release could be as soon as next month.
You can get BeOS 5 Max free. It's moderately recent, and it's a nice way to take a look at what BeOS is all about if you aren't in the loop. It even boots as a Live CD if you're so inclined, although you can't do much besides click on stuff if you boot it that way.
Bears don't normally eat things that talk and move backwards.
BeOS was considered very strongly as a foundation for what would become OS X instead of NeXT - see the What is OS X? guide.
Windows has never been run on a supercomputer.
Well, unless you include clusters. But boot times on those are still limited by the abiltiy of each individual node.
tasks(723) drafts(105) languages(484) examples(29106)
Versions 1 through 4, as well as the Pro version of 5, were paid products. There was a free edition of 5, but it lacked features.
Directly from yellowTAB
Hardware requirements
Minimal Requirements:
* Pentium 200MHz (or Cyrix, Athlon, Via...)
* 32 MB RAM
* 600 MB Hard Disk Space
* 8 MB Video Memory
* bootable CD-ROM Drive
* Mouse, Keyboard, 14" Color Monitor
Recommended Hardware:
* Intel Pentium III 1 GHz (Celeron, AMD Athlon Duron/XP)
* 256 MB RAM
* 4 GB Hard Disk Space
* 32 MB Video Memory
* Soundcard
* CD/DVD Drive
* Mouse, Keyboard, 17" Color Monitor
Check our hardware compatability list to see if Zeta will run on your machine.
---
yellowTab has a story under which they have gained access to BeOS code (legally) prior to the Palm deal. Zeta = BeOS + yellowTab code + some Haiku code
I'm sure someone out there can do a better job of explaining this, but I'll take a shot:
Metadata is data about data. File metadata is information describing a file or its contents.
On many operating systems, file metadata comes primarily in the form of filename extensions. A file with the name "house.jpg" can reasonably be assumed to be a JPEG image file.
Unfortunately, filename extensions are pretty limited as a means of storing file metadata. There's a lot of other metadata one might want to store and retrieve for a give file.
Classic Mac OS went a small step further, storing 2 pieces of file metadata: file type and file creator. This information was stored separately from the filename, allowing Mac users to name there files whatever they wanted, without having to include a filename extension. It also allowed them to have some JPEGs open in Photoshop when double-clicked, and others to open in a web browser, by means of the files' creator metadata.
Not too much later, the World Wide Web appeared, and with it the use of filename extensions as required metadata for any files to be transferred via the Internet. So Mac users learned to live with filename extensions. Most of them were already doing so.
One development that accompanied the rise of the Internet was the development of mime types, another means of storing file metadata. BeOS used mime types extensively for storing file metadata, in conjunction with a database-driven filesystem. From what I saw, the combination was pretty effective and powerful.
File metadata on Mac OS X is a mess because Apple has officially abandoned the traditional Mac type/creator metadata system. This is one area where Apple could have taken a leadership position as they transitioned their core userbase and developers to their new OS, as they did in other areas like Core Audio, but instead of replacing the type/creator paradigm with some newer, better metadata system along the lines of that which already existed in BeOS, they simply chose to fall back to the less powerful but more internet-compatible filename extension paradigm. Yet they did not completely abandon the traditional system, as it would have made porting classic Mac apps to O S X more difficult. So some Mac OS X apps use type/creator metadata, some only use filename extensions, and some use both. Without a clear leadership direction from Apple, things are kind of a mess. Not that most users would notice.
There is some hope. Last I checked, Dominic Giampaolo was still working at Apple. He was the main brain behind the BeOS filesystem and went to work for Apple a few years back. He's responsible for the journaling support that was recently added to Mac OS X. Many folks (myself among them) are hoping that Dominic will bring the BeOS metadata system (or something like it) to Mac OS X. I believe Tiger and Spotlight will bring some improvements in this area.
First check BeOS!
.
http://web.archive.org/web/20010521150816/www.bene ws.com/beos/
to learn the root of the OS.
BeOS was originally developed for BeBOX(custom ppc based smp box) and later started supporting 60x lines of PPC based Apple's Macintosh computers and power computing(Taiwan's mac licensed manufactural).
With version 3.0 x86 versions started shipping.
There were 3.0, 4.0, 4.5 then 5.0 Personal Edition and 5.0 Professional Edition.
I personally believe that BeOS doomed itself with expensive public relations fund spend heavily on BeOS Preview release 2(Remember those BeOS preview release shipped with Mac related magazines for free?) and decision to start selling x86 version. They started offering free version for 5.0 called 5.0 Personal edition, which were bit late(developers have migrated to linux world then...). So company were bought out by Palm.
However, right before they were bought out by Palm, there were two main project which disappeared all together.
BeIA with SONY eVilla project and Dano(BeOS 5.5 release). BeIA pretty much slipped away when Be had office equipment auction when they closed down the building along with some handheld devices(tablet computers loaded with BeIA).
I've heard rumors that after Sony seeing the utter failure of QNX based iOpner(which was immediately followed by another QNX based 3com'saudrey), axed eVilla and destroyed all produced units, so only surviving units are the ones that were auctioned off with BE office closing in CA(developer's machine?).
After BE was sold to Palm...however, BE source along with Dano was leaked over Beshare(beos centric p2p software).
So Dano(considered as unofficial release ver 5.1d0)
OpenBeOS movement started around this time.
Now OpenBeOS has changed its name to Haiku-OS.
http://www.haiku-os.org/.
And soon people started BeOS Developer's Edition
at http://www.beosonline.com/.
And other people started BeOS http://freshmeat.net/projects/beos-max/
http://www.beos-max.org/.
Both BeOS Developer's Edition and BeOS Max revolves around Be's latest official release BeOS Personal Edition 5.0 + 5.0.3 upates and many new improvement which were contributed by a user community developed opensource softwares & drivers.
However, there versions which includes some unofficial released stuffs(stuffs from Dano and some controversial stuffs)
http://phosphuros.tk/
You can read the article by OSnews here.
http://www.osnews.com/story.php?news_id=6948
Here are some screen shots provided by Korean BeOS UserGroup.
http://www.bekrage.net/gallery/view_album.php?set_ albumName=screen
BeOS is nice because Localization stuffs were incorporated into GUI nicer than most other OS, making easier to support different language than English, especially where language isn't based on phonetic latin based alphabet languages such as Korean/Chinese/Japanese. Thier alphabet is 8bit(or even 16bit) character based.
Currently, Haiku-OS programmers are plugging away diligently where OS is almost ready, where most of the bread and butter applications were already worked out! This is a nicer situation where applications are already there when OS still hasn't shipped, due to special current circumstances of BeOS.
ZetaOS is heavily based on BeOS R5.0.3 + Bone network(Dano style) + lots of improvement borrowed from drivers found on BeBits(opensource community of BeOS) + Haiku-OS(OpenBeOS).
ZetaOS, there are RC1, RC2, RC3, Zeta Neo(considered as RC4) a
I have no idea what bug you have up your butt, but here's a few points.
Yes, BeOS is a dead operating system. There are no marketing claims for BeOS after about 2000. If you're going to be evaluating the original claims for BeOS made during its brief moment in the sun, 1998-1999, compare those claims with what was around then, not what's around now.
Steinberg ported Nuendo to BeOS. You'll notice that it could process 96 media tracks simultaneously. Why is this significant? Because on the same hardware the NT version could only do 48 tracks.
As a matter of fact, yes, BeOS did have a better media core than anything else did, in one specific area: latency. There was literally nothing else beyond true RTOSes that could touch it. If you go to a stage show in Vegas, Disney or even some Broadway theatres, there's a non-zero chance that the sound and lighting system is still being run by a BeOS-based system from LCS. In 2005, other operating systems have caught up in some respects, but the main thing that "beats" BeOS in media processing is simply Moore's Law: machines are so much faster now than they were six years ago that it doesn't matter that their signal processing still blows moose chunks.
There are other things that BeOS had that no other operating system had, most notably the file system and live queries that could operate on metadata. Make a virtual folder that contains all the word processing documents you've edited in the last week? No problem. BeOS was by far the most responsive operating system I've ever used. And you know what? It got more commercial applications announced for it in its first two years of public release than Linux did in its first five or six. (Some of those commercial applications are in fact still around, now on other platforms.)
Yes, BeOS had its share of problems, some of them did involve driver support, and there's been very little development on drivers since 2000. But it wasn't difficult to find supported hardware back then--I ran it on a pretty much stock Gateway PC--and I can assure you that BeOS does not suck. If Be had made some wiser business decisions (like not going after the non-existent internet appliance market, and knifing their desktop developers in order to do it), it'd probably still be around.
I'm not particularly interested in ZetaOS because, in the context of 2005, it's not a very compelling operating system. But you obviously don't have a clue why so much of the computing world was excited about it in 1999.
In my opinion (I've used Macs since 97 and used BeOS since the first release) I would rather have seen BeOS with the Aqua makeover. BeOS was VERY close to being like a UNIX, it tried to copy all the good stuff but left out the bad stuff.
I don't know how well it worked in a technical sense but it let you load and unload drivers and extensions just by moving them in and out of a folder (never reboot!). It also let you load extensions and drivers for the machine, or just the user (it was never multiuser but was designed with this in mind for the future).
On a 240 MHz 603e I was able to rotate a 3D cube playing QuickTime movies on all 6 sides (compressed with the "video" setting). Without GPU support. BeOS was like the new Amiga, it was amazing and would have been something truly phenomenal had it come out AFTER the DOJ trial against MS.
Not since Marie-Antoinette played milkmaid has looking simple and honest been so fake and complicated.