On Fri, 9 Jul 1999, Alistair Riddoch wrote:

> Hi all,
> 
> I have just spent the day hacking, and have finished off some bits and
> pieces, and commited them into CVS. As CVS mail reporting doesn't seem to
> be wroking while doa.org is down, here is a summary of what I have
> commited.
> 
> 
> Tweaked the bioshd driver to make sure it still works when hd is disabled.
> 
> Added byteorder functions required by romfs. romfs now compiles, but does
> not seem to work yet.
> 
> Added a basic pseudo tty driver. This almost certainly does not work in a
> standard way, but was enough for me to hack together a terminal program for
> nano-X.
> 
> Loads of socket code. I have added lots of code from Linux 1.2 which gives
> elks the socket layer api, and I started on getting unix sockets working
> under ELKS. I also took the unix socket code, and used it to write code for
> a new type socket called nano sockets. These work very like unix domain
> sockets, but they don't use a filename as their address, they have a single
> integer as their address instead. This makes the code very small and
> simple. I have tested these, and they appear to work. The main purpose to
> this socket family is to provide an inexpensive way of running nano-X on
> ELKS.

Nice one. On the subject of sockets my holidays are finally here, and I'm
gonna play some more with TCP/IP. It would be a lot easier though if I new
how to link the kernel up to the user space network stack.

Could people give me a few hints on this?

Luke(Boo) Farrar.


Reply via email to