Slashdot Mirror

I'm going to go out on a limb here and hazard a guess that if I said, 'NetBSD,'

1. AtheOS is no longer developed, and the codebase has not been updated in several years.
2. Syllable is our community-driven fork of AtheOS, which was started two years ago.
3. AtheOS domain lapsed and is now hosting a knock-off website hawking drugs

..one shouldnt forget AtheOS which has some similarities to BeOS.

AtheOS!...?

I need to finish my OS for when Linux goes down in flames. Then I can be the author of the most popular free OS instead of the least popular.

Isn't that what open source is all about? Who is most popular?

Try these OSes on for size:
Retro Forth
AtheOS
VSTa
TinyOS

Does AtheOS's previous developer still use it on his home machine?

It sounds like the worst of both worlds to me -- it's not free (speech or beer) but it also doesn't have the broad support of Windows or Mac OS. Sheesh.

I'm sure this will appeal to some people who like installing new OSs for the heck of it, but why not try some of the interesting free ones first?

Maybe we should check out alternate operating systems that may not have this problem?

-dk

Looks like a rerun of the AT&T lawsuit that threatened BSD. Time for the masses to move to the next worthy operating system

-dk

AtheOS uses the BIOS for disk access, according to the website:

There is an IDE driver on it's way (only tested on one machine, and not part of the current distro). But generally all disk accesses are done through the BIOS, so most IDE and SCSSI disks should work. I even boot AtheOS from my panic ZIP disk every now and then.

I have to wonder what AtheOS' disk performance is, though. It was common during the Windows 3.11 days for disk controller makers to produce 32-bit disk drivers for Windows that would bypass the BIOS and talk to the controller directly, thus avoiding expensive protected-to-real-mode-and-back switches.

This, no?

-uso.

AtheOS
BeOS
Amiga
atari's os
Ecomstation (fka OS2)

those are the *easy ones*... there are probably 500 more...

UNIX, on the other hand, commonly links 16 processors and can successfully link up to 32 processors for simultaneous operation. This difference in memory management performance is very significant to enterprise customers who need extremely high computing capabilities for complex tasks. The ability to accomplish this task successfully has taken AT&T, Novell and SCO at least 20 years, with access to expensive equipment for design and testing, well-trained UNIX engineers and a wealth of experience in UNIX methods and concepts.

If I am not mistaken, KHTML now runs on Linux, Atheos and now Mac OS X. That's not bad for code that is supposedly "not portable".

When Kurt Skuen (Guy who wrote AtheOS) was looking for a browser engine for AtheOS, he looked at both KHTML and Gecko. In the end, he chose KHTML because it was easier to port than Gecko. That even included writing Qt2.x wrappers around the AtheOS GUI (Not easy, as Qt is not thread safe, while AtheOS is inherently multi threaded).

Kurt was able to port KHTML in about two months or so. I'm barly surprised that Apple chose KHTML over Gecko (Have you even tried to read the docs regarding embedable Gecko? Just look at the list of dependencies!)

Do the install demo the last day. Show them all the wonderful things non-Micr0s0ft platforms can achieve first, then show them how to harness all that power on their own system at home by demonstrating how to dual boot a box. NOT! Be sure to include a big disclamer - write letters to parents to back up their data, etc. Or give out demo CD's like the Knoppix distro and maybe figure out a way for people to store their data somehow. Messing with people's parents' hard drives would not be advised for a bunch of high schoolers. Fried hard drives are not the right way to send a good message about Linux and other alternatives to parents, etc.

Use debian for the majority of your demos. Debian is used as a base for a lot of other distros out there, so this would be a terrific learning platform. apt-get is extremely popular and easy to use and would be a great way to build confidence. "Gee! That's even easier than windows!" It is, again, used in a number of debian-based distros and this is a plus. Messing with RPM dependencies I would say would be less conducive to learning. It should be experienced, but you don't want to spend a lot of time with a headache like this. Let them figure it out when they get to a real RPM based system and they overload their harddrive with unnecessary packages. We needn't worry their little minds with this now.

