On Fri, Oct 04, 2002 at 11:25:23AM -0700, JohnMaloney at earthlink.net wrote:
> 
> I think building on an OS kernel (such as OSKit, as Tim mentioned) is a
> great approach. It gives you excellent control all the way down, but you
> can share device driver code with others working on that kernel.
> 
> Like Tim, I thought someone out there was doing exactly this. If so, I'd
> love to know how it works out.
> 

I did a OSkit-based kernel some time ago. But this was only a weekend
projekt. (It took longer to compile OSKit than to do anything else...)

I've put the stuff at

ftp://ftp.ira.uka.de/pub/squeak/SqueakOS
(I really should rename this...)

the diskimage can be written to a 1.44MB floppy with 
ftp://ftp.ira.uka.de/pub/squeak/demo/rawrite2.exe and the thing should
boot on a intel-PC.

The Squeak used is Paul Fernaut's embedded Squeak 2.2 (which had a simple
command-line interface). 

OSKit seems to be really nice... you can tailor the kernel just as you
need it, the squeak-kernel uses a very minimal configuration, it's more
like a boot-loader (no Virtual Memory, no Filesystem, not even a scheduler).

But all things needed for a real powefull OS are there: Filesystems,
Networking, Display, Threads, ... and you can simply link with Linux or 
FreeBSD drivers. 

    http://www.cs.utah.edu/flux/oskit/


    Marcus


-- 
Marcus Denker marcus at ira.uka.de  -- Squeak! http://squeakland.org