Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!tim@lll-crg.ARPA@hoptoad.UUCP
From: tim@lll-crg.ARPA@hoptoad.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Need information on NFS
Message-ID: <8612210934.AA03714@hoptoad.uucp>
Date: Sun, 21-Dec-86 04:34:39 EST
Article-I.D.: hoptoad.8612210934.AA03714
Posted: Sun Dec 21 04:34:39 1986
Date-Received: Sun, 21-Dec-86 14:35:16 EST
References: <8612201638.AA08140@bu-cs.bu.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: hoptoad!tim (Tim Maroney)
Organization: Centram Systems, Berkeley
Lines: 17
Approved: tcp-ip@sri-nic.arpa

Unfortunately, the current crop of 512K and 640K micros are not going to
magically evaporate when the technology improves.  IBM offers no upgrades,
and Apple's are priced too high for large nets to make them on a general
basis.  We still have VAXen even though you can buy a better machine for
under $30K these days, after all.

Also remember that the 100K estimate was for a client RPC only.  I don't
know how much an NFS client itself would add, nor an RPC server and NFS
server.  A complete NFS implementation would surely strain even a one
megabyte Mac+ or (hypothetical) MS/DOS version 5 machine.  For instance, the
Mac Programmer's Workshop (a Greenhills C compiler with a scaled-down but
still powerful UNIX subset) requires over 800K.  This means you couldn't
have NFS installed during program development.
-- 
Tim Maroney, Electronic Village Idiot
{ihnp4,sun,well,ptsfa,lll-crg,frog}!hoptoad!tim (uucp)
hoptoad!tim@lll-crg (arpa)