Xref: utzoo comp.protocols.nfs:1991 comp.windows.ms:10396 comp.protocols.tcp-ip.ibmpc:5195 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!jethro!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: <1991Mar16.012844.19618@amd.com> Date: 16 Mar 91 01:28:44 GMT References: <1991Mar13.180625.14540@amd.com> <20171@ists.ists.ca> Sender: usenet@amd.com (NNTP Posting) Organization: Advanced Micro Devices, Inc; Sunnyvale, CA Lines: 34 In article <20171@ists.ists.ca> aronb@gkcl.UUCP (Aron Burns) 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. | |At recent presentation, an HP rep indicated that |the IIIsi would talk IP shortly. It's a great concept, as But Novell is first. As you imply, to use TCP/IP with PC-NFS will require double traffic. |>configure the printers, select servers, and server queues |>FROM A MENU. A crippled network like PC-NFS requires you to |>manipulate configuration files so cryptic most users never figure | |Not at all. Run NFSCONF. It changes the configuration files FROM A MENU |and has pretty colours as an added bonus. Sorry, I was talking about Windows and meant Windows menus, not some Sun menu (which you have to run from DOS). |so who let him configure his own machine? Who could expect a user |to understand an IP address and pick a machine name? You do this |once on initial install. And you're missing the point. Unix bigots only know how it is done in Unix and can't imagine other systems having an easier way to do something. In Novell, you don't have to mess with IP addresses or machine names (or Novell addresses). You choose servers (when you want to change) from a menu of available servers. -- The government is not your mother. The government doesn't love you.