Xref: utzoo comp.os.minix:8083 comp.protocols.nfs:557
Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!lll-winken!ncis.tis.llnl.gov!helios.ee.lbl.gov!nosc!crash!pnet01!jca
From: jca@pnet01.cts.com (John C. Archambeau)
Newsgroups: comp.os.minix,comp.protocols.nfs
Subject: Re: NFS service
Message-ID: <770@crash.cts.com>
Date: 26 Nov 89 08:36:01 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 44

al@escom.com (Al Donaldson) writes:
>jca@pnet01.cts.com (John C. Archambeau) writes:
>>  thurlow@convex.com (Robert Thurlow) writes:
>>  >...  Further, RPC, on which NFS is based, can
>>  >be had in the public domain, which removes a lot of the nasty work.
>> The moral to the story is "why reinvent the wheel?"  ...
>
>I'm just now starting to read the background papers on Amoeba,
>but it seems to me there's been a lot of work done there to provide
>the same kind of capability you're asking for, i.e., remote files.
>Why not use Amoeba networking *instead of* NFS (see recent postings 
>on Suns, etc), or use Amoeba RPC as a base for NFS?   
 
Because of TCP/IP.  Everything out there runs on TCP/IP.  Rather than porting
Amoeba over to every platform that already has TCP/IP available already, why
not implement TCP/IP for Minix?  Doing one job for one OS is a lot simpler
than doing one job for many OS'es.  I'd much rather implement TCP/IP for Minix
rather than implement Amoeba for everybody else.  The reasoning is what is
considered the de facto standard out there.  TCP/IP is the de facto standard
out there for Suns.  Go out and run traffic and you'll see TCP and UDP.  I
don't know what the hell Amoeba uses, but since there are some PD TCP/IP
implementions out there with source for the IBM PC, it should not be that hard
to hammer into Minix unless of course they won't run in a 64K text and data
space.  If this is the case, then I don't expect to see TCP/IP until Minix
386 is out (probably won't be too far off since the price of 386SX
motherboards are about $100 to $200 more than 286 motherboards) and GNU C is
ported over or some masochist implements a large model C compiler for the 286
and modifies Evans' Protect Mode kernel to support large model programs.  Of
course, then there's the problem of which ethernet boards will be supported
and who's going to write the ethernet card driver.  Do we go 3 Com, Western
Digital, or ???

 /*--------------------------------------------------------------------------*
  * Flames: /dev/null (on my Minix partition)
  *--------------------------------------------------------------------------*
  * ARPA  : crash!pnet01!jca@nosc.mil
  * INET  : jca@pnet01.cts.com
  * UUCP  : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca
  *--------------------------------------------------------------------------*
  *         Apple Computer, Inc. is really the Anti-Christ!
  *--------------------------------------------------------------------------*
  * Note  : My opinions are that...mine.  My boss doesn't pay me enough to
  *         speak in the best interests of the company (yet).
  *--------------------------------------------------------------------------*/