Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!iconsys!caeco!i-core!geo-works!bryan
From: bryan@geo-works.UUCP (Bryan Ford)
Newsgroups: comp.protocols.tcp-ip
Subject: Followup to Ignorant Question
Message-ID: <1865.AA1865@geo-works>
Date: 19 Jul 89 12:30:09 GMT
Reply-To: geo-works!bryan@i-core.UUCP
Followup-To: comp.protocols.tcp-ip
Lines: 23

Thanks to everyone who responded to my question!  I sent replies to all the
messages I received, but my mailer just messed up and some might have
gotten lost, so forgive me if you didn't get a response.

Anyway, sorry for boring everybody with a beginner's question. :-)  Now,
another question.  (Uh oh... :-)  About what does it take to implement
TCP, IP, and a few of the "normal" ULPs (FTP, etc.) and possibly NFS?  Is
there public domain source code out there for these protocols that I could
port?  About how much memory and disk space could these beasties be
expected to eat up on a 68xxx-based system?

I'm considering implementing TCP/IP rather than 'doing my own thing', but
if it would take years to program and megabytes to run, I'd rather give up
the standardization.

				Bryan

--

     _______________________________________
   _/   Bryan Ford - bryan@geo-works.uucp   \_
 _/  ..!utah-cs!caeco!i-core!geo-works!bryan  \_
/ ..!uunet!iconsys!caeco!i-core!geo-works!bryan \