Xref: utzoo comp.protocols.nfs:1968 comp.windows.ms:10305 comp.protocols.tcp-ip.ibmpc:5175 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!gatech!wrdis01!wpdis01!hassler From: hassler@logdis1.hq.aflc.af.mil (Barry D. Hassler) Newsgroups: comp.protocols.nfs,comp.windows.ms,comp.protocols.tcp-ip.ibmpc Subject: Re: Sun PC-NFS deficiencies Message-ID: <105@logdis1.hq.aflc.af.mil> Date: 14 Mar 91 17:33:20 GMT References: <1991Mar11.232450.5556@amd.com> <1991Mar13.180625.14540@amd.com> Followup-To: comp.protocols.nfs Organization: Control Data @ HQ AFLC LMSC/SXSN WPAFB Lines: 69 In article <1991Mar13.180625.14540@amd.com> phil@brahms.amd.com (Phil Ngai) writes: >In article kv56962@tut.fi (V{{r{nen Kari) writes: ... >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. > >Doesn't Sun talk about being standards based? Novell is THE standard >in PC networks. I must object to this. Simply because a product is widely available does NOT make it a standard. Standards imply widely accessible, public specifications The above products you mention, while extremely attractive, are not viable options in environments where open competition and interoperability are required. > >With regard to Windows, a real PC network lets you inspect the >print queues, pause, resume, and delete jobs FROM A MENU. You can >configure the printers, select servers, and server queues >FROM A MENU. A crippled network like PC-NFS requires you to A "network" allows you to do non of the above. It is the implementation of software ABOVE the network which provides these capabilities. See the axiom about "solving problems at the right level - then you only have to solve them once". Neither Novell "network" or PCNFS "network" provide the above capabilities. Again, it is the implementation of software utilizing those network services. ... > >Now, the unix bigots will say "stupid user". That attitude is >a big part of the problem. But I don't know if it is possible >to make the unix bigots realize that. Most unix bigots would >never believe this kind of problem could be solved, should >be solved, and would not try. I'm a "UNIX bigot" I suppose, but I won't say stupid user. From your point of view (assuming you are a "user", and not a systems-type), the entire issue *is* part of the network, as it should be. The reality of the situation though is that they are completely separate. Your "system experts" should be providing this type of information to you and helping to ensure that you have the right set of tools to satisfy your needs. One of the nice things about NFS, is that it ISN'T limited to Unix (and neither is Novell limited to PCs). NFS is available on just about any platform you can name. Novell also works with UNIX, but as someone else pointed out, its usefullness on that platform may be questionable (I haven't used it myself on UNIX, so I can't say personally). IT MAY BE TRUE that PCNFS does not satisfy your needs, but that isn't a reflection upon PCNFS itself, but instead on those companies that have chosen to implement it. By the way, I have no vested interest in NFS. I do have an interest in assuring my clients are provided the best solution to their requirements. ------- Barry D. Hassler hassler@logdis1.hq.aflc.af.mil Networking and Systems Consultant (513) 257-4499 (WPAFB) Control Data Corporation DSN 787-4499 Integrated Information Systems "It is better to be blind than to be able to see but have no vision." - Helen Keller