I would suggest, if you've got a bunch of spare computers for your use, installing a selection of operating systems. Maybe just have them around, for kids to explore on their own time if they seem interested. A selection of the common Linux distros would be good - Red Hat, Mandrake, etc. If you've got the money, do some installs of Xandros, Lindows or Lycoris. Show an install of Gentoo and demonstrate the portage build system. Put YellowDog or LinuxPPC on some older Mac machines that the school is sure to have laying around. Install something fun on a new G4. You're wide open here. If you've got the time, do installs of NetBSD, OpenBSD, and FreeBSD. Actually, I'd move FreeBSD up the ladder a bit, even into the linux distros above. This one I think is going to become pretty important in the next few years. It's clean, stable and very security concious. It also runs linux binaries and, all in all, is a tremendous platform. The flexible workhorse.

Linux and *BSD aren't the only alternative operating systems. Try doing an install of SkyOS, AtheOS, or MinuetOS. Read about those here.
There's also Syl-la-ble, QNX[review], and, lest not forget, the Wonderful! the Amazing! MacOS X. Amiga, Minix, VMS, on and on. Find a local LUG with someone in it that likes these obscure operating systems. See if he (she?? --nahh...) will lend a hand. No. Not that hand.

Show them the GUI. Copy some files around or perform some other common tasks using the GUI's helpful tools. Then show them how much faster and more efficiently they can do the same after clicking on gnome-terminal (or Kterm or whatever). Show them the virtual terminals that are availible if X isn't around. Show them that you can start up two instances of X, each with a different user, and switch between them [after you have one going, type "startx -- :1" in a virtual terminal as the user you want running the second instance, then Alt-Fx to find it. Switch back and forth). Then ask them if they can do that on dad's windows box. Give them a printed reference of some of the more common unix command and have them figure out how to perform a selection of tasks. Do the shuffle about pipes and redirection and all that and have them do some "homeworks," maybe working together. Then tell them to use the man pages for command xxxxx and yyyy, integrate the knowledge found there with the printed references you gave them, to complete another task. Do speed trials. Ask them to try the same task with only the GUI. Point made.

Hand them a Knoppix disk. Let them find debian if they are feeling adventerous. Suggest to them if they think they know what they are doing, and can stand being grounded or whatever if they break mom's computer, to try an install of Mandrake - with the easy repartitioning and all built in so nicely. Easy to use from the get go, but quite fully functional linux distro as well. Easier still, and based on debian, would be Xandros. Apt-get to your hearts content, and can even resize NTFS partitions.

"Am I wearing my pants?"

Don't forget this one before you walk into your first day of class.

The AtheOS File System created by Kurt Skauen for use with AtheOS is 64bit too. He simply bought a good book or two, and put it together all by himself (along with the OS that uses it). If one guy can do this by himself, why is it so "extraordinarily difficult" for Microsoft to do?

Although...

AtheOS (Seems to be down mostly these days)
Syllable (Carries on where AtheOS left off)
SkyOS

Read OSNews for more :)

Yes, attributes are certainly cool. Both BFS and AFS (AtheOS/Syllable) use attributes.

I'm wondering about Linux supporting them (At least nominaly, with XFS) as at the moment, tools that understand attributes are a little thin on the ground. tar, for example, does not understand attributes. Nor do the usual GNU fileutils. Linux support could hopefully mean broader and standardised support in general, which would make our job a little easier.

Just switch to Qnx or AtheOS

Or the AtheOS parrots...

www.slackware.com
www.redhat.com
www.debian.org
www.mandrake.org
cm.bell-labs.com/plan9dist/
www.atheos.cx
www.freebsd.org
www.openbsd.org
www.netbsd.org

That's that problem solved, then. Next, please!

No. You're new here aren't you? Well, if you realize that slashdot posters talk out of their ass, then you can't be that new.

I dearly wish there was a "strip all comments labeled "Funny" button.

Considering what passes for funny on slashdot, I'd have to agree with you.

(hell, slashdot doesn't even have color barcharts on the front page!)

Oh, so this is supposed to be a funny post, right?

Several years ago, comments included information from computer scientists, sysadmins, and knowledgable hobbyists.

I'm a computer scientist. See, it says so right there on my degree. Do you feel better now?

The moderation system that once worked well is failing miserably because almost all moderators are as stupid as the posters.

Hey! I resent you calling me as stupid as the moderators! And for implying I voted for any of the idiots in Washington, DC! I only turned 18 in 1996, and by that time the elections were already over. That and I didn't vote for Dubya.

Beyond technical comments, why does everyone feel a need to deride RMS and the GNU project all the time?

Umm, I think you answered your own question with this choice quote: "As anyone can tell, I'm pretty pissed that a bunch of whiney losers in diapers, who couldn't spell "algorithm" if they had a copy of CLR on their desk, or explain why CISC was a natural choice for microprocessors in the 1960s, have drowned out any hope of interesting discussion on a technical topic.". That, and my general theory is that people will a) generally attack what they don't understand and b) will use ad hominem attacks against things they disagree with.

