Xref: utzoo comp.protocols.nfs:2035 comp.sys.novell:915
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!newstop!exodus!appserv!sun!amdcad!brahms!phil
From: phil@brahms.amd.com (Phil Ngai)
Newsgroups: comp.protocols.nfs,comp.sys.novell
Subject: Re: Sun PC-NFS deficiencies
Message-ID: <1991Mar19.011129.16541@amd.com>
Date: 19 Mar 91 01:11:29 GMT
References: <1991Mar15.173934.18700@novell.com> <20305@ists.ists.ca>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices, Inc; Sunnyvale, CA
Lines: 16

In article <20305@ists.ists.ca> aronb@gkcl.UUCP (Aron Burns) writes:
|To expand:  in a large network, systems professionals will
|have to be in attendance anyway.  I'd rather have them setup
|the user's machine at lunch-hour and allow the user to continue 
|with whatever tasks he/she is charged with.  Most data-entry 

You can do that with Novell too. With Sun PC-NFS, you really
ought to if you don't want your server to crash. With Novell,
you don't have to (for the average user.)

The guy who crashed our server is no data-entry clerk, he's
fairly inteligent and could have handled a Novell install,
but not a Sun PC-NFS install without spending a lot of time.

--
The Macintosh makes it easy to do sloppy work.