Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!ico!ism780c!wilbur!jon
From: jon@wilbur.uucp (Jonathan C. Broome)
Newsgroups: comp.os.minix
Subject: Re: TCP/IP and PC Minix
Summary: it can be done
Message-ID: <1990Apr09.083238.23610@wilbur.uucp>
Date: 9 Apr 90 08:32:38 GMT
References: <2137@crash.cts.com>
Reply-To: jon@wilbur.UUCP (Jonathan C. Broome)
Organization: Wilbur's Bike Shop, Westlake Village, Ca
Lines: 22

In article <2137@crash.cts.com> jca@pnet01.cts.com (John C. Archambeau) writes:
: coxj@tusun2.knet.utulsa.edu (Jason Cox  [UCRIG]) writes:
: >Has anyone attempted a TCP/IP implementation for MinixPC?
[ stuff ]
: I don't think KA9Q will port because of the memory model of the compiler.  The
: first thing one should try is try making it run in a small memory model (or
: split I&D) and if it works then try cross compiling it to Minix or running
: Minix's CC through it.


Well, it shouldn't be totally impossible to do -- my '286 system is running
a slightly modified Minix 1.2+ (I know, ancient!) that just happens to boot
(diskless) using RARP & TFTP and accesses all of its filesystems via a
WD8003E ethernet card using a UDP-based filesystem protocol.  It doesn't do
TCP (yet), but it does all the rest (IP, ICMP, UDP, ARP/RARP, etc.)  The
kernel is 64,928 bytes large, with both XT & AT wini drivers, a mouse driver,
and virtual consoles crammed in for good measure.  (Hence the delay in
updating to v1.5.5)

  ---Jonathan Broome
  jon@wilbur.uucp
  ...!uunet!ism780c!wilbur!jon