1) Think for yourself

Hey! Who are you to tell me what to do? Besides, I'm already doing that.

2) Listen careefully to what people say, in comments and otherwise

Umm, didn't you just argue that most of what is in the comments here is not worth listening to?

If we follow those rules, then maybe we'll be able to learn stuff from slashdot comments again.

Agreed. I for one am still curious as to why we never see posts that are truly informative, like ones that list other operating systems that are making faster progress than HURD, and are very different.

Here are some screenshots of Cosmoe No, really. He uses the AtheOS appserver & decorator plugins. It looks like AtheOS....On Linux!

This is one of the several BeOS features that the Open Source community should reall (sic) consider stealing

Yes, I agree, we desperatly need to write a 64bit Journalled FS with Attribute meta-data support. Someone should read Dominics book and implement the ideas.

Konqueror from KDE 2.2.2 is quite stable on my machine. I don't use Mozilla in Linux but on Windows it seems quite stable as well. I don't think one has a huge advantage over the other in this area.

2) Cross-platform support. Konqueror is not available on Windows or Mac OS

And Mozilla isn't available on AtheOS ;-). Konqueror is actually quite portable, due to it being based on the well-designed and cross-platform QT. A Windows or MacOS port of Konqueror/Embedded would probably be a fairly simple thing if you had a QT/Windows or /Mac license. Also, the KDE-Cygwin project is aiming to provide all of KDE on the Windows platform, using the GPL'd QT/Linux. And besides, cross-platform support doesn't directly benefit a Linux desktop user. Konqueror's aim was never to be the be-all end-all of browsers, just a good browser for KDE. And it has succeeded.

3) Standards support. Mozilla has better support for more standards than Konqueror

I don't know where you might get data to show this one way or the other, but I do know that Konqueror's from KDE 3's javascript implementation rocks. It works on many sites that Mozilla doesn't even try to run. Konqueror goes out of its way to be compatible with IE (as far as that is sensible with regards to standards support) and this helps it render sites designed by Windows users better.

4) Scope. Konqueror is just a web browser/file manager. Mozilla has a mail client and an HTML composer.

"Just" a web browser/file manager? It rips CDs, it interfaces with digital cameras, it browses Windows networks, it browses the web, it manages files, it does FTP, it burns CDs, it manages MP3s on your Nomad Jukebox, it browses your RPM database, it is totally integrated with KDE and previews tons of file types. "Just" a browser/file manager indeed! I think KMail is a great mail client, and I prefer the concept of Quanta+ to a WYSIWYG html editor.

5) Tabs :)

For the life of me I can't understand what the big fuss is about tabs, but they'll be in KDE 3.1.

Although I'm always suspicious of the practise of tying a windowing system into the OS, the windowing system of AtheOS is nicely OO'd and clean.

(Unfortunately it is very young code, and therefore has an API liable to change and a few missing features).

There is no insurmountable reason why something like this couldn't be constructed for any other OS. I would drop this bloated X rubbish in a second.

I use KDE, and have found that Konqueror never freezes while loading pages. The AA works very nicely too. If you want something closer to BeOS, you may like to try Atheos.

You could try Atheos. It's not a BeOS clone, but is quite like a combination of it and AmigaOS, and is under rapid development. It's also under the GPL. It's aiming for the market of people who don't want to fiddle to get the OS the way they want it. The OS has an integrated GUI/desktop, instead of the Linux style of Kernel-Usermode-XFree86-WindowManager. It's mostly POSIX compliant, and has many Linux apps ported already. It might be just what you're looking for.

You should concentrate on a good operating system, or this one here.

If they could do that, they wouldn't be in QA.

Actually I know I could do that, and I'm a QA Tester. I just don't code for a living, but write copiuous amounts of C & C++ for a certain Open Source Operating System in almost all of my spare time.

The difference is actually in the fact that a QA tester is doing BlackBox testing, and shouldn't see the code anyway, whereas the WhiteBox testing is being performed during Peer Reviews & Code Audits by the developers. So thats why a QA tester is unlikely to find a subtle buffer overflow.

