> > To start with, there IS the beginnings of a TCP/IP stack. I think the
> > author managed to get it to reply to pings, but I'm not sure if he did or
> > not. The big problem is that we're very tight on memory space, so the
> > code has to be small.
> >
>
> TCP/IP stacks under ELKS have so far clearly demonstrated the benefit of
> sharing code, and releasing early in on Open Source project. At least two
> people working on code for the project for a while by themselves, have lost
> their own copies and then given up rather than starting again from scratch.
>
> A plea to anyone working on code for the project:
>
Where abouts is the existing tcp/ip stuff? I would like to keep a close
eye on its development as a sort of educational process, and maybe even
help.
I've been looking through the actual linux tcp/ip code, and there is a lot
of stuff to do. I presume that the plan would be to keep the way
networking ticks as similar to the full linux method as possible (but cut
down for size reasons).
Luke(Boo) Farrar.
