Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!ucsd!nosc!crash!pnet01!jca
From: jca@pnet01.cts.com (John C. Archambeau)
Newsgroups: comp.os.minix
Subject: Re: TCP/IP and PC Minix
Message-ID: <2163@crash.cts.com>
Date: 10 Apr 90 04:59:59 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 34

jon@wilbur.uucp (Jonathan C. Broome) writes:
>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)

A lot of us would like to know exactly how you did that...

(Hint, hint...)
 
     // JCA

 /*
 **--------------------------------------------------------------------------*
 ** Flames  : /dev/null                     | My opinions are exactly that,
 ** ARPANET : crash!pnet01!jca@nosc.mil     | mine.  Bill Gates couldn't buy
 ** INTERNET: jca@pnet01.cts.com            | it, but he could rent it.  :)
 ** UUCP    : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca
 **--------------------------------------------------------------------------*
 */