Linked by Eugenia Loli-Queru on Sun 28th Jul 2002 05:32 UTC
Syllable, AtheOS The Syllable team makes strides these days on their AtheOS fork, and most of the AtheOS developers have joined Vanders and Rick to their quest of a better operating system. OSNews reader Daryl Dudey joined the Syllable team recently, and he already wrote a nice networking preference panel for Syllable. The team is still looking for a kernel developer though, or C++ developers who like writting low level system software. On a related hobby-OS note, SkyOS made its first steps into the SMP world.
Permalink for comment
To read all comments associated with this story, please click here.
ABrowse, Glibc & GCC 3.x
by Vanders on Sun 28th Jul 2002 10:24 UTC

The ABrowse source is in the CVS Repository, however I admit I didn't spend any time trying to get it to compile. CVS can do many wicked and subtle things to source code, not to mention we do not know the original runes used to compile it in the first place! The ABrowse package we provide is simply a gzipped tarball of the ABrowse directory from Atheos 0.3.7

Getting ABrowse up to date would be a "full time" job, in the sense that anyone taking on that work would wouldn't be able to simply do the work and then move onto something else. The code requires a dedicated maintainer. Its not just porting/updating khtml but it is also the GUI & things like cookies that also require work.

Its the same situation for Glibc, in fact. I've spent weeks on the Glibc source from the atheos.cx CVS, and it still won't compile. Something as large as Glibc really needs a full time hacker to keep it current. If anyone has experience of hacking Glibc, I'd be interested in any help you could offer! ;)

As far as GCC 3.x goes, anybody is free to do the port, and I would happily keep GCC 3.x as an official package. However, nobody really has the time to fix the GCC 2.x C++ (We already know there are some problems, as Bill Hayden went through them with Cosmoe). Everyone is rather more interested in bringing the GUI upto date and getting all of their ideas out and into the open.

Looking at the current work being done, what will probably happen is that we will continue to work on 0.4.x releases that will fix the various missing peices (The VM, GUI classes etc.) and then start some "modernisation" work for 0.5.x, E.g. moving to GCC 3.x, bringing Glibc & the development tools upto date etc. etc.