Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!image.soe.clarkson.edu!news From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.dcom.lans Subject: Re: PC/NFS and NCSA Telnet reprised Message-ID: Date: 23 Aug 90 01:14:58 GMT References: <1990Aug20.185329.8200@naitc.uucp> <999@ncis.tis.llnl.gov> Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 23 In-reply-to: paik@lance.tis.llnl.gov's message of 22 Aug 90 18:40:11 GMT In article <999@ncis.tis.llnl.gov> paik@lance.tis.llnl.gov (Yunki Paik) writes: In article ssw@cica.cica.indiana.edu (Steve Wallace) writes: >The packet driver will NOT allow you to run PC-NFS and NCSA >telnet at the same time. The packet driver doesn't support more >that one application using the same ethernet type. There is a Ironical. The very reason for the packet driver is for sharing the device through the common interface. I have not used packet driver much, but I once used it with NCSA telnet all right. Again, I don't know if PC-NFS is aware of the packet driver. If it is, then they should coexist fine. Yes, your self-admitted ignorance shows. The packet driver is for sharing the device with *different* protocols, not the *same* protocols. The only way to run NCSA Telnet over PC-NFS is for NCSA Telnet to *use* PC-NFS. That is, if you want to avoid booting. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) Russ.Nelson@$315.268.6667 We won the cold war. The Russians spent trillions defending their stuff, then they found that they didn't have any stuff. Will we avoid the same trap?