Kurt Skauen started the project with the intent of making an Amiga clone. He says in the FAQ, however, that there isn't much resemblance these days besides the window borders. The article did call him an ex-Amiga coder, he must like the look.

This is one of those things that I keep meaning to check out. Maybe now I will.

"The GUI is server/client like X11 but communicate through the native messaging system and the protocol is private to the server and client library and entirely hidden from the applications."

Yes, I know this is the wrong place for this. But since the so called staff doesn't seem to be interested in posting anything but the newest build of Linux, I'll post here.

AtheOS 0.3.7 Released

Thank you for modding this as -1 Offtopic.

This is probably even more off-topic, but bear with me:

Just managed to get the company to buy a Mac. This is for a 700 employee MS-purity site (MS everything bar HP-UX boxes for Oracle). Have to say the experience made me go "ohh" in a quiet little voice of stunned amazement. Incredible combination of Linux/*BSD internals with a glorious user interface, and the whole thing reeking of design and quality.

However the relevant bit about all this was the rather groovy way the desktop is displayed, with all the natty minimise / maximise animations. Apparently this is all done on a PDF variant called Quartz. Seemed pretty good to me.

We've already been hearing from AtheOS not using X. Perhaps (and this is where I come marginally more on-topic) there's some mileage in merging the current efforts on xPDF, or some open alternative, the great work on Quartz from the Apple fellows, and binning the antiquated X interface. You could allow for all sorts of more up-to-date features a la Citrix's ICA, e.g. encryption, compression and the like, plus allowing better app serving in the ASP model.

Aegilops

Why was the lameness filter encountered? You stupid shitdicks.

Sounds like you want AtheOS.

a monopoly. That's right, AtheOS has an integrated web browser!! What will you do to maintain healthy competition and innovation in the OS market?

Hmm, oops.

Just for the benefit of the others reading this slashdot thread: The AtheOS FAQ has a note on portability that slashdot readers might find informative. You should read it. Wish i'd noticed that before i posted.. hm. i feel stupid.

i'm going to go crawl into a hole now. seeya. :)

Linux needs a single GUI. Be it Gnome, KDE, or whatever. Pick one, build it right. Follow Microsoft's example and do extensive usability tests, and make it easy and intuitive for the user to use it.

Hey! That sounds like AtheOS! I havn't tried sitting my mother in front of my AtheOS box and letting her go yet, but I think i'll get IPTables set up on my Linux box and give it a go. I reckon I can have her doing the basics in a few minutes.

one specific and SIMPLE GUI and a text console as hard and complete as you may whish?

Why this sounds like a perfect time to plug AtheOS!

One GUI (Not X), and a terminal that you can use to run a shell. Choose your POSIX compliant shell. Currently it uses bash, although I have no doubt tcsh/ksh/zsh/$PERVERSE_SHELL_OF_THE_MONTH would compile and work perfectly well on AtheOS. Oh and it does do Telnet/SSH remote logins as well. Beut!

Is the Linux kernel the official GNU kernel now? If not, I will humbly suggest that AtheOS be considered as the GNU OS. It's a modern, multi-user OS that has its own aims but doesn't abandon UNIX compatibility. Much GNU software already compiles and runs on AtheOS. Would the GNU Project consider this?

Oh, hang on, you want an OS with one desktop? Try Windows.

Or, why not try AtheOS?

We prefer choice here.

So do I. I have a choice between the "Linux way", which is basically a huge mish-mash of diferent toolkits, window managers and desktop enviroments, and the "AtheOS way", which is basically a unified kernel, single GUI tookit, and a single user interface.

I'm seriously hoping to be able to use AtheOS as my "main" operating system at home within six months, instead of Mandrake 8.0 as I currently use know. Seriously.

New version. There has been a long time since the last release of AtheOS but finally V0.3.5 is ready for release. There is several reasons for the long delay like the fact that I have been rather busy at work lately and that we have had a great summer here in Oslo so AtheOS have not always been at the top of my priority list. Also quite a lot of work have gone into this release and quite a lot of new features and improvements have been made.

Many of the changes are additions and modifications to the various API's and toolkits but also a few user-visible aspects are improved in this release. Many bugs are fixed in the text editor and list-view widgets. The scrollbar have got a totally new look and a few new features like "paging" (jump one page when clicking beside the knob) and small arrow buttons that can be used to move the know.

Some crash-bugs have been fixed and the general robustness of the application server has been improved. Also several kernel crash-bugs have been fixed so the general stability of AtheOS have improved quite a bit. The uptime on my heavily stressed developer machine is 34 days when I write this (the time since the last HW upgrade).

This version also have two new keymaps (German and Sweedish) and support for a wide range of nVidia graphics adaptors.

The main focus for V0.3.5 however has been on the KHTML based web browser. I have ported the HTML parser/renderer used in the Konqueror web browser (KHTML) to AtheOS. KHTML is a very capabel HTML parser and renderer that support both CSS and javascript and so does the AtheOS web browser. Finally a high-quality web browser for AtheOS! The browser is part of the 0.3.5 base install and the 0.3.4->0.3.5 upgrade archive. Take a look at the changes list for a more detailed list of changes since V0.3.4.

New version. There has been a long time since the last release of AtheOS but finally V0.3.5 is ready for release. There is several reasons for the long delay like the fact that I have been rather busy at work lately and that we have had a great summer here in Oslo so AtheOS have not always been at the top of my priority list. Also quite a lot of work have gone into this release and quite a lot of new features and improvements have been made.

Many of the changes are additions and modifications to the various API's and toolkits but also a few user-visible aspects are improved in this release. Many bugs are fixed in the text editor and list-view widgets. The scrollbar have got a totally new look and a few new features like "paging" (jump one page when clicking beside the knob) and small arrow buttons that can be used to move the know.

Some crash-bugs have been fixed and the general robustness of the application server has been improved. Also several kernel crash-bugs have been fixed so the general stability of AtheOS have improved quite a bit. The uptime on my heavily stressed developer machine is 34 days when I write this (the time since the last HW upgrade).

This version also have two new keymaps (German and Sweedish) and support for a wide range of nVidia graphics adaptors.

The main focus for V0.3.5 however has been on the KHTML based web browser. I have ported the HTML parser/renderer used in the Konqueror web browser (KHTML) to AtheOS. KHTML is a very capabel HTML parser and renderer that support both CSS and javascript and so does the AtheOS web browser. Finally a high-quality web browser for AtheOS! The browser is part of the 0.3.5 base install and the 0.3.4->0.3.5 upgrade archive. Take a look at the changes list for a more detailed list of changes since V0.3.4.

Ok, the site has loaded (finally), the actual changelog is at: http://www.atheos.cx/download/0.3.5/base/changes.t xt

Monopolies have the power to enrich themselves by evading the limitations of the competitive marketplace. Prices need not fall when demand slackens, and demand need not slacken if the monopoly makes itself essential to the economy (like electrical power or computer operating systems).

Even though this is, in all probability, a troll, I'll bite.

Open Source advocate[s] simply need to abandon Linux and create a new OS from scratch with the focus on flashy graphics, gaming, same stability, and an equally cute logo.

The OS you're talking about is (or at least might be in the future) AtheOS. All it needs are drivers, and it's there.

AtheOS is a free desktop operating system (currently) under the GPL lisence. AtheOS currently run on Intel, AMD and other compatible processors and support the Intel Multi Processor architecture. I have seen quite a few anouncements of "promising" OSes with "great potential" during the development of AtheOS. The problem is that when I follow the links I normally find a description of the concept, a floppy-bootloader written in assembly, and not much else. AtheOS is a bit more mature, and is already running quite a lot of software. This server for example is running AtheOS. The HTTP server is a AtheOS port of Apache, and most of the content is generated by the AtheOS port of PHP3 and perl.The native AtheOS file system is 64-bit and journaled.

AtheOS is not meant to be a new Unix clone (like Linux and *BSD) but a new clean desktop OS. It does support large parts of the POSIX standard and hence are able to run most of the UNIX CLI tools and it comes with a standard UNIX shell (BASH) but this does not compromise anything in AtheOS as a desktop OS. AtheOS have a integrated GUI that works in conjunction with the kernel and various other components to create a complete and consistent system. The GUI is server/client like X11 but communicate through the native messaging system and the protocol is private to the server and client library and entirely hidden from the applications. Both the client library and the server is heavily multithreaded. The fine-grained multithreading and the low latency messaging system make the GUI much more responsive than X11.

Not using X has its ups and downs. The big down is of course the lack of applications that can be easily ported to AtheOS. Another down is that the current GUI does not support remote display, even though implementing it should not be hard at all. The up's is that the GUI interface is much more high-level, and is much better at defining how a GUI should work. This leads to better consistency between applications. Drag and drop, clipboard, and other forms of high-level communication between applications are defined by the OS. This will hopefully lead to applications that work well together and that give the user an impression of a complete system with consistency between applications. I believ this consistency is important so the user doesn't have to start from scratch each time she learns a new program to know.

The AtheOS GUI consists of two main components: An application server and a dll providing a C++ interface between the server and the application. The GUI is therefore programmed through a C++ API providing windows containing a hierarchy of widgets that all have their own graphical environment.

The kernel was written from scratch. It supports SMP (Symmetric Multi Processing), has a built-in network TCP/IP stack. It supports loadable device-drivers and file-systems. It provides threads and processes with several powerful communication systems that makes it easy, efficient and safe to create server/client implementations where both the server and the client run on the same machine. Threads can communicate through message ports (most common), shared memory, posix signals, semaphores, named and anonymous pipes, pty's, TCP/IP, and probably a few other methods as well.

Unlike many people seems to believe AtheOS is *not* a BeOS clone. The two OS's are not compatible at binary level nor source-code level. Making a BeOS clone has never been a goal (I started working on AtheOS before the first BeBox was shipped), it is not a goal now, and it will not be a goal in the future.

If you have any questions or comments you can reach me at kurt@atheos.cx

I have zero tolerance for zero-tolerance policies.

AtheOS is a free desktop operating system (currently) under the GPL lisence. AtheOS currently run on Intel, AMD and other compatible processors and support the Intel Multi Processor architecture. I have seen quite a few anouncements of "promising" OSes with "great potential" during the development of AtheOS. The problem is that when I follow the links I normally find a description of the concept, a floppy-bootloader written in assembly, and not much else. AtheOS is a bit more mature, and is already running quite a lot of software. This server for example is running AtheOS. The HTTP server is a AtheOS port of Apache, and most of the content is generated by the AtheOS port of PHP3 and perl.The native AtheOS file system is 64-bit and journaled.

AtheOS is not meant to be a new Unix clone (like Linux and *BSD) but a new clean desktop OS. It does support large parts of the POSIX standard and hence are able to run most of the UNIX CLI tools and it comes with a standard UNIX shell (BASH) but this does not compromise anything in AtheOS as a desktop OS. AtheOS have a integrated GUI that works in conjunction with the kernel and various other components to create a complete and consistent system. The GUI is server/client like X11 but communicate through the native messaging system and the protocol is private to the server and client library and entirely hidden from the applications. Both the client library and the server is heavily multithreaded. The fine-grained multithreading and the low latency messaging system make the GUI much more responsive than X11.

Not using X has its ups and downs. The big down is of course the lack of applications that can be easily ported to AtheOS. Another down is that the current GUI does not support remote display, even though implementing it should not be hard at all. The up's is that the GUI interface is much more high-level, and is much better at defining how a GUI should work. This leads to better consistency between applications. Drag and drop, clipboard, and other forms of high-level communication between applications are defined by the OS. This will hopefully lead to applications that work well together and that give the user an impression of a complete system with consistency between applications. I believ this consistency is important so the user doesn't have to start from scratch each time she learns a new program to know.

The AtheOS GUI consists of two main components: An application server and a dll providing a C++ interface between the server and the application. The GUI is therefore programmed through a C++ API providing windows containing a hierarchy of widgets that all have their own graphical environment.

The kernel was written from scratch. It supports SMP (Symmetric Multi Processing), has a built-in network TCP/IP stack. It supports loadable device-drivers and file-systems. It provides threads and processes with several powerful communication systems that makes it easy, efficient and safe to create server/client implementations where both the server and the client run on the same machine. Threads can communicate through message ports (most common), shared memory, posix signals, semaphores, named and anonymous pipes, pty's, TCP/IP, and probably a few other methods as well.

Unlike many people seems to believe AtheOS is *not* a BeOS clone. The two OS's are not compatible at binary level nor source-code level. Making a BeOS clone has never been a goal (I started working on AtheOS before the first BeBox was shipped), it is not a goal now, and it will not be a goal in the future.

If you have any questions or comments you can reach me at kurt@atheos.cx

I have zero tolerance for zero-tolerance policies.