Path: utzoo!attcan!uunet!fernwood!apple!bionet!agate!ucbvax!yuba.UUCP!hwajin
From: hwajin@yuba.UUCP (Hwa Jin Bae)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  TCP/IP Source Code Search
Message-ID: <9011052355.AA28967@yuba.WRS.COM>
Date: 5 Nov 90 23:55:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

>Many people use the Berkeley code as a start. It's an excellent
>protocol engine; its main drawback is that it really really wants to
>live inside a UNIX kernel. It often takes many man-months to port
>properly. You can find it on uunet.uu.net for anonymous FTP.

berkeley code is actually pretty portable.  it's really not that hard
to port berkeley code to non-unix environment.  you need to write a set
of compatible routines -- spl*(), splx() can be emulated using semaphores,
timeout() can be emulated in most operating systems that support 
watchdog timers of some sort, sleep() (kernel version) can be done
via a semaphore or mailbox, wakeup() the same way, perror() and panic()
are trivial, cluster mbuf can be emulated if you change the mbuf structure
slightly even on systems that lack virtual memory, etc.   i'm speaking
from my experience... your mileage may vary.

hwajin