HDTenEightyP/NetNews huggingface dataset:
From: kjetilo@bilbo.uio.no (Kjetil Otter Olsen)
Subject: Re: Keyboard-mapping with PC-NFS 4.0
Organization: University of Oslo
Date: Thu, 30 Jul 1992 08:47:06 GMT



>Subject: Keyboard-mapping with PC-NFS 4.0
>From: per@teknologi.agderforskning.no (Per Sigmond)
>Date: Thu, 30 Jul 1992 07:03:16 GMT
>
>Sun have changed their telnet-implementation from 3.5 to 4.0 versions, and the
>method for keyboard-mapping and character-translation changed with it. I have
>found out that the mapout-command does character-translation, but how do I map
>certain characters to be sent from certain keys? (I know about the altkey-command
>but it doesn't quite do the job.)
>
>Thanks. Per.

A well known "feature"..........

On page 131 in the PC-NFS 4.0 Reference manual it says:

  ...(No mapping of keyboard input is performed.)...

Which is a pitty for us non-english speaking..... We have approx. 1500
PC-NFS users wanting to upgrade here at the University of Oslo, but we
hesitate because of the lack om keyboard mapping in Telnet.

A while ago I contacted both our Norwegian SUN-retailer and SunSelect
directly to get a version with keyboard mapping features. To date
I have not seen any fixes or heard of any plans for it :-(

Hopefully something will emerge soon, very soon!


--Kjetil

-----
Kjetil Otter Olsen                            kjetilo@usit.uio.no
Senior Communication Engineer,     M.Sc.,   C.Sc.
University Center for Information Technology Services (USIT)
University of Oslo, PoBox 1059 Blindern, N-0316 Oslo, Norway
Phone:                  +47-2-45 34 88,       Fax:   +47-2-45 37 30
After 10th August:      +47-2-85 24 88,       Fax:   +47-2-85 27 30
-----
From: ronald@lowt.phys.tue.nl (Ronald Aarts)
Newsgroups: comp.protocols.nfs
Subject: pcnfsd version 2 on a RS/6000
Summary: Has anybody successfully ...
Keywords: PC/NFS
Date: 22 Jul 92 08:35:45 GMT

I tried to install the new version of the PC/NFS daemon on our RS/6000
(Aix 3.1.5). I changed the Makefile according to the README-file that
was included on my PC/NFS 4.0 floppies:
  CFLAGS= -g -DUSER_CACHE -DWTMP -DUSE_YP -D_BSD
But it goes wrong with the first file:
           cc -DUSER_CACHE -DWTMP -DUSE_YP -D_BSD -c pcnfsd_svc.c
         405 |                         getrlimit(RLIMIT_NOFILE, &rl);
               ..................................a...................
   a - 1506-045: (S) Undeclared variable.
Is there somebody out there who successfully compiled this daemon on a
RS/6000 ???

Please replay by E-mail as I don't read this group that often.
--
Ronald Aarts
Eindhoven University of Technology  | Internet: ronald@lowt.phys.tue.nl
Physics Department, P.O. Box 513,   |    Phone: +.31.40.474213
5600 MB Eindhoven, The Netherlands  |      Fax: +.31.40.453587
Newsgroups: comp.protocols.nfs
From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
Subject: Re: PC-NFS 4.0, RTM, Heap size
Date: 31 Jul 1992 17:48:25 GMT
Organization: SunSelect
NNTP-Posting-Host: tyger.east.sun.com

Quoth kjw@doc.ic.ac.uk (Kevin J Walters) (in <1992Jul30.143320.5227@doc.ic.ac.uk>):
#
#There are quite a few computers i've come across which are loading rtm
#with the parameter '/heap 64'. I had a look in the manuals and found 
#the value to be 64k, as i suspected, so basically rtm is using up 64k
#plus the resident portion of that oh-so-precious ram.
#
#The manual gives a defualt of 22k if the heap option isn't specified - is
#there any reason for a heap as large as 64k?
#
#I suspect it all comes down to efficiency, but there must be a more
#reasonable balance between memory use and nfs performance.
                                           ^^^
Minor clarification: the heap size does not affect NFS performance: only
the performance of Toolkit apps. (Remember that in PC-NFS the NFS
client is embedded, along with some RPC/XDR and a subset of UDP) in
the PCNFS.SYS driver. 

Geoff
--
Geoff Arnold, PC-NFS architect | In the years after WW2 it was said that Oxford
  (geoff.arnold@East.Sun.COM)  | philosophers had found a cure for atheism.
         SunSelect,            | Young people coming up as atheists soon found
  a Sun Microsystems Business  | that they no longer knew what to disbelieve...
Newsgroups: comp.protocols.nfs
From: cohen@lindsay.psychiatry.uiowa.edu
Subject: pcnfs 4.0 and stacker
Date: Tue, 28 Jul 1992 19:33:56 GMT
Organization: University of Iowa

I have been trying desperately to get my PCNFS working again after
"stacking" my hard drives.  I get a wierd little happening when the
PC is reading my config.sys file:

it gets to the device loading statements for the PCNFS and..

bad or missing EVICE=C:\LANMAN\PROTMAN.DOS
DEVICE=C:\LANMAN\HPLAN.DOS
DEVICE=C:\LANMAN\NFS-NDIS.SYS
stacks=9,256

ERROR in CONFIG.SYS line 25

bad or missing EVICE=C:\LANMAN\HPLAN.DOS
DEVICE=C:\LANMAN\NFS-NDIS.SYS
stacks=9,256


error in config.sys line 26

...
.
.
etc

and then it just keeps telling me that there are (unrecognized command) errors
in the config.sys for lines 30-~60 (there are no such lines...)
and then tells me that it can't find and appropriate command.com
"bad or missing command interpreter"

What gives?  Shouldn't this stuff all work together, or did I misunderstand
something..


thanks
gregg
From: uresh@ovrbid.lkg.dec.com (Uresh Vahalia)
Newsgroups: comp.protocols.nfs
Subject: lockd
Date: 21 Jul 92 17:47:21 GMT
Organization: Digital Equipment Corp.


I have a few questions about the lockd protocol, which I am trying to
implement:

1.  There seem to be 3 flavors of each request - eg. for the lock
request, there is 
    nlm_lock, nlm_lock_msg and nlm_lock_res.  Why?  What are the differences?
2.  What are the version 3 requests for (share, unshare, nm_lock and free_all?)
3.  What is the function of the cookie argument in all the calls?
4.  What does the svid argument mean?

Can anyone point me to any document which gives me a high level description of
the protocol (besides just the uncommented spec?).


Uresh Vahalia
Newsgroups: comp.protocols.nfs
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Subject: Re: lockd
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Wed, 22 Jul 1992 00:20:54 GMT

In article <14hpi3INNppo@seven-up.East.Sun.COM>, geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
> ...
> Why? Because back in 1986 it wasn't practical to create a multithreaded
> lock manager.


This is the first even remotely official statement I've heard that any
of the various versions of lockd owe much to the simple locking demo
program shown at USENIX or whatever in Feb (I think) 1986.  By
listening to what was said in meetings of B.Lyons' group at the time, I
inferred that it was not intended to be a product.  Are you referring
to the same demo?

It was not <<technically>> "impractical to create a multithreaded lock
manager" in 1986.  Perhaps no one had the time or inclination, but it
was certainly technically feasible.  "Multi-processing", "threads",
and so on have not changed much since 1986.  It is true that more
companies are shipping multi-processor UNIX systems today, but that is
not relevant.  You don't need more than one processor for a
multi-threaded program.  You don't need klunky things like System V
shared memory and semaphores, which were around in 1986 and might have
been in SunOS--I don't remember.  Lockd on SunOs of that vintage could
probably have used vfork(), although that would have been somewhat kludgy.


Vernon Schryver,  vjs@sgi.com
Xref: sparky comp.protocols.nfs:1960 comp.protocols.tcp-ip:3847 comp.protocols.tcp-ip.ibmpc:4439 comp.sys.ibm.pc:321 comp.unix.ultrix:5909
From: dmiller@dragon.tricity.wsu.edu (David L. Miller)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc,comp.sys.ibm.pc.net,comp.unix.ultrix
Subject: Paradox over TCP-IP/NFS
Date: 27 Jul 92 18:51:32 GMT
Organization: Washington State University Tri-Cities, Richland
Originator: dmiller@dragon.tricity.wsu.edu

We are attempting to run Paradox on our network, but we are only running
TCP/IP (no Novell, ...).  Specifically, we are running PC/TCP version 2.05
with Interdrive on our PCs.  The server is a DECsystem 5000/200 running
Ultrix 4.2.

Following is a description of the problem from our Database Administrator,
please respond to her directly.

>From brunken@beta.tricity.wsu.edu Mon Jul 27 11:37:17 1992
>Date: Tue, 21 Jul 1992 14:35:02 -0700 (PDT)
>From: Cyndy Brunken <brunken@beta.tricity.wsu.edu>
>To: "David L. Miller" <dmiller@beta.tricity.wsu.edu>
>Subject: Paradox
>
>Paradox has a police file called PARADOX.NET.  When I try to load Paradox
>from the server I get the following error message:
>
>  "Can't start Paradox: unable to record lock/unlock e:\PARADOX.NET.  You
>   may have insufficient access rights to directory e:\"
>
>I have mounted as user root, and I still get this problem.  Paradox will
>run from the server, if I write the PARADOX.NET file onto my PC's hard
>disk.  The Paradox man from BCSR thought that it was a problem between UNIX
>lock/unlock protocols and Paradox.
>
>Do you need more?

-- 
*****************************************************************************
David L. Miller                       Internet: dmiller@beta.tricity.wsu.edu
Systems Programmer/Network Analyst      BITNET: MILLERD@WSUVM1
Washington State University Tri-Cities    UUCP: ...!yoda!dmiller
100 Sprout Road                          
Richland, WA 99352                       Phone: (509)375-9245
*****************************************************************************
From: jim@cs.strath.ac.uk (Jim Reid)
Newsgroups: comp.protocols.nfs
Subject: Re: what locking techniques work over NFS?
Date: 31 Jul 92 09:53:52 GMT
Organization: Computer Science Dept., Strathclyde Univ., Glasgow, Scotland.
In-reply-to: eggert@twinsun.com's message of 31 Jul 92 00:39:03 GMT

Another point which has been overlooked is that file attribute
cacheing by clients and servers mean that there is a sizeable window
when two machines may see a different picture of the same directory:

	Client A reads a directory
	Client B creates the lock file in that directory
	A checks the directory for the lock file, but gets the answers
	from its file attribute cache instead of from the file server.
	Since A sees no lock file.....

		Jim
From: johng@uniwa.uwa.edu.au (John Gibbins)
Subject: PC/NFS 4.0 telnet can't hotkey out?
Organization: University of Western Australia
Date: Wed, 22 Jul 1992 04:10:40 GMT

After installing PC/NFS 4.0a, we find that F10 no longer allows us to
exit telnet and leave the connection in memory.  I remember reading a
while ago that this was due to the function keys sending vt200(?) escape
sequences so the hotkey function had to be moved to another key.

I cannot find any mention of this in the manual.
Does anyone know what the new hot key is?
Does this feature still exist?

Please reply by mail to johng@chi.uwa.edu.au as I am having problems
reading news lately.

thanks
johng
--
John Gibbins                           The Western Australian Research Institute
The University of Western Australia      for Child Health Ltd     ,-_|\
email:  johng@chi.uwa.edu.au           GPO Box D184              /     \
Phone:  +61-9-3408547                  PERTH  W.A. 6001          *_,-._/
Fax:    +61-9-3883414                  AUSTRALIA                      v
"Nothing is foolproof as fools are so ingenious"
-- 
John Gibbins                           The Western Australian Research Institute
The University of Western Australia      for Child Health Ltd     ,-_|\
email:  johng@chi.uwa.edu.au           GPO Box D184              /     \
Phone:  +61-9-3408547                  PERTH  W.A. 6001          *_,-._/
Newsgroups: comp.protocols.nfs
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Subject: Re: NFS I/O Ops/seconds
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Thu, 23 Jul 1992 00:34:08 GMT

In article <l6r4uvINNf0p@exodus.Eng.Sun.COM>, beepy@tabitha.Eng.Sun.COM (Brian Pawlowski) writes:
> ...
>
> The number "300 NFS ops/s per ether" is a rule-of-thumb
> ...


Yes, everyone keeps saying, for ethernet.

One can hope to do significantly better on FDDI.

Imagine a multi-homed FDDI NFS server (>1 FDDI link), with FDDI-to-ether
routers or bridges that can run at ethernet speeds.


Vernon Schryver,   vjs@sgi.com
From: rmilner@zia.aoc.nrao.edu (Ruth Milner)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS I/O Ops/seconds
Date: 22 Jul 92 18:57:48 GMT
Article-I.D.: zia.1992Jul22.185748.852
Reply-To: rmilner@zia.aoc.nrao.edu (Ruth Milner)
Distribution: usa
Organization: National Radio Astronomy Observatory, Socorro NM

In article <64081@hydra.gatech.EDU> gt1111a@prism.gatech.EDU (Vincent Fox) writes:
>In <1992Jul22.061146.15641@u.washington.edu> kint@rio.engr.washington.edu (Rick Kint) writes:
>>	We're buying a Sun to serve as an NFS server in one of our departments.
>>The Sun rep commented that a typical Ethernet allows 300 NFS ops per second,
>>so if you're on a single wire any server bandwidth beyond that is wasted. 
>
>Hmmm. I'm a bit skeptical. All NFS operations are not created equal.
>A write obviously takes a lot longer to complete than a getattr. I've seen
>claims up to 1,000 or better. Auspex claims this I feel certain.

Not on a single Ethernet, they don't. You need 4 Ethernets to get these kinds 
of figures.

>>typical mix of operations; since a getattr is presumably quicker than a write

By a factor of about 15.

>>how useful are these numbers anyway?
>
>Not much. Sun reps usually know less than you do.

Yes, but the Sun reps don't run the benchmarks (thank god). In this case the
300 ops/sec/Ethernet maximum is about right for the default mix nhfsstone uses
(which is actually a pretty typical mix).

Quite honestly, I think 60 Suns on a single unsubnetted, unbridged Ethernet
is really pushing it. You won't get 300 NFS ops/sec out of a server that can't
get that much of the bandwidth, even if "all" it is providing is user files.
One of our users recently generated 4 *gigabytes* of NFS traffic between the 
server and his workstation in a 36-hour period, and that was sure not the OS 
or the application executables!
-- 
Ruth Milner                          NRAO/VLA                  Socorro NM
Computing Division Head      rmilner@zia.aoc.nrao.edu
Newsgroups: comp.protocols.nfs
From: jbvb@vax.ftp.com  (James B. VanBokkelen)
Subject: Re: Fast Fault Tolerant NFS Server
Nntp-Software: PC/TCP NNTP
Reply-To: jbvb@ftp.com
Organization: FTP Software, Inc., Wakefield, MA
Distribution: na
Date: Mon, 20 Jul 1992 11:17:27

In article <SHEPLER.92Jul7180529@gumby.austin.ibm.com> shepler@gumby.austin.ibm.com ( Spencer Shepler ) writes:

    So how does this system handle the case where both operating system
    decide to panic at the same time (or both system receive an NFS
    request that makes them crash).  In this case wouldn't the NFS
    clients lose data that has already been ack'd as written to disk?

Were I trying to do this, I'd first fix all the bugs that allowed the
machine to be crashed from the net.  The NFS reference implementation's
fragility isn't inevitable...

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901
From: bradshaw@ccvax.ucd.ie
Newsgroups: comp.protocols.nfs
Subject: Problem using Sun IPC as print server
Date: 29 Jul 92 17:28:42 GMT
Organization: University College Dublin

I have my SPARCStation IPC setup as a print server via PC-NFS 
Ver 3.5b. The printer I am using is a Hewlett Packard Laserjet
IIIP and is attached to the IPC's serial port /dev/ttya. 
It all works fine except for one small problem....at the end of 
every print job, it ejects a blank page. My configuration is as 
follows:
/etc/printcap on the IPC:
ljet:\
    :lp=/dev/ttya:br#19200:\
    :ms=pass8,ixon,raw:\
    :sh:\
    :sd=/var/spool/lpd:\
    :lf=/var/spool/lpd/log:

LaserJet config:

     AUTOCONT = OFF
     I/O = SERIAL
     BAUD RATE = 9600
     ROBUST IXON ON
     DTRPOLAR HI
     RET MEDIUM

NFSCONF
     Printer is set up for raw transmission.

Can anybody see what I might be doing wrong? Any ideas 
appreciated. My E-Mail addresses follow:

    CBRADH89@IRLEARN.UCD.IE
    BRADSHAW@CCVAX.UCD.IE
Help!!!!!
From: tbo@vector.dallas.tx.us (Terry Bohaning)
Newsgroups: comp.protocols.nfs
Subject: NFS problems
Date: 28 Jul 92 19:05:14 GMT
Distribution: usa
Organization: Dallas Semiconductor

Has anyone seen a recurrent problem with NFS running extremely slowly 
or not at all on their Suns.

Our network has an typical load of 4% to 5%. As the network moves above
5% the Suns start having problems communicating with each other via NFS.

I've adjusted rsize and wsize down as low as 1k. timeo as been varied.
Frankly, I'm ruuning out of ideas....

SUN finally told me after 3 weeks for minimal action that the DELNI's
(AUI fanout boxes) from DEC are not compatible with Sun's gear. Has
anyone else seen this???

Comments PLEASE.....

Thanks
Terry Bohaning    tbo@vector.dallas.tx.us
Newsgroups: comp.protocols.nfs
From: dwight@hyphen.com (Dwight Ernest)
Subject: Newbie Question: What's LADDIS? (was: Re: NFS I/O Ops/seconds)
Organization: Hyphen, Inc., Wilmington, MA 01887 USA / +1 508 988-0880
Date: Sun, 26 Jul 1992 16:53:50 GMT


I see a lot of reference being made to LADDIS and PRE-LADDIS.  Can someone
point me to a reference that would explain what that/those is/are?  Thanks.

-- 
--Dwight A. Ernest	Special Projects Engineer	I speak only for myself.
  Hyphen, Inc. / 187 Ballardvale St. / Wilmington, MA 01887 / +1 508 988 0880
  dae@world.std.com		dwight@hyphen.com
Xref: sparky comp.protocols.nfs:1939 comp.sys.sun.hardware:3515
From: numb@root.co.uk (Matthew Newman)
Newsgroups: comp.protocols.nfs,comp.sys.sun.hardware
Subject: Re: NFS I/O Ops/seconds
Date: 23 Jul 92 11:53:18 GMT
Organization: UniSoft Ltd., London, England
X-Address: Spa House, Chapel Pl, Rivington St, London EC2A 3DQ
X-Organisation: UniSoft Ltd
X-Quote: To imagine is everything. - Albert Einstein
X-Job: Systems Engineer
X-Phone: +44 71 729 3773 x215, Fax: +44 71 729 3273


Assuming a typical mix (does such a thing exist?) a friend of mine
and I did some very comprehensive NFS tests on a wide range of Sun
and non-Sun equipment, a small paper was submitted to the Nice EUUG
a few years ago.

From memory our mix was 10-15% writes lots of getattr and lots of reads.

The Sparc Servers at the time (SS2 type machines) with fast SCSI
disks gave a sustained 80/sec, various machines can in the 40 -
60/sec range, the EPOCH NFS server gave 70/sec and wait for it:-

The cheapest machine we tested: Sun SLC 86-92/sec. We spent six
months doing this, and at the end bought 6 SLC's and 7GB of disk,
I belive that they now have something like 15 SLC servers and about
20-30 GB of disk. They worked very well.
-- 

Matt Newman
From: coolidge@speaker.wpd.sgi.com (Don Coolidge)
Subject: Re: NFS I/O Ops/seconds
Organization: Silicon Graphics, Inc.
Date: Thu, 23 Jul 92 23:13:05 GMT

In article <1992Jul23.192203.12376@newshost.lanl.gov>, cwm@beta.lanl.gov (Christina W Mercier) writes:
|> In article <nkok0p0@rhyolite.wpd.sgi.com> vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:
|> >In article <l6r4uvINNf0p@exodus.Eng.Sun.COM>, beepy@tabitha.Eng.Sun.COM (Brian Pawlowski) writes:
|> >>
|> >> The number "300 NFS ops/s per ether" is a rule-of-thumb
|> >> 
|> >Yes, everyone keeps saying, for ethernet.
|> >One can hope to do significantly better on FDDI.
|> 
|> So does anyone have a start at a rule-of-thumb for FDDI????
|> Any results of default-mix NHFSSTONE benchmarks on FDDI would be 
|>   appreciated.

There's really no rule-of-thumb, because as yet nobody hits FDDI
bandwidth for any real applications (OK, maybe Cray excluded :^).
However...

Let's say your FDDI ttcp throughput can hit 6 Mbytes/sec (that's
less than 50% bandwidth, but very few FDDI implementations are
that fast yet). That's improvement over Ethernet throughput by
a factor of 6 (most boxes can saturate an Ethernet these days).
Since only roughly 1/3 of the nhfsstones default mix does reads
or writes, they are the only operations affected by medium bandwidth
(the others are basically latency-limited, which is about the same
for Ethernet as for FDDI - speed of light, ya know...). So, your reads
and writes would complete in 1/6 the time, and everything else would
be unchanged. Net result - the overall FDDI number is less than 
1.4 times the Ethernet number.

If your FDDI ran at a full 100Mb/sec (12.5 MB), the best you could
hope for would be improvement by a bit over a factor of 1.4.

Remember, FDDI has no effect (actually very little) on the IOPS 
for all latency-bound operations, only for reads and writes. So
even if you had infinite bandwidth, you'd never get a larger
improvement factor than 1.5 .

Somebody should have pointed this out to the guys specifying LADDIS;
their recommendations for adding resources (extra networks, for
instance) seem to think that because FDDI bandwidth is 10X Ethernet,
that means you'll get 10X your Ethernet nhfsstones numbers. Well,
it just ain't so.

Don Coolidge
coolidge@speaker.wpd.sgi.com
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.nfs
Subject: Re: nfs-client
Date: 31 Jul 1992 20:45:41 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
NNTP-Posting-Host: telecaster.think.com

In article <26026@sophia.inria.fr> Stephane.Boyera@crazy.inria.fr writes:
>I'm writing a nfs-client driver for macintosh. When i want to access a
>private file (read/write denied fo other) i need to fill the fields auth_unix
>and cred_unix in the rpc packet. Which protocol will do that ? (e.g enter the
>user name and password and get these fields)

There's no one protocol that does this, you have to emulate what Unix
normally does, by looking in /etc/passwd and /etc/group on the server.

If your site is using NIS (nee YP), you may also have to contact an NIS
server and look up the name in the passwd.byname map to get the user's
encrypted password, uid and primary gid, and then find all the user's
secondary groups by searching the group.byname or group.bygid map.
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar
From: cohen@lindsay.psychiatry.uiowa.edu
Subject: PCNFS on A/UX
Date: Thu, 30 Jul 1992 18:41:30 GMT
Organization: University of Iowa

I have been attempting to get PCNFS to compile on a Mac IIx running
System 7.0 and A/UX 3.0.  When I made the appropriate changes to the
Makefile (such as the SVR4 line in and BSD line out, and the library
changes) I get the following answer from the make.

lindsay.root # make
        cc -g -D SVR4 -DSHADOW_SUPPORT -c pcnfsd_svc.c
"pcnfsd_svc.c", line 405: RLIMIT_NOFILE undefined
Make: *** Error: Update of `pcnfsd_svc.o' terminated with exit code 1


So what have I done wrong, has anyone been able to get pcnfsd to run
on an Apple (don't ask why I am doing this, it's too long to relate)?

Thanks in advance

gregg
 
Newsgroups: comp.protocols.nfs,comp.sys.sun.hardware
From: kint@rio.engr.washington.edu (Rick Kint)
Subject: NFS I/O Ops/seconds
Organization: University of Washington, Seattle
Date: Wed, 22 Jul 1992 06:11:46 GMT

	We're buying a Sun to serve as an NFS server in one of our departments.
The Sun rep commented that a typical Ethernet allows 300 NFS ops per second,
so if you're on a single wire any server bandwidth beyond that is wasted. 

	I have no feel whatsoever for the numbers that go into this figure,
can anyone in netland (a) explain this in words of two syllables or less, and
(b) does anyone know the figures for current systems?

	I'm sure that this includes assumptions about what represents a 
typical mix of operations; since a getattr is presumably quicker than a write
(for example), how useful are these numbers anyway?

	ObCurmudgeonlyRemark:  I was reading about the SS10/41, with 1 MB of
cache.  Good Lord, a meg of cache on a workstation, why when I was your age
we thought a meg of *main memory* on a *mainframe* was a lot...


-- 
Rick Kint				UNIX Geek, College of Engineering
kint@engr.washington.edu		University of Washington, Seattle