Xref: utzoo comp.protocols.nfs:1960 comp.windows.ms:10273 comp.protocols.tcp-ip.ibmpc:5170
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!appserv!sun!amdcad!brahms!phil
From: phil@brahms.amd.com (Phil Ngai)
Newsgroups: comp.protocols.nfs,comp.windows.ms,comp.protocols.tcp-ip.ibmpc
Subject: Re: Sun PC-NFS deficiencies
Message-ID: <1991Mar14.021926.2340@amd.com>
Date: 14 Mar 91 02:19:26 GMT
References: <1991Mar13.180625.14540@amd.com> <1991Mar13.192701.21148@ccad.uiowa.edu>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices, Inc; Sunnyvale, CA
Lines: 42

In article <1991Mar13.192701.21148@ccad.uiowa.edu> cadsi@ccad.uiowa.edu (CADSI) writes:
|> You can print to an HP Laserjet IIIsi over the Ethernet directly,
|> something Sun PC-NFS could never do, since the LJIIISi talks Novell.
|...
|> You can also print to the Intel Netport devices. Again, they speak
|> Novell only.
|
|Hmmm...  I wonder if we could find a solution???  If you set a port
|as raw on the UNIX side, would this printer then work???  I have printed
|to other binary devices, maybe...

You don't understand. These devices talk Novell. No TCP/IP at all.
Setting raw is something you do with RS-232, I believe. Which you can
do with the LJIIIsi (but not the Intel Inport), but then instead of
10,000,000 bits per second, you're down to 9,600 bits per second. And
only the physically attached host can control it. If the host goes
down or runs out of spool space or some bozo fires up a zillion NFS
copies and makes the host go catatonic, too bad. With the LJ IIIsi,
any Novell node can use it as long as the Ethernet cable isn't
shorted out or something drastic like that. A big improvement in
reliability.

|Actually PC-NFS has a menu driven interface to manage these files.

But not a Windows menu. And it won't give you a choice of
servers and printers to use, you have to know their names
already. Another example of not being user friendly.

|> PC-NFS requires you to choose a name for your machine. One user
|> chose the name of our server. He wasn't malicious, just confused.
|> He crashed the server.
|
|Hmmmm... could this have been an old PC-NFS version.  I had three machines
|called the same thing for a time when we screwed up.  The SGI server
|never crashed, but PC-NFS did complain a lot about breaking laws of
|licensing and whatnot on the PC screens across the network.

This happened pretty recently.

--
The government is not your mother.
The government doesn't love you.