Subject: COMP.PROTOCOLS.NFS FAQ (11/3/93) Back again from the blue. Here's version 1.5. Disclaimer: The material in this FAQ is not based on preferrence for any one product. All questions have been drawn from the archives of comp.protocols.nfs starting from the very beginning. To all distributers/ software houses: If you feel that there is unfair representation of your product in this list please mail me at: rawn@rtd.com or rawn@xray1.chem.arizona.edu or call: (602) 318-0696 [US] I have to admit that there is one bias. All addresses or phone numbers which do not state which country they are in, are in the US. I've been pretty oblivious about that. NOTE: If you use this FAQ list and decide you like a product listed here enough to purchase it, please mention where you got this information to the product seller. Thank you. Rawn Shah RTD Systems & Networking, Inc. Tucson, AZ ------------------------------------------------------------------------------- *. This FAQ *-1. What topics does this FAQ cover? *-2. Where can I get this FAQ? *-3. Who helped write this FAQ? *-4. Who maintains this FAQ? *-5. Who maintains comp.protocols.nfs? *-6. Where are the archives for comp.protocols.nfs? *-7. Trademarks and Registered names. *-8. What do the -, + and * before the questions mean? *-9. *Whats up and coming in the next issue of the FAQ list? The real FAQ: A. Basics A-1. What is NFS? A-2. What is (PC)NFS? A-3. Where can I get (PC)NFS for my DOS system? A-4. Where can I get (PC)NFS for my MS-Windows system? A-5. +Where can I get (PC)NFS for my Macintosh system? A-6. What is PC-NFS as opposed to (PC)NFS? A-7. What is TCP/IP? A-8. What is telnet? What is ftp? A-9. What is a client? What is a server? Why do I need them? A-10. Where can I get (PC)NFS cheap/free/PD? A-11. What is SOS & SOSS? Where can I get it? A-12. +Are there any free NFS clients available for DOS? A-13. What is SLIP? A-14. What is PPP? B. Setup B-1. *What are the different types of drivers available? B-2. -What are "shim"s? What shims are available? B-3. What are packet drivers? Where do I get them? B-4. Can I use packet drivers with (PC)NFS? B-5. +Can I run (PC)NFS over SLIP? B-6. Can I run (PC)NFS at the same time as Netware? B-7. Can I run (PC)NFS at the same time as CUTCP or NCSA Telnet? B-8. Can (PC)NFS run with NDIS drivers? B-9. +Can I use (PC)NFS to mount a diskless PC from a remote server? B-10. Can (PC)NFS run over token ring? B-11. Can I run PC-NFS with my 3C509 Etherlink III card? B-12. Can I run PC-NFS slip at higher baud rates than 9600? B-13. Can I access an MSCDEX CD-ROM with PC-NFS? B-14. Can I run NDIS over Packet drivers? B-15. *How does ODI compare to NDIS? C. Server C-1. What is pcnfsd? What is pcnfsdv2? C-2. +Where can I get pcnfsd for my server system? C-3. -What is lockd? C-4. How can I test NFS performance? C-5. What is NHFSSTONES? Where can I get it? C-6. -What will help my server increase performance? C-7. How many nfsd's & biod's should I run on my server? C-8. What is asynchronous I/O? How can I modify my NFS server system to use asynchronous I/O? C-9. What is a good NFS server? C-10. What is LADDIS? C-11. -What is XRemote & LBX? D. Applications D-1. +Where can I get mail with (PC)NFS? D-2. Where can I get news with (PC)NFS? D-3. Where can I get an FTP server? D-4. Where can I get rwalld for (PC)NFS? [May be removed, please read] D-5. Where can I get a INT-14 redirector for (PC)NFS? D-6. Where can I get YPPASSWD for PC-NFS? D-7. Where can I get IBM 3270 terminal for (PC)NFS? D-8. Where can I get an X-Windows server for (PC)NFS? D-9. -Where can I get a calender/scheduling program for (PC)NFS? D-10. +Where can I get a database that works with (PC)NFS? D-11. Where can I get a WAIS client for (PC)NFS? D-12. +Where can I get an archie for (PC)NFS? D-13. +Where can I get a gopher client for (PC)NFS? D-14. +Where can I get a WWW (World Wide Web) client for (PC)NFS? D-15. Where can I get X25 for (PC)NFS? D-16. Where can I get NEWGRP.EXE for PC-NFS? D-17. Where can I get AUTOCONF for PC-NFS? D-18. Where can I get a backup utiliy for (PC)NFS? D-19. Which (PC)NFS packages support DNS [named]? D-20. Where can I get a traceroute program? D-21. +Where can I get an LPD program? E. Problems & General Q&A E-1. -How can I load (PC)NFS into DOS high memory? E-2. Can I use DNS instead of NIS with PC-NFS? E-3. Why do some versions of (PC)NFS not follow symbolic links? E-4. PC-NFS v4.0 has trouble with Cntl-S, Cntl-Q. E-5. PC-NFS v4.0 has trouble with redrawing the window while in MS-Windows. E-6. +PC-NFS v4.0 doesn't allow me to access the local printer when I have network printers. E-7. I cannot delete any file that PC-NFS makes with a ~ (tilde) in it. E-8. PC-NFS says that it cannot open any more files even when the limit in autoexec.bat is set higher. E-9. Can (PC)NFS mount file systems which are bigger than 2 GB? E-10. What is NFS/TCP? Will it work with my NFS? E-11. +What is PKTD.SYS? Where can I get it? E-12. How can I run Novell Netware (tm) 3.xx at the same time as (PC)NFS using NDIS? E-13. -How many PC's can work with a single PC-NFS server? E-14. Is it possible to modify the read & write buffer sizes in (PC)NFS? E-15. How can I install Ethernet boards not supported by (PC)NFS? E-16. *In postscript files I sometimes get a ^D before the header from my programs. How do I get rid of it? F. Programming F-1. +Is there a toolkit for (PC)NFS programming? Whats the latest version and where can I get it? F-2. What is the Windows Sockets API (winsock)? Where can I get it? F-3. What is the latest version of the NFS protocol? F-4. What happened to version 3 of the NFS protocol? F-5. What is the current RPC version? Where can I get it? F-6. Where can I get the RPC definition for PCNFSD? F-7. What are RFC's? What RFC's describe the NFS protocol? Where can I get these RFC's? F-8. How can I tell if a file is NFS mounted from a server? G. Product Features Comparisons G-1. +Driver support comparison chart of different products. G-2. +Protocol support comparison chart of different products. G-3. +MS-Windows applications and support chart of different products. G-4. +Utilities available with different products. G-5. +Telnet features of different products. G-6. +TCP/IP package compability with other network protocols. G-7. Features of different X-windows products. H. Information Sources H-1. Chest - Council for Higher Education Software Transfer [UK] H-2. X/Open H-3. +Books H-4. Related Papers (published) H-5. +Popular FTP sites H-6. Related FAQ's, USENET lists, mail lists. H-7. *Glossary. W. Third-Party Email Software W-1. CliqAccessories Quadratron Systems W-2. Higgins Group Prod sw Enable Software W-3. Linkage Concentric Technologies W-4. OpenMail Hewlett-Packard W-5. PathWay Messenger The Wollongong Group. W-6. PC-Eudora Qualcomm Software. W-7. SelectMail SunSelect X. X-Windows Software X-1. eXceed Hummingbird Software Ltd. X-2. eXcursion DEC X-3. eXodus White Pines Software. X-4. Micro X-Lite StarNet Communications Corporation. X-5. MultiView/X JSB Corporation X-6. PC-Xware & PC-Xview NCD, Inc. X-7. PC X-server & PC Link XLink X-8. PC-Xsight Locus Computing Corp. X-9. PC DECWindows Motif DEC X-10. -Reflection X Walker, Richer & Quinn X-11. X Appeal Xtreme s.a.s. X-12. Xoftware AGE Logic, Inc. X-13. Xvision VisionWare Soft, Inc X-14. X-windows for OS/2 IBM Y. Other Third Party & Related Software Server Products: Y-1. eNFS INTERSTREAM Y-2. Multinet TGV, Inc. Y-3. -DEC TCP/IP Digitial Equipment Corp. Y-4. -NHFSSTONE Legato Y-5. -PrestoServe Legato Y-6. SOSS Rich Braun Y-7. TCPWare for VMS Process Software Corp. Other software: Y-9. -WinTrumpet/Trumpet Peter Tatam. Y-10. -WinVN Y-11. -Cello Y-12. MacPPP Z. TCP/IP & NFS Products Z-1. AIR for Windows SPRY, Inc. Z-2. BW-NFS Beame & Whiteside, Inc. Z-3. Chameleon NFS NetManage Z-4. CU/TCP Clarkson University/Rutgers University Z-5. Distinct TCP Distinct Corp. Z-6. -LAN Manager TCP/IP Microsoft Corp. Z-7. LAN Workplace NFS Novell, Inc. Z-8. NCSA Telnet Nat'l Center for Supercomputing Applications. Z-9. NFS/Share Intercon, Inc. Z-10. NS & ARPA Services Hewlett-Packard, Inc. Z-11. +Pathway Access DOS/Win The Wollongong Group. Z-12. PathWay Access OS/2 The Wollongong Group. Z-13. PC-NFS SunSelect Inc. Z-14. PC/TCP FTP Inc. Z-15. Reflection Walker Richer & Quinn, Inc. Z-16. SuperTCP Frontier Technology, Corp. Z-17. TCP/IP for DOS IBM Z-18. -TCP/IP for OS/2 IBM Z-19. TCP/Open Lanera Corp. Z-20. TTCP Turbosoft Pte. Ltd. Z-21. WATTCP Erick Engelke Z-22. WinQVT QPC Software, Inc. Z-23. *Fusion Pacific Softworks, Inc. Z-24. *PathWay Access for Mac The Wollongong Group. Z-25. *ICE/TCP James River Group Z-26. *Piper/IP IPswitch, Inc. ------------------------------------------------------------------------------- *-1. What topics does this FAQ cover? This Frequently Asked Questions list covers questions on commonly available NFS products and related products and topics running on PC systems and Macintosh systems. The original section of topics has increased so much that I've expanded them into separate sections as well. The topics now covered are: A. Basics - general questions on what NFS, (PC)NFS, & TCP/IP are. B. Setup - questions on setting up these products C. Server - questions on the PCNFSD server & server system administration D. Applications - commercial and public-domain applications which will work with these systems. E. Problems & General Q&A - questions, problems and general info on (PC)NFS maintainence. F. Programming - Programming toolkit and NFS & RPC related programming questions. G. Product Features Comparions - This compares the features of the TCP/IP packages. H. Information Sources - This is a list of organizations or sources of information on NFS, XDR, Winsock, lists, etc. W. Third Party Email - This is a list of commercial and shareware email packages X. Xwindows Packages - This is a list of commercial Xwindows software Y. Third Party & Related Software - Third party products such as server software, news, etc. Z. TCP/IP & NFS products - Commercial and public domain/shareware TCP/IP & NFS products. NOTE: Throughout this document all vendors are referred to by their entry number in section Z, eg. Z-X refers to entry X in section Z. ------------------------------------------------------------------------------- *-2. Where can I get this FAQ? This FAQ is available on the USENET newsgroup, posted once in every two weeks and also on the following FTP sites: seagull.rtd.com: /pub/tcpip/pcnfs.FAQ ftp.york.ac.uk: /pcnfs/FAQ/pcnfs.FAQ As of August: bcm.tmc.edu: /nfs src.doc.ic.ac.uk ftpserver.massey.ac.nz ------------------------------------------------------------------------------- *-3. Who helped write this FAQ? The information in the FAQ is a collection generated from my personal knowledge and with the help of the following people who I'm very grateful to: Geoff Arnold (geoff@east.sun.com) Sun Microsystems Farid Rahmi (fr@sunbim.be) Sunbim (?) Marty Udescci (martyu@twg.com) The Wollongong Group Chip Sparling (chip@ftp.com) FTP Software Fred Whiteside (fred@bws.com) Beame & Whiteside C. J. Sacksteder, et. al. (cjs@psuvm.psu.edu) Penn State Univ. Dean (Dean@frontiertech.com) Frontier Tech. Winifred Crowther Beame & Whiteside Kenneth Adelman (Adelman@tgv.com) TGV, Inc. Bruce Miller (Miller@tgv.com) TGV, Inc. John Keyes (john.keyes@east.sun.com) Sun Microsystems Vernon Schryver (vjs@sgi.com) SGI, Inc. Marc Wiz (mwiz@austin.ibm.com) IBM Corp. (The Core Group) Dave Fetrow (fetrow@biostat.washington.edu) Univ. of Washington Fritz Mueller (fritz@netmanage.com) NetManage, Inc. Zvi Alon (zvi@netmanage.com) NetManage, Inc. Brian Pawlowski (beepy@ennoyab.eng.sun.com) Sun Microsystems Edmund J. Sutcliffe (edmund@york.ac.uk) Univ. of York Erick Engelke - Independent Giovanni Novelli Xtreme s.a.s Danny Thomas (vthrc@mailbox.uq.oz.au) Independent Thomas Dwyer III (tomiii@mtu.edu) Independent Geert Jan de Groot (geertj@ica.philips.nl) Philips Francis K. Selkirk (fks@ftp.com) ftp Software Inc. Alan Arndt (aga@Comtech.com) Comtech Labs Gavin Longmuir (gavin@sorokin.anu.edu.au) Australian Nat'l Univ. George Brad Weiner (sales@age.com) AGE Logic, Inc. George Stump The Wollongong Group, Inc. Bob MacFadgen (bob@ipswitch.com) Ipswitch, Inc. Special thanks to: Edmund Sutcliffe & the University of York for providing an FTP site and his endless help. Geoff Arnold for placing the FAQ on the comp.protocols.nfs FTP sites. C.J.Sacksteder for allowing the use of portions of his document, "Features of TCP/IP Packages for DOS and Windows" Brian Pawlowski for allowing the use of his list of bibliographic entries on papers for NFS, XDR, and RPC. To any others that I may have forgotten, you have the right to look me up in Tucson and demand a beer out of me. ------------------------------------------------------------------------------- *-4. Who maintains this FAQ? This FAQ is maintained by Rawn Shah. Any additions, clarifications, modifications and other changes to the FAQ should be directed to me. You can reach me at any of the following addresses (in order of preferrence): rawn@rtd.com rawn@xray1.chem.arizona.edu You can also contact me at the following postal address: Rawn Shah RTD Systems & Networking, Inc. 2601 N. Campbell Ste 202B, Tucson, AZ 85719 USA or the following US phone numbers: Phone: (602) 318-0696 FAX: (602) 318-0695 This FAQ list may not be modified or redistributed under any other name other than that reserved by the author. You may reproduce the FAQ and distribute it freely as long as you maintain the original author. ------------------------------------------------------------------------------- *-5. Who maintains comp.protocols.nfs? This is an unmoderated USENET newsgroup although there are regular posters who will be able to help with your questions related to (PC)NFS products. ------------------------------------------------------------------------------- *-6. Where are the archives for comp.protocols.nfs? The archives for comp.protocols.nfs are kept at the following FTP sites: bcm.tmc.edu src.doc.ic.ac.uk ftpserver.massey.ac.nz ------------------------------------------------------------------------------- *-7. Trademarks and Registered names. AppleTalk, LocalTalk and Macintosh are registered trademarks and MacX and A/UX are trademarks of Apple Computer Corp. VMS, and OpenVMS are registered trademarks of Digital Equipment Corp. ONC, NFS, NIS & PC-NFS are registered trademarks of Sun Microsystems Computer Corp. PC/TCP and Interdrive are trademarks of FTP Software Inc. BW-TCP and BW-NFS are trademarks of Beame & Whiteside Software, Ltd. IBM, IBM PC, AIX & OS/2 are registered trademarks and LAN Server is a trademark of International Business Machines, Inc. Chameleon, ChameleonNFS and Newt are trademarks of NetManage Corp. DEC, VMS, OpenVMS, DECnet are registered trademarks and eXcursion and DECwindows are trademarks of Digital Equipment Corporation TSSNet is a trademark of Thursby Software Systems, Inc. PathWay, PathWay Access & PathWay Client NFS are trademarks of The Wollongong Group SuperTCP is a trademark of Frontier Technologies, Inc. XVision is a trademark of VisionWare Software Ltd., UK. eNFS is a trademark of INTERSTREAM, Inc. AIR is a trademark of SPRY, Inc. ODI and LAN WorkPlace are trademarks of Novell, Inc. NDIS, MS-DOS and MS-Windows are registered trademarks and LAN Manager is a trademark of Microsoft Corp. MOTIF is a trademark of the Open Software Foundation, Inc. WINQVT/NET and WINQVT/NFS are trademarks of QPC Software Corp. HCL-eXceed, HCL-eXceed Plus, and HCL-eXtend are trademarks of Hummingbird Software, Ltd. TCPOpen is a trademark of Lanera Corp. UNIX is a trademark of Unix Systems Laboratories Multinet is a trademark of TGV, Inc. PC-Xware & PC-Xview are trademarks of NCD, Inc. PC-Xsight is a trademark of Locus Computing Corp. Multiview/X is a trademark of JSB Corporation PC X-server & PC-Link are trademarks of XLink Corp. eXodus is a trademark of White Pines Software. CU/TCP is a trademark of Clarkson University and Rutgers University NCSA Telnet is a trademark of the National Center for Supercomputing Applications. Micro X-Lite is a trademark of StarNet Communications Corp. AIR is a trademark of SPRY, Inc. ICE.TCP is a trademark of the James River Group, Inc. Piper/IP is a trademark of Ipswitch, Inc. ------------------------------------------------------------------------------- *-8. What do the -, + and * before the questions mean? The - is used to signify that the question is out of date or has no information related with it. The + is used to signify that the question has been recently updated with new information or corrections have been made to the answer. The * signifies the question as a new one as of the current FAQ version ------------------------------------------------------------------------------- *-9. Whats up and coming in the next issue of the FAQ list? The FAQ is expanding at good rate and I'm still waiting for it to level off. Coming issues should include: - a few more TCP products (VxDTCP, DLink, etc) - a better description of NFS 3 once I finish reading it. - Cello, trumpet, MacWAIS, etc. ------------------------------------------------------------------------------- A. Basics ========= A-1. What is NFS? Network File System (NFS) is file system that will mount remote file systems across homogenous and heterogenous systems. NFS consists of a client and server systems. An NFS server can export local directories for remote NFS clients to use. NFS runs over IP using UDP (commonly). There are NFS implementations that will work using TCP as the network transport service. NFS was originally developed by Sun Microsystems Computer Corp. (SMCC) and is now part of their Open Network Computing (ONC) initiative. NFS has been accepted by the IETF in certain RFC's (see question F-X) as a standard for file services on TCP/IP networks on the Internet. ------------------------------------------------------------------------------- A-2. What is (PC)NFS? (PC)NFS is a generic term referring to all NFS systems running on IBM PC and compatible systems as well as other Personal Computer systems as defined upon by the X/Open Group. ------------------------------------------------------------------------------- A-3. Where can I get (PC)NFS for my DOS system? (PC)NFS for DOS systems is available from the following vendors: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Product Name Vendor Pricing Entry +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ AIR SPRY Z-1 PC-NFS SunSelect *$435 Z-13 BWNFS Beame & Whiteside *$395 Z-2 PC/TCP FTP Corp. *$400 Z-14 IBM TCP/IP IBM Z-17 LAN Manager TCP Microsoft Z-6 PathWay The Wollongong Group * Z-11 SuperTcp Frontier Tech. *$495 Z-16 LAN Workplace Novell $ Z-7 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ * means other pricings available see corresponding entry for product in Section Z. ------------------------------------------------------------------------------- A-4. Where can I get (PC)NFS for my MS-Windows system? (PC)NFS for MS-Windows is available from the following vendors: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Product Name Vendor Pricing Entry +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ AIR SPRY $ Z-1 PC-NFS SunSelect *$435 Z-13 BWNFS Beame & Whiteside *$349 Z-2 Distinct Distinct Corp. Z-5 TCPOpen Lanera Corp. Z-19 PC/TCP FTP Corp. *$400 Z-14 PathWay The Wollongong Group * Z-11 ChameleonNFS NetManage *$495 Z-3 SuperTCP Frontier Tech. Z-16 WinQVT/Net QPC Inc. $40 (shareware) Z-22 $20 (student) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ * other pricings available; see corresponding entry for product in Section Z. ------------------------------------------------------------------------------- A-5. Where can I get NFS for my Macintosh system? You can get NFS clients for Macintosh from: The Wollongong Group: PathWay NFS [Z-11] Intercon: NFS/Share [Z-9] There are also packages for hardware gateways which will allow Macintosh systems to NFS drive systems. Cayman systems puts out the GatorShare software for their GatorBox and GatorStar series which gateway LocalTalk based Macintosh systems onto an Ethernet and allow IP tunneling inside Appletalk to reach external systems. GatorShare allows Macintoshs to mount NFS disks as AFP (Apple Filing Protocol) volumes which are displayed as remote drives on the Apple Chooser. Shiva & Fallaron have similar gateway (DDP-IP) systems. IPT has a software only system that works in concert with one of the above mentioned hardware systems that allow Unix systems to export disks as AFP volumes. IPT's Partner is not in strict sense an NFS system. It implements Appletalk on Unix systems and exports drives and printers as Appletalk ones. CAP (Columbia Appletalk) is a public domain package which has similar services. Work is currently in progress to produce a software based DDP-IP package that will connect LocalTalk Macintoshes through a Mac system with both LocalTalk & Ethernet interfaces to Ethernet based IP systems. Hopefully the project will be completed before October. Initial prospects are to distribute this as shareware. ------------------------------------------------------------------------------- A-6. What is PC-NFS as opposed to (PC)NFS? PC-NFS is a specific NFS product for PC systems from SunSelect. PC-NFS is a registered trademark and so should NOT be used as a generic term describing all NFS systems on PC's. (PC)NFS is a generic term describing NFS systems on PC's as decided upon by the members of X/Open. ------------------------------------------------------------------------------- A-7. What is TCP/IP? Transmission Control Protocol/Internet Protocol (TCP/IP) is the main transport protocol used on the Internet for connectivity and transmission of data across heterogenous systems. It is an open standard which is available on most Unix systems, VMS and other minicomputer systems, many mainframe & supercomputing systems and some microcomputer & PC systems. TCP/IP is a software solution for network connectivity. There is little assumption on the hardware system used for actual physical connections. The most common hardware solution is Ethernet, but TCP/IP will also run on Token-Ring, AT&T StarLAN, microwave & spread spectrum systems , LocalTalk (needs a gateway), Serial lines (modems, serial connections) and other systems as well. To run TCP/IP on a system you first need a hardware driver. On Macintosh systems, the hardware drivers are built into the system or is provided by the board manufacturer. On a PC system, there are different types of hardware drivers available both commercially and via public domain/shareware including the Packet driver specification by FTP Software, Inc., Microsoft's Network Device Interface Specification (NDIS), & Novell's Open Datalink Interface (ODI). Drivers for OS/2 systems are available from IBM and/or the board manufacturer (if they support OS/2). If a driver is not available for your hardware, look for a shim. This is a software device which translates between two driver specifications. There are shims for ODI-on-NDIS, NDIS-on-Packet driver. ODI-on-Packet driver, etc. usually publically available. You then need a TCP/IP stack. This is package specific usually comes with every product. Each such stack has its own requirements for hardware drivers. you must find a combination of driver & TCP/IP stack which is compatible with your hardware & system. Macintosh's do not have a problem since most Macintosh systems use the MacTCP stack which is available from Apple and is provided with most if not all Macintosh TCP/IP packages. PC systems have something close to a standard in TCP applications called the Windows Sockets API (Winsock). [Note: This is not specific only to TCP/IP it is a general standard for networking on PC irrelevant of the transport protocol. Hence, there may be versions for NetBEUI, IPX, etc.]. The Winsock API is avaialble in 16 bit and 32 bit versions. The 32 bit versions are for Windows NT systems. Winsock is implemented in Dynamically Loaded Libraries or DLLs. Currently work is under way to develop a freeware Winsock DLL but many commercial versions are available. With the TCP/IP stack in hand, you then need all the TCP/IP application programs such as Telnet, FTP, mail, etc. Just about every TCP/IP package has a corresponding set of applications although some do not provide all the different applications available. ------------------------------------------------------------------------------- A-8. What is telnet? What is ftp? Telnet & FTP are two TCP/IP applications for remote host access and remote file transfer, respectively. Any host with a telnet client can connect to any host with a telnet server. Any work done within a telnet session is executed on the server host, thus for most intents and purposes your are on the remote server, virtually. FTP clients can connect to FTP servers to transfer files either direction. You can preserve the file contents independent of the client and server hosts. ------------------------------------------------------------------------------- A-9. What is a client? What is a server? Why do I need them? A client application uses resources available on a remote site. This remote site runs a server for this purpose. NFS is a client-server technology. You need an NFS client to mount remote disks or directories. The server makes these disks or directories available for other systems to use. For example, If you have an NFS client on your PC, you can mount remote drives on your PC. However, if that PC does not have an NFS server, then you cannot make it possible for other systems to use your local drive. ------------------------------------------------------------------------------- A-10. Where can I get (PC)NFS cheap/free/PD? There are currently no free or shareware NFS _client_ packages available. Please read [A-X]. SOSS [Y-6] is a public domain NFS _server_ available by FTP. There are, however, a few different TCP/IP packages available as shareware and freeware such as WATTCP, NCSA Telnet, CU/TCP, WinQVT (shareware). Please see the product list in section Z for appropriate referrences. ------------------------------------------------------------------------------- A-11. What is SOS & SOSS? Where can I get it? SOS (stan's own server) is the original NFS server developed by See-Mong Tan and is a public domain nfs server. SOSS (son of stan's server) is a souped up version of SOS developed by Rich Braun, et al with better performance capabilities. SOS is still available although it is advised that you use SOSS when necessary. SOSS is available at the following site: grape.ecs.clarkson.edu ------------------------------------------------------------------------------- A-12. Are there any free NFS clients available for DOS? There was once a project at the Univ. of Maryland which made an NFS client for free distribution but is now no longer available. There have also been reports that NCSA Telnet may come out with an NFS client in the future but so far there hasn't been any further news on that. There is a client being developed for the WATTCP package by Micheal Durkin. This will be released as shareware ($15) in executable format only. Source code may be available depending on the authors preference. ------------------------------------------------------------------------------- A-13. What is SLIP? Serial Line Internet Protocol (SLIP) is a standard on the Internet for serial line and modem connectivity between two systems. This allows any one SLIP client to connect to a SLIP server to provide connectivity between different IP hosts. Both systems must have TCP/IP stacks running. Certain SLIP packages even allow the SLIP client to act as a gateway between a local network and a remote network, ie. all machines on the local network can connect automatically over the SLIP line to remote systems and vice versa. SLIP packages are available for PC systems. See G-1. ------------------------------------------------------------------------------- A-14. What is PPP? PPP (Point-to-Point Protocol) is a direct link protocol which works over serial lines and direct links similar to SLIP. Overall it gets more throughput than SLIP. The remote host needs to accept PPP connections and the local host should act as a client. ------------------------------------------------------------------------------- Section B. Basics ================= ------------------------------------------------------------------------------- B-1. What are the different specification types of drivers available? The following are common specification types of drivers available: A. Packet drivers - freely available set of drivers on the net maintained by ftp Software and also in part by Russell Nelson of Crynwyr. B. NDIS v2.0 & v3.0 - Network Device Interface Specification developed by Microsoft and 3Com. Version 2.0 is the current version for MS-Windows and Windows for Workgroups. Version 3.0 is the new specification for MS-Windows NT. C. ODI - Open Driver Interface developed by Novell, Inc. D. SLIP, PPP - These are more protocol specifications for serial and distance links. Both are defined in the Internet RFCs. PPP is described initially in RFC 1172 with related descriptions in 1331-1334, 1376-1378, and several newer ones. SLIP is described in RFC 1055. ------------------------------------------------------------------------------- B-3. What are packet drivers? Where do I get them? Packet drivers are the link between your Network interface card and your TCP/IP protocol stack (of each application). They are a low level driver specification with support for many different Network interface cards. The packet driver specification is maintained by FTP Software and is available from: vax.ftp.com:/pub/packet-d.* Russ Nelson of Crynwyr, Inc. (nelson@crynwyr.com) also maintains many packet drivers. He also maintains the FAQ available for packet drivers on comp.protocols.tcp-ip.ibmpc. This FAQ can be received by ftp from the following sites: seagull.rtd.com: /pub/tcpip/other-faqs/pktdrv.faq ------------------------------------------------------------------------------- B-4. Can I run packet drivers with (PC)NFS? Yes. See chart G-1 for compatibility with different packages. ------------------------------------------------------------------------------- B-5. Can I run (PC)NFS over SLIP? Yes. See chart G-1 for availability in the different products for PC systems. Macintosh systems can run NFS/Share from Intercon with the InterSLIP package copyrighted & freely distributed by Intercon available from: ftp.intercon.com: InterCon/sales/InterSLIP1.0fc3.sea.hqx This will run with MacTCP 1.1.1. ------------------------------------------------------------------------------- B-6. Can (PC)NFS run with NDIS drivers? Yes. See chart G-1 for availability in the different products. ------------------------------------------------------------------------------- B-7. Can I run (PC)NFS at the same time as CUTCP or NCSA Telnet? Yes. You need to run PKTMUX.EXE. This will multiplex connections between two different applications using packet drivers. PKTMUX allows one to run multiple TCP/IP protocol stacks. There is also a version of CUTCP which runs over SunSelect's PC-NFS and is available via ftp from: ftp.york.ac.uk:/pub/pc/pc-nfs/cutcp/CUTCP.ZIP ------------------------------------------------------------------------------- B-8. Can (PC)NFS run with NDIS drivers? Yes. Please look at chart G-1 for compatibility with different products. ------------------------------------------------------------------------------- B-9. Can I use (PC)NFS to mount a diskless PC from a remote server? Yes. The following products have this capability: PC-NFS PC/TCP BW-NFS AIR for Windows PC-NFS can be installed partially onto disk to access network applications like telnet, ftp, etc. placed on a remote server. PC/TCP also has PROM chips for ethernet cards for diskless PCs to boot with network services. In Europe, BOOTP PROMs are available from Dirk Keoppen [dirk@incom.de]. These PROMs support a large number of Ethernet cards and works with many versions of (PC)NFS including that from SunSelect, FTP Software, Novell and Microsoft LAN Manager. ------------------------------------------------------------------------------- B-10. Can (PC)NFS run over token ring? Yes. See chart G-1 for availability in the different products. ------------------------------------------------------------------------------- B-11. Can I use my 3C509 Etherlink III card with (PC)NFS ? Yes. The 3C509 has both NDIS and ODI drivers shipping with the box. Trouble is some are not where they are supposed to be. The NDIS drivers are in the following directory on the floppy : A:\MSLANMAN.DOS\DRIVERS\ETHERNET Also, a packet driver is obtainable for this card (also see B-1) ----------------------------------------------------------------------------- B-12 Can I PC-NFS SLIP at higher baud rates than 9600 ? The built-in slip driver will not allow any higher speeds than 9600, but there is a way around this. Instead of using SLIP.SYS, you can always configure PC-NFS in packet driver mode (look for the PKTD.SYS shim) and use a shareware slip driver than conforms to the packet driver specification. Ask archie about SLIPPER.EXE or ETHERSL.COM. ----------------------------------------------------------------------------- B-13 Can I access an MSCDEX CD-ROM with PC-NFS ? No, but you can fool your PC by using an 'MSCDEX simulator', i.e. a small utility that will redirect the interrupt used by MSCDEX and return constant values. Does not work will all the published CD's, but is worth the try. Mounting an ISO9660 CDROM over NFS is not always sufficient to get full access to the application residing on it. Some utilies refer to MSCDEX for various reasons. So, can you use the NFS-mounted volume and still have full MSCDEX access ? No, but you can fool your PC by using an 'MSCDEX simulator', i.e. a small utility that will redirect the interrupt used by MSCDEX and return constant values. Does not work will all the published CD's, but is worth the try. These utils are obtainable from ftp.york.ac.uk (/pub/pc-nfs/CD-rom) ------------------------------------------------------------------------------- B-14. Can I run NDIS over Packet drivers? Yes. You can run packet drivers along with the DISPKT9.COM shim and run the program as a generic NDIS driver. ----------------------------------------------------------------------------- B-15. Which is better NDIS or ODI? After a small discussion, it seems that ODI is generally faster and it does not need be to loaded in the config.sys which helps enormously during debugging and development). Both NDIS and ODI are widely available with most Ethernet cards and many Token-Ring cards as well. ODI however has one slight problem when it comes to development. Although it is an "open" specification and is available via ftp, Russel Nelson of Crynwyr pointed out that: Message-ID: <744695828snx@crynwr.com> " The documentation for Novell's driver development kit is available from dev_docs/lan_drv. This should not be mistaken for a specification of an "open" interface. If you want to write an "ODI driver" (that is, the thing that adapter manufacturers ship), you must purchase the Lan Driver Development Kit for $7,000. When I suggested to Novell that they should document the LSL <--> MLID interface, they seemed somewhat bemused, as if to say "Whyever would you want that?? -- just buy the DDK!" Apparently, there *is* no "ODI driver" spec -- Novell doesn't even have an internal document for the LSL <--> MLID interface. " You can FTP the NDIS specification from: vax.ftp.com You can FTP the ODI specification from: sjf-lwp.sjf.novell.com:/dev_docs/{lan_drv, pstacks}/* [email to Dave Murphy dmurphy@novell.com] ------------------------------------------------------------------------------- Section C. Server ================= ------------------------------------------------------------------------------- C-1. What is pcnfsd? What is pcnfsdv2? What is BWNFSD? PCNFSD is the server software run on remote systems for service access such as User authorization and print services. PCNFSD is freely distributed. It was originally designed for SunSelect's PC-NFS software package but has been accepted by the X/Open committee as a semi-standard for (PC)NFS. PCNFSDv2 is the current version of this server software. BWNFSD is an alternate server package from Beame & Whiteside, Inc. which is also freely distributable. ------------------------------------------------------------------------------- C-2. Where can I get PCNFSD for my server system? PCNFSD has been ported to many different platforms. The following is a list of FTP sites for the different versions: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Platform Location +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SunOS 4.x, Solaris, bcm.tmc.edu Solbourne, src.doc.ic.ac.uk NeXTStep ftp.york.ac.uk:/pun/pv/pc-nfs/RPC.pcnfs/* Ultrix 4.2 bcm.tmc.edu IRIX/SYSV sgi.sgi.com:/support/pcnfsd.sysV [unsupported] ftp.york.ac.uk:/pub/pc/pc-nfs/RPC.pcnfsd/* AIX 3.2 Call IBM and ask for PTF# U412556 AIX 3.2.1 Call IBM and ask for PTF# U419359 AIX 3.2.3 Call IBM and ask for PTF# U414701 MIPS platforms ftp.york.ac.uk:/pub/pc/pc-nfs/RPC.pcnfsd/* IBM MVS Call IBM and ask for PTF# UY84244 [pcnfsd v1 only] OpenVMS 5.5 DEC TCP/IP v3.0 [product] SCO Unix v3.2 SCO NFS [product] HP 9000 [HP-UX 9.x] HP-UX NFS [product] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ There is a combined version of PCNFSD v2 for the following systems: Sun, Ultrix, MIPS, SGI, BSD, SVR4 which is available from ftp.york.ac.uk:/pub/pc-nfs/RPC.pcnfs/pcnfsd.tar.Z BWNFSD (V3.0f) is available from: dorm.rutgers.edu: /pub/msdos/bws/bwnfsd ftp.bws.com: /pub/bw/bwnfsd ------------------------------------------------------------------------------- C-4. How can I test NFS performance? The following information does not contain information on LADDIS which is a newer test suite for NFS systems. Please look at C-10 for information on LADDIS. The following is a post from the archives from a while back which answers this directly: As it turns out, there's a surprising amount of software floating around that looks at NFS. Such software includes: nfswatch -- curses-based promiscuous NFS monitor. This program prints out a running tally of how many of each type of request comes in, and of which file systems are the most heavily used. Nfswatch can be used to look at traffic to individual files, too. This is anonymously FTPable from icarus.riacs.edu. server_stat -- a NFS monitor program that runs on Encore Multimaxes. This shows information on hosts, users, and NFS request types performed. This is capable of talking to a rpc.srvstatd process on another machine, though I don't know of other machines that support the Encore srvstatd program. nfsstone -- the Encore NFS benchmark, as presented in: Shein, B., Callahan, M., Woodbury, P., NFSSTONE: A Network File Server Performance Benchmark, Usenix Summer 1989 conference proceedings, pp 269-275. This is a synthetic benchmark load, with an empirically- determined mix of operations. nhfsstone -- the Legato NFS benchmark. This is also a synthetic load generator, based again on a particular observed load mix. You can get this by sending mail like: To: request@legato.com Subject: send nhfsstone path path_back_to_me I had some problems getting this, though I was ultimately successful. NetMetrix (formerly EtherView) -- a Sun-based packet spy that is capable of doing some characterization of NFS load and response times. This is a commercial product. For more information, contact: Hewlett Packard, Network Test Division One Tara Blvd., Suite 403, Nashua NH 03062 (603) 888-7000 LANWatch -- another packet spy, from FTP Software, Inc. This can filter out NFS traffic; I don't know what can be done with the packets though once they're filtered out. For more information, call FTP at (800) 282-4FTP, or send mail to info@ftp.com. [ There's lots of other packet spies, too, and I suspect that most of them can do at least a little bit with NFS packets. ] The problem with most of the programs above (except for the synthetic loads, to which this just doesn't apply, since they're not NFS monitors) is that you don't get raw data points which you can then analyze. You get the data that the authors thought you might want... and which might not be what you really want. There's much to be said for the approach of dumping traces and lots of timestamps into a file, then providing (a) programs that analyze such files, and (b) the format of the files, so that people can write their own analysis programs. On a PC-based packet spy, this is a hard thing to do. There's a fair number of people (at the major NFS server vendors, Sun, DEC, and a few universities) who are also poking around at the problem. Some people are looking at filesystem activity tracers, which (in addition to being interesting research on its own) could provide still more reams of interesting statistics when combined with a NFS tracer. The consensus was that the best way to trace NFS operations is to do so via a promiscuous packet spy. Such an approach has many advantages. First, if you don't have kernel sources, you can still get useful information. Second, because you don't instrument the server kernel, you don't have to worry about influencing the experiment in adverse ways. However, there's some chance (depending on your hardware and on how fast you make your software go) that you'll drop packets. The 'hack the server kernel' approach won't drop any requests, but violates the above constraints. I suspect that the best way to gather statistics is by using *both* methods of measurement, then comparing the results. I was also referred (twice) to the SunOS 4.1 NFS implementation, and in particular the adaptive NFS retransmission code therein. These numbers might be interesting to see, once 4.1 is more easily available. Of course, the usual Unix file access pattern (i.e., lots of short-lived files in /tmp, most of which get written, then read once, then deleted) information applies. This was mentioned by several people; one reference given was: Floyd, Rick, Short-Term File Reference Patterns in a UNIX Environment, University of Rochester Department of Computer Science TR 177, March 1986. Another good paper (with not much data on NFS, though) is: Lazowska et al, "File Access Performance of Diskless Workstations", ACM TOCS, volume 4, number 3, August 1986, pp 238-268. Not a whole lot was said about general models of NFS access. Most places that had any models had derived them from some number of studies and from the output of nfsstat, or so it seemed. It does seem that there's a few general trends, however. There are some sites (including ours, I suspect) that fall into the low-utilization, few write model, where the server rarely satisfies more than one client's NFS requests in some given time slot. There's also the high-utilization, many write model, which is what I'm sure a lot of sites see. One responder said that once one's clients have enough memory, the buffer cache ends up reducing the number of random reads going on, so one is left with the reads that happen to start up a new process, and with writes. Those who talked about models generally said that they think there's almost as many models as there are networks using NFS. I suspect that this is true, but that perhaps some useful information (or at least methods) can be abstracted out, regardless. A number of people also suggested that I talk to Legato and to Auspex and see what they've done in this area. I have a couple of papers from Auspex; at a first glance, I don't think they look too closely at NFS load characterization (at least, not as I define that), but instead concentrate on what Auspex did to get better speed out of their NFS file server. The Auspex paper titled, "Benchmark Methodology and Preliminary Performance Specifications for the Auspex NS5000 Network Server" (Bruce Nelson, Auspex TR #2, October 1989) has more load characterization information than do the other Auspex TRs I have, but it still doesn't have a whole lot. (By the way, I'm not implying that Auspex hasn't looked at load characterization, because they obviously have. I just don't have the fine details of their results.) I also did some talking with people at Legato; their comments and models show up in the nhfsstone benchmark, or are otherwise repeated above. -Steve Spoken: Steve Miller Domain: steve@umiacs.umd.edu UUCP: uunet!mimsy!steve Phone: +1-301-454-1808 USPS: UMIACS, Univ. of Maryland, College Park, MD 20742 ----------------------------------------------------------------------------- C-5. What is NHFSSTONES? Where can I get it? "Nhfsstone" (pronounced n-f-s-stone, the "h" is silent) is a copyrighted product of Legato Systems, Incorporated and is provided for unrestricted use and distribution of the binary program derived from it. nhfsstone is a NFS load generating program. It is used on an NFS client to generate an artificial load with a particular mix of NFS operations. It reports the average response time of the server in milliseconds per call and the load in calls per second. The program adjusts its calling patterns based on the client's kernel NFS statistics and the elapsed time. Load can be generated over a given time or number of NFS calls. The current version of the program can only be compiled on 4.x BSD based UNIX systems. To obtain the nhfsstone source shar file, send email to "request@Legato.COM" or {sun,uunet}!legato!request. The Subject line and/or body of the message should have contain the command line: send unsupported nhfsstone Note the exact spelling of "nhfsstone". To issue delivery, you should also add a line of the form: path
where
is the preferred email address to use. Generally, using a domain-style email address works best. A uucp path starting with "sun!" or "uunet!" can also be used. Joseph Moran Legato Systems Inc. 260 Sheridan Avenue Palo Alto, CA 94306 (415) 329-7886 mojo@Legato.COM or {sun,uunet}!legato!mojo ------------------------------------------------------------------------------- C-7. How many nfsd's & biod's should I run on my server? Default number of nfsd's & biod's is 8 Suggested Equation for nfsd's is: [number of disks exported] + [number of network interfaces] Suggested maximum number of nfsd's runinng on a Sun system (SunOS 4.x) without any accelerators is 22. Any more does not help in performance. ------------------------------------------------------------------------------- C-8. What is asynchronous I/O? How can I modify my NFS server system to use asynchronous I/O? Asynchronous I/O (ASYNC) means that information comes and leaves at unannounced intervals whereas synchronous I/O (SYNC) has a predetermined interval when I/O can actually pass. NFS has been used both through SYNC and ASYNC communications. The original specification stated that SYNC I/O should be used although did not bind to it. This results in slower communications during transfers. ASYNC creates problems in that, if for some reason communications should fail (eg., your NFS server crashes), there may be inconsistency in the data. The bright side of ASYNC is that performance increases by a great deal. Many implementations of NFS using asynchronous I/O are available. Despite the disadvantage, the number of complaints about data loss due to this are far fewer than the reports of performance increase. However, be warned that asynchronous I/O is a direct violation of the NFS specification from X/Open which states that all procedures of the NFS protocol are synchronous. This makes such a server no longer compliant to X/Open ------------------------------------------------------------------------------- C-9. What is a good NFS server? Network Appliances Corp have recently come out with a product which they call an NFS appliance, the FAServer. It is a 486 based system with an EISA bus, 16 MB RAM, 2 MB NVRAM, and a RAID subsystem. The RAID subsystem keeps up to 20 logical copies of the entire file system. They have a proprietory operating system which does only simple management and disk serving. The pricing is about $20,000. ------------------------------------------------------------------------------- C-10. What is LADDIS? LADDIS is multi-vendor and vendor neutral SPEC NFS Benchmack designed by engineers from Leato, Auspex, Data General, DEC, Interphase and Sun [LADDIS is an abbreviation using their first letters]. This covers local Ethernet or FDDI nets and not WAN. An excerpt from the LADDIS abstract: " The purpose of the LADDIS benchmark is to give users a credible and undisputed test of NFS performance, and to give vendors a publishable standard performance measure that customers can use for load planning, system configuration, and equipment buying decisions. Toward this end, the LADDIS benchmark is being adopted by SPEC (the System Performance Evaluation Cooperative, creators of SPECmarks) as the first member of SPEC's System-level File Server (SFS) benchmark suite." " LADDIS is available directly from SPEC. Here is the contact person: Name: Dianne Dean (SPEC contact person at NCGA) Phone: 703-698-9600 Ext 318 Fax: 703-560-2752 Email: spec-ncga@cup.portal.com Mail: SPEC c/o NCGA 2722 Merrilee Drive, Suite 200 Fairfax, VA 22031-4499 There is about a $1000 charge for the distribution tape. ------------------------------------------------------------------------------- C-11. What is XRemote & LBX? These are specifications for running the X11 windows system over lower bandwidth connections like serial lines. XRemote is a private specification developed by NCD. Inc. It is available in commercial packages. LBX (Low-Bandwidth X) is the specification also contributed by NCD to the X11 standard forthcoming next year, ie. X11R6. You can get information on LBX via FTP from: export.lcs.mit.edu:/contrib/LBX-xconf93-paper.ps.Z This is not a formal document only an informative disclosure. Running a low bandwidth X protocol over something like Ethernet would not be useful since the compression algorithms involved would incur additional CPU usage and so you would not get much of a performance advantage at all. ------------------------------------------------------------------------------- Section D: Applications ======================= ------------------------------------------------------------------------------- D-1. Where can I get mail with (PC)NFS? POPmail versions 2 and 3 and SMTP are the most common mail protocols for (PC)NFS and TCP/IP systems for PCs. Please look at the chart G-3 for mail systems. Here are some additional third-party mail packages that work with PC-NFS: a. Open Systems Mail by Pinesoft (US) [pinesoft@netcom.com] b. Mail-It by Unipalm (UK) [tomk@unipalm.co.uk] Tom Kermeen Unipalm Ltd 216 Cambridge Science Park Milton Road Cambridge CB4 4WA UK +44 223 420002 +44 223 426868 [FAX] [Site license is available for L5000 (five-thousand pounds)] Distributed in the US by: Unipress Software 2025 Lincoln Highway, Edison, NJ 08817 USA (800) 222-0550 info@unipress.com c. WinELM was written by Peter Churchyard of Imperial College, London. It is available for winsock systems from the ftp site ftp.york.ac.uk:/pub/pc-nfs/Mail/winelm.zip lister.cc.ic.ac.uk:/pub/winelm There are also DOS, PC-NFS and WinSock API versions there. d. ECSMail is a commercial package which supports IMAP & MIME contact steve@edm.isac.ca. I also supports Macintosh & Unix You can get a demo version of ECSMail from ftp.york.ac.uk:/pub/pc-nfs/Mail/ecs.zip [The demo requires an IMAP daemon such as in the Pine mailer] e. Cin'etic Mail Manager works directly with mounted file systems and sends mail via different setups like rsh on PC-NFS. Its publicaly availble via ftp (cmm21f.zip). You can also contact them at: Cinetic@speedy.cam.org 71460,666 (Compuserve) This package currently supports PathWay, PC/TCP, PC-NFS, FSUUCP by Fubar Systems, UUPC/extended by Drew Derbyshire. Its configuarble for other systems as well. In addition, for mail arrival notifiers, there is WinBiff (version 1.6) for MS-Windows 3.x that works with PC-NFS, UUPC, Waffle and FSUUCP. This is available from: ftp.cica.indiana.edu: /pub/pc/win3/mirrors/wnbff16.zip wsmr-simtel20.army.mil: PD1: WNBFF16.ZIP ------------------------------------------------------------------------------- D-2. Where can I get a news client for (PC)NFS? USENET News (NNTP) clients are available specifically from: Super-TCP [Z-16] - Windows version WinQVT [Z-22] - Windows version Chameleon [Z-3] - DOS version. There is a public domain program called WinVN which uses the Winsock API. This means that just about any product which has the Winsock.dll should be able to run it. It is available from: sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps/winvn.zip Trump and WinTrump are other popular packages for news available from sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps/* A simple news client by Stan Barber and a client by Kjettil Otter Olsen (with source code) are avalable from ftp.york.ac.uk:/pub/pc-nfs/news WinVN is a newsreader for Windows 3.x systems publically available from: titan.ksc.nasa.gov: [anonymous.pub.win3.winvn] (Its a VAX host) Macintosh newsreaders include: TheNews Newsreader MacNews Nuntius All are available from: mac.archive.umich.edu:/mac/util/comm/* ------------------------------------------------------------------------------- D-3. Where can I get an FTP server for (PC)NFS? The following systems have FTP servers: BW-TCP, PC-NFS, PC/TCP, Chameleon, PathWay, Super-TCP, IBM TCP/IP, Lanera TCP ------------------------------------------------------------------------------- D-4 Where can I get RWALL for my (PC)NFS system? As far as memory serves me there currently are no implementations of the rwall command as in Sun ONC on (PC)NFS systems, except possibly one for the Macintosh NFS/Share product from Intercon. Sorry folks. If anyone has information on this one please mail me, there are people who want to know. Here is what Geoff Arnold had to say about it back in 1989: " One of the questions I am often asked about PC-NFS is "how come there's no way for me to find out when a particular file server is going down? Unix users get notified." I point out that (at least on SunOS) the mechanism used is "rwall", which is an RPC service, and that for size reasons we can't afford to embed a version of rpc.rwalld in PC-NFS. This explanation is reasonable, but unsatisfactory. My reaction was to say "let's ask the NIC for a UDP port so that we can use it to send unsolicited messages to PCs running PC-NFS." That would certainly do the trick. However, a moment's thought reveals that the problem is bigger than just PC-NFS. Surprisingly, there is at present no simple ubiquitous message protocol to fulfil this function. rwall is fine for SunOS and other ONC licensees, but what about other systems? Do I have to rely upon SMTP? That's incompatible with the idea of broadcasting a simple message such as "The backbone will be down for five minutes at 12:00 to replace a bridge." This could be trivially simple or slightly more involved (but still simple). The trivial approach is to dedicate a UDP port for unsolicited system messages. Anyone could send one, in a single datagram, and the listener process would be responsible for delivering it as seemed appropriate for the system (dialog box, console message, etc.) A more complete approach would be to define a formal protocol so that it would be possible to convey information about the coding of the message, message length (so that TCP could be used instead) and so forth. [If the spec exceeds one page, it's too complicated.] Comments? Geoff " ------------------------------------------------------------------------------- D-5. Where can I get an INT-14 redirector for (PC)NFS? INT-14 redirectors are available with various (PC)NFS products including: BW-NFS [Z-2] PC/TCP [Z-14] Chamelon NFS [Z-3] There is a version for PC-NFS v5.0 (by Geoff Arnold) at: ftp.york.ac.uk:/pub/pc-nfs/utils/int14/* sorokin.anu.edu.au:/pub/nfs5-addons/int14.zip An INT-14 redirectory for WATTCP is available from: dorm.rutgers.edu:/pub/msdos/wattcp/apps.zip ------------------------------------------------------------------------------- D-6. Where can I get YPPASSWD for PC-NFS? There is a version of YPPASSWD for PC-NFS v5.0 at: ftp.york.ac.uk:/pub/pc-nfs/utils/yppasswd/yppasswd.zip ------------------------------------------------------------------------------- D-7. Where can I get IBM 3270 terminal for (PC)NFS? Please see chart in section G-1 under TN3270. ------------------------------------------------------------------------------- D-8. Where can I get X-Windows for (PC)NFS? The following X-windows products are available: For DOS: Product Cost Company Version ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Xvision $395 VisionWare Soft, Inc X11R5 PC-Xware $545 NCD, Inc. X11R5 PC DECwindows ?? DEC X11R4 PC Xsight ?? Locus Computing X11R4 Micro X-Lite $75 StarNet Comm. Corp. X11R4 X Appeal $350 Xtreme X11R5 Xoftware ?? AGE Logic X11R4 PC X-Kit $249 XLink X11R5 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For MS-Windows: Product Cost Company Version ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ HCL-eXceed ?? Hummingbird Software X11R5 eXcursion ?? DEC X11R5 MultiView/X ?? JSB Corp. X11R4 PC-Xview $445 NCD Inc. X11R5 Xoftware ?? AGE Logic X11R4 eXodus $295 White Pine Software X11R5 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For Macintosh: Product Cost Company Version ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ MacX ?? Apple Computer Corp. X11R5 eXodus $295 White Pines Software X11R5 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For OS/2: Product Cost Company Version ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ X Windows $150 IBM X11R5 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ------------------------------------------------------------------------------- D-10. Where can I get a database that works with (PC)NFS? Any database would be able to use the NFS mounted drive as long as it recognizes it as a local drive. Most network versions of a database however will not work unless they specifically say they support (PC)NFS & TCP/IP. DBMS's known to work with (PC)NFS include SQL*Net (Oracle), and Sybase for DOS. PC-NFS is known to work with Paradox for Windows & DOS for network file storage. ------------------------------------------------------------------------------- D-11. Where can I get a WAIS client for (PC)NFS? WAIS Manager 3.0 by Kebin Gamiel (representing MCNC CNIDR and UNC-Chapel Hill) has recently been announced which is WinSock compliant. Features include multi-format handling capability, relevance feedback and a new interface with Toolbar for quicker access. You can get this via ftp from: sunsite.unc.edu: /pub/micro/pc-stuff/ms-windows/winsock/apps/waisman3.zip ftp.cnidr.org: /pub/NIDR.tools/wais/pc/windows/waisman3.zip There is a WAIS client for PC/TCP at: calvin.sfasu.edu: /pub/dos/network/pc-tcp/wais.zip WinWAIS is another winsock version of WAIS by EINET is available from: ftp.einet.net:/einet/pc/* sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps MacWAIS is a MacTCP compatible application for System 6 and 7 by EINET: ftp.einet.net:/einet/mac/* ------------------------------------------------------------------------------- D-12. Where can I get an archie client for (PC)NFS? A ported version of c-archie is available for PC-NFS at the ftp sites: bcm.tmc.edu: /nfs/archie.exe ftp.york.ac.uk:/pub/pc-nfs/utils/archie.exe (has source as well) This version works for PC-NFS v4.0a There is a version for PC/TCP at: calvin.sfasu.edu:/pub/dos/network/ftp-pctcp/archie.zip ------------------------------------------------------------------------------- D-13. Where can I get a gopher client for (PC)NFS? nfsgopher is available from bcm.tmc.edu in /nfs which will work with PC-NFS gopher for MS-Windows is available for PC-NFS systems in an alpha release from the ftp site: lister.cc.ic.ac.uk: pub/wingopher/{readme.txt,gopher.exe} ftp.york.ac.uk:/pub/pc-nfs/utils/gophersfx.exe source available in ftp.york.ac.uk:/pub/pc-nfs/utils/gofer.zip HGopher (Hampson's Gopher) is a client for gopher systems. The following version has been tested at ANU: sorokin.anu.edu.au: /pub/nfs5-addons/hgopher.exe It is originally distributed from: lister.cc.ic.ac.uk: /pub/wingopher There is a gopher client for PC/TCP at the following site: calvin.sfasu.edu:/pub/dos/network/ftp-pctcp/goph1_05.exe gophbook from UNC is an Asymetrix Toolbox application which uses winsock.dll and is available from the ftp site: sunsite.unc.edu: /pub/micro/pc-stuff/ms-windows/winsock/apps/gophbook.zip ------------------------------------------------------------------------------- D-14. Where can I get a WWW (World Wide Web) client for (PC)NFS? There is a version of such a client for PC-NFS at ftp.york.ac.uk:/pub/pc-nfs/utils/wwwpcnfs.zip Winsock clients are now commonly available and should work with any PC TCP/IP system which supports winsock. Some winsock clients are Cello and NCSA Mosaic. ------------------------------------------------------------------------------- D-15 Where can I get X25 for (PC)NFS ? The Software Forge developed a PC/TCP-IP adapter for X25, which is a hardware/ software bundle that : - conforms to PDS specification 1.09 - conforms to RFC 877/1356 (TCP-IP over X25) - supports PC/TCP and PC-NFS (probably any PDS-compliant software) - does address resolution of 100 Internet adresses (expandable) - can have up to 20 simultaneous sessions For more information, contact UniPalm (+44(0)223250100) or unipalm@unipalm.co.uk The Software Group Ltd also makes X.25 software for PC systems. They can be contacted at: 2 Director Court, Suite 201 Woodbridge, Ontario, Canada L4L 3Z5 (418) 856-238 (418) 856-0242 or email scott@group.com There is also an X.25 package available with Super-TCP from Frontier Technologies [Z-16]. ----------------------------------------------------------------------------- D-16 Where can I get NEWGRP.EXE for PC-NFS ? NEWGRP.EXE is a utility written by Geoff Arnold that does the equivalent of the Unix newgrp command. See man newgrp if you are really interested. It can be ftp-ed from some of the ftp sites found in C-2. ----------------------------------------------------------------------------- D-17 Where can I get AUTOCONF for PC-NFS ? AUTOCONF is a shareware utility designed and implementes by Henk Swaters that allows system administrators to define an NIS map (pcnfs.config) that holds the equivalent of DRIVES.BAT. The NIS map works on a user-basis and the mounting and unmounting of existing resources is performed trough a single .EXE file. AUTOCONF.ZIP is available on ftp.york.ac.uk in /pub/pc-nfs. You do need at least PKUNZIP 2.04G to unzip it. What follows is the README. AUTOCONF 14-06-93 autoconf utility for pcnfs ========================== NAME autoconf.exe - configure PCNFS-client network drives and printers DISCRIPTION This program is made to configure the network drives and printers of a PCNFS-client from the NIS database. The name of the NIS-map is pcnfs.config. Each line of the pcnfs.config file defines user or group information and has the format username/groupname list-of-drives/printdevices where list-of-drives/printdevices is either another username/ groupname, or a network drive/printdevice: (drive:,hostname:/path,/option,option..) or (printdevice:,hostname:printername,/option,option..) example: ---------------------------------------------------------------- all\ (g:,calibra:/export/MSDOS/WinEnv) printer_staff\ (lpt1:,pslw1:lw1,/fmt=raw) smith\ all (f:,calibra:/export/MSDOS/DosEnv)\ printer_staff ---------------------------------------------------------------- When user smith executes autoconf.exe he mounts the following environment: g: calibra:/export/MSDOS/WinEnv f: calibra:/export/MSDOS/DosEnv lpt1: pslw1:lw1 /fmt=raw USAGE A known user has to be logged in, otherwise the program terminates. If the program is executed without any options the username is used as keyvalue. It is possible to give one or more keyvalues as argument of the program. These arguments can be either usernames or groupnames. By Default the program unmounts a drive before mounting a new drive on the same device. The argument /n or /nounmount switches this option off. The argument /h or /help prints out a help screen and terminates the program. There will be no mount or unmount command. example with the same auto.config as above: autoconf printer_staff /n or autoconf /nounmount printer_staff These equivalent commands try to mount: lpt1: pslw1:lw1 /fmt=raw There will be no unmount command and if there is already a network device on lpt1: there are no changes made. AUTHOR Henk Swaters Dept. of Computer Science University of Twente. swaters@cs.utwente.nl HISTORY autoconf.exe ------------- 14-06-1993 verion 1.0 ------------------------------------------------------------------------------- D-18. Where can I get a remote backup utility for (PC)NFS? WATTCP has a backup utility called "rtar" with its applications distribution. The following commercial packages have similar facilities: PC/TCP, Super-TCP, BW-TCP, Lanera TCPOpen, XLink PC-Link ------------------------------------------------------------------------------- D-19. Which (PC)NFS packages support DNS [named]? Please see the chart Z-3. ------------------------------------------------------------------------------- D-20. Where can I get a traceroute program? BW-TCP [Z-X] has a traceroute program with their package. There is a traceroute program available for WATTCP at: polysla.calpoly.edu:/pub/mdurkin/trtb91b.zip This is for an older version of WATTCP but is being converted to the new version currently. ------------------------------------------------------------------------------- D-21. Where can I get an LPD program? For commercial and some PD packages which have an LPD program please look at the chart G-4. There's a Winsock-compliant LPD called NLPD available via ftp from: sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/apps/wslpd.exe A PC-NFS LPD version is in ftp.york.ac.uk:/pub/pc-nfs/utils ------------------------------------------------------------------------------- Section E: Problems & General Q&A ================================= ------------------------------------------------------------------------------- E-2. Can I use DNS instead of NIS with PC-NFS? No. PC-NFS currently only supports the Sun ONC NIS product. (Even NIS+ is not fully compatible). DNS is available with other packages. ------------------------------------------------------------------------------- E-3. Why do versions of (PC)NFS not follow symbolic links? This is because according to the NFS definition, filenames are handled by the NFS client. In some (PC)NFS if the files in the symbolic links may not be in the same exported directory as the directory the link is in. NFS mounted files appear as drives on the clients and the clients cannot parse any files which appear higher up on the tree or on a different tree segment than that of the NFS exported drive (from the server). Certain versions can be clever enough to counter this problem by their own methods but it is generally accepted that (PC)NFS systems do not support symbolically linked files. ------------------------------------------------------------------------------- E-4. PC-NFS v4.0 has trouble with Cntl-S, Cntl-Q. This has been fixed in release 4.0a and 5.0. For 4.0a please look at the ftp sites [H-5] ------------------------------------------------------------------------------- E-5. PC-NFS v4.0 has trouble with redrawing windows. This has been fixed in release 4.0a and 5.0. For 4.0a please look at the ftp sites [H-5] ------------------------------------------------------------------------------- E-6. PC-NFS v4.0 doesn't allow me to access the local printer when I have network printers. This is because the default setup for printers in PC-NFS v4.0 is as a network printer. In the print manager choose the printer and change the setup. At the bottom of the setup screen for the printer should be a checkbox indicating that it is a network printer. Uncheck this box. ------------------------------------------------------------------------------- E-7. I cannot delete any file that PC-NFS makes with a ~ (tilde) in it. To get rid of the problem, in your config.sys, run pcnfs.sys as: C:\NFS\PCNFS.SYS /c^ where c reassign the immediately following character. [In this case to the character '^'] ------------------------------------------------------------------------------- E-8. PC-NFS says that it cannot open any more files even when the limit in autoexec.bat is set higher. PC-NFS uses its open own file limit and not the DOS system open file limit. To modify this limit use the /f flag as such in the config.sys: C:\NFS\PCNFS.SYS /f50 The limit here is set to 50. The maximum is 64. ------------------------------------------------------------------------------- E-9. Can (PC)NFS mount file systems which are bigger than 2 GB? Most server file systems do not handle such large file systems, but this is possible with various software enhancements like Disk-Suite for Sun systems. NFS clients on the other need not know how big the actual remote file system is. It only receives information on how big the individual files are and not the file system itself. The Network Appliance server has one partition under which all drives can be mounted for NFS exportation. ------------------------------------------------------------------------------- E-10. What is NFS/TCP? Will it work with my NFS product? NFS/TCP is a different type of the original NFS protocol which uses the TCP protocol as opposed to the originally specified UDP protocol. NFS over UDP works well over a single LAN but is as not suitable for multiple LANs or WANs as NFS/TCP. TCP's windowing of packets capability and reliability gives it an advantage. In UDP dropped packets are not acknowledged between the two hosts, however, TCP retransmits all dropped packets. One more aspect of TCP (which is more idealistic than real) is the congestion control capacity between routers for TCP which prevents overflooding of a congested network link. In NFS/UDP it is easy to create UDP data which look like NFS requests from other machines. However, TCP makes it much more difficult to add falsified packets which impersonate another machines data. The problem with NFS/TCP is that it is incompatible with NFS/UDP. Therefore all servers running the TCP version will be invisible to clients running a UDP version and vice versa. NFS/TCP is available in PC/TCP and BWNFS. ------------------------------------------------------------------------------- E-11. What is PKTD.SYS? Where can I get it? PKTD.SYS is a shim that allows PC-NFS to use packet drivers instead of its native drivers. It is available from: bcm.tmc.edu src.doc.ic.ac.uk ftpserver.massey.ac.nz ftp.york.ac.uk:/pub/pc-nfs/pktd/pktd.zip The current version is 5.0. ------------------------------------------------------------------------------- E-12. How can I run Netware 3.xx at the same time as (PC)NFS using NDIS? You can run the NDIS-over-ODI shim available from Novell that will let you run netware at the same time as any other product running NDIS (ie. many (PC)NFS products. ------------------------------------------------------------------------------- E-14. Is it possible to modify the read & write buffer sizes in (PC)NFS? Different (PC)NFS systems have different sizes with default at 1024 Kbytes for both. The standard maximum is 8 KB. In PC-NFS, read buffer size is fixed (1024KB) but you can modify the write size to any thing below this maximum. Currently anything less than 128 bytes is cached into a 256 byte datagram. Anything more than this is passed as its specific size. PC/TCP, PathWay Client NFS & BWNFS allow modification of read & write buffer sizes. ------------------------------------------------------------------------------- E-15. How can I install an Ethernet board not supported by (PC)NFS? Contributed by Farid Rahmi: If you're installing on an IBM PC or compatible, you can use NDIS drivers in general for your Ethernet board. Although I only upgraded to 5.0 after installing a beta version of 5.0 on my 3C509 PC, the procedure should still be the same : 1) Get the NDIS driver, the PROTOCOL.INI and the .NIF file from the LANMAN directory off the floppy that shipped with the 3C509 and copy these three files onto your harddisk (*NOT* in C:\LANMAN !!!, see below) 2) Select NDIS during installation. 3) This should wake up QUIKNDIS, which will transform PROTOCOL.INI for you and put it in C:\LANMAN together with the NDIS driver. Three remarks : - If you have an EISA machine and an ISA 3C509, please RTFM before complaining about lockups. - I noticed that QUIKNDIS would scratch (make zero byte file) the NDIS driver if placed into C:\LANMAN. As mentioned, this was in the beta release. - Too bad SunSelect couldn't ship the drivers with 5.0. Seen most of the other vendors ship these drivers and they are publicly available (ftp.3com.com)... Farid (fr@sunbim.be) ------------------------------------------------------------------------------- E-16. In postscript files I sometimes get a ^D before the header from my programs. How do I get rid of it? This happens mostly on PC systems sending output to postscript printers. The ^D is the EOF character and sometimes causes a blank page to be output by the printer before the print job. It can be disabled by the following: In your WIN.INI file, add below [yourprintername, port] this line: CTLD=0 If you wish to do this permenantly for all windows systems, you can reprogram your printer with the following piece of Postscript code (Thanks to Mark Fleming of Queen's Univ.). Send this as a file to your printer: %! %%Title: CTRL-D serial EOF (End-of-File) character fixed %%Creator: R. Mark Fleming %%+ Queen's University at Kingston % Check if EOF is installed, if not install it % assumes serverloop password is the default one currentdict % Get current dictionary (\004) cvn known { % Check if CTRL-D defined in this dictionary (%% CTRL-D procedure already installed\n %%) print } { (%% CTRL-D procedure not installed!\n %%) print % Define IBMpc (serial) EOF character to do nothing serverdict begin 0 exitserver % Make permanent changes (\004) cvn {} def % To ignore ^D at the end of prologs. } ifelse %%EOF ------------------------------------------------------------------------------- Section F: Programming ====================== ------------------------------------------------------------------------------- F-1. Is there a toolkit for (PC)NFS programming? Where can I get it? Until recently, programming toolkits were developed independently by vendors alongside their products. Due to the efforts of different persons and organizations there is a formal definition of MS-Windows in the Windows Sockets API. The current version is 1.1. This is only a standard and product vendors are allowed to distribute their own programming toolkit. Most are now developing or selling Windoes Sockets API compatible toolkits. Please refer to the chart G-3 for products with Windows Sockets API. Certain libaries for mounting drivers and user authentication with PC-NFS 5.0 are available on ftp.york.ac.uk:/pub/pc-nfs/dnet/DNET50.tar ------------------------------------------------------------------------------- F-2. What is Windows Sockets (winsock)? Where can I get it? Windows Sockets is an API developed by a group of NFS vendors as a standard for future network based communications in MS-Windows. The current version of the API is 1.1. Further information for this is available on request. Mail all questions and comments to "winsock@microdyne.com". To join the mailing list, mail to "winsock-request@microdyne.com". Windows Sockets API documentation and related documents are available by ftp to: microdyne.com: /pub/winsock sunsite.unc.edu [Mirror site of the above address and much faster and up 24 hrs] Peter Tatham (developer of the Trumpet newsreader) has developed an alpha release of winsock.dll which uses a packet driver as the network driver. Its currently available from ftp.utas.edu.au:/pb/trumpet. This winsock will be used in the developement of WinTrumpet. ------------------------------------------------------------------------------- F-3. What is the latest version of the NFS protocol? The current official version of the NFS protocol is version 3. It has just recently come out and is being tested at this years Connectathon. A Postscript file is available from: ftp.uu.net:/networking/ip/nfs/NFS3.spec.ps.Z bcm.tmc.edu:/nfs/nfsv3.ps.Z gatekeeper.dec.com:/pub/standards/nfs/nfsv3.ps.Z All comments and questions should be mailed to: nfs3@eng.sun.com ------------------------------------------------------------------------------- F-4. What is new in version 3 of the NFS protocol? New features of version 3 are: - 64bit support - exclusive creates, - asynchronous writes (I guess its official now Vernon) - improved attribute caching - the "ACCESS" command works on the server attributes as well - relaxed transfer size restrictions. - reduced required "GETATTR" operations. More information to come later. ------------------------------------------------------------------------------- F-5. What is the current RPC version? Where can I get it? The current version of RPC is 4.0. It is available at the ftp sites: bcm.tmc.edu src.doc.ic.ac.nz ftpserver.massey.ac.nz There is a version 4.0 which works with WATTCP which is available from polyslo.calpoly.edu:/pub/mdurkin/rpc01a.zip ------------------------------------------------------------------------------- F-6. Where can I get the XDR/RPC definition for PCNFSD? The .x file in the current source kit is available by FTP from: bcm.tmc.edu src.doc.ic.ac.uk ftpserver.massey.ac.nz sunsite.unc.edu:/pub/micro/pc-stuff/ms-windows/winsock/gen/spry-rpc.zip ------------------------------------------------------------------------------- F-7. What RFC's describe the NFS protocol? Where can I get these RFC's? RFC's (Requests for Comments) are standards approved by the IETF (Internet Engineering Task Force) which maintain order on protocols and information technology affecting on the Internet. There are about 1500 or more Internet RFC's and many more drafts & proposals. There are three RFC's currently related to the NFS protocol: RFC 1094 - NFS: Network File System Protocol Specification RFC 1057 - RPC: Remote Procedire Call Specification Version 2 [supercedes RFC 1050] RFC 1014 - XDR: External Data Representation Standard These RFC's are available by ftp from: NIC.DDN.MIL seagull.rtd.com: /pub/tcpip/papers or by mail server from: SERVICE@NIC.DDM.MIL with subject "HELP" or retrieve with "RFC index" ------------------------------------------------------------------------------- F-8. How can I tell if a program is NFS mounted? Here's a message which discusses C code and methods of doing this: In article <21egppINN5li@hoss.usl.com> mdash@usl.com (-candee-+Scheer M.D.) writes: >By happy (?) coincidence, both NFS (at least implementations based closely >on the Sun reference port) and RFS assume that (1) local file systems have >major device numbers where the high bit is off, and (2) the client is >therefore free to play in the namespace of devs with the high bit on. >Clients of both types synthesize devs with the high bit on. I'm aware of >no environment that breaks assumption (1). We're aware of several. We've been down that route and abandoned it several years ago. While this is true of faithful SVRx (where I'm not sure whether "x" includes any 4) ports with RFS, it breaks on many other machines. Including SunOS, which uses a major number that is determined at driver configuration time to denote NFS mounted files. If I recall correctly, out-of-the-box, the magic major number is 20 on SunOS, but may change on reconfig. Other machines where I'm fairly sure that the highbit kludge doesn't work are Pyramid DCOSX, AIX3. It's been a while... If I have to, I could confirm and expand the list by pawing thru our SCCS history databases. Please don't make me - it's scary in there ;-) Furthermore, st_dev will not change between different NFS mounts. Thus st_dev:st_ino cannot be unique. If you're on a SVR3'ish port, there is a macro in sys/types.h (or param.h) analogous to major() and minor(). I seem to recall it is called "bmajor()". If you're on a system that has bmajor(), you can use it - I remember it masking off the upper bit of a major number. So you can say: if (major(x.st_dev) != bmajor(x.st_dev)) file is remote If it doesn't, you have to experiment and keep your fingers crossed. I hate to say this, but there is no easy way to do this universally. We ended up having to read the mount tables and match path prefixes. Yuck. #defines up the wazzoo. I suggest you start reading about getmntent() and analogues, and parse the file system type fields. If performance isn't particularly critical, it may be easier to popen /etc/mount and parse the output: f = popen("/etc/mount", "r"); while(fgets(buf, sizeof(buf), f)) { ... } pclose(f); If you use getmntent() (or /etc/mount kludge), and get a reasonable stat() st_ino value for each file, you can use a "mount number":st_ino as a unique key. But you cannot guarantee that a single file has only one key (multiple NFS mounts of a directory heirarchy). You may also have to resolve symlinks depending on how your application works. This isn't a lot of fun either. If you merely have to determine whether the occasional file is remote or not, just "df " it, and parse the output. Grotty, effective, reasonably portable, and *usually* reliable. But we know systems that can't even get this right... [On HPUX, use "bdf" not "df" ;-)] -- Chris Lewis; clewis@ferret.ocunix.on.ca; Phone: Canada 613 832-0541 Psroff 3.0 info: psroff-request@ferret.ocunix.on.ca Ferret list: ferret-request@ferret.ocunix.on.ca ------------------------------------------------------------------------------- Section G: Product Features Comparisons ======================================= ------------------------------------------------------------------------------- G-1. Driver support comparison chart of different products. Additional codes: s = supported with a "shim" (perhaps some "y" should be "s", tell me) m = "must be used with" as opposed to "also works with" Drivers Included Interfaces Supported ------------------- ----------------------------- Stack Token Packet ID Provided Ethernet Ring FDDI Drivers NDIS SLIP PPP ODI --------- -------- -------- ----- ---- ------- ---- ---- --- --- AIR y y y y PC/TCP y y y y s y y s Chameleon y y y y s y y n Super-TCP y y y n y y y x y IBM/DOS y y y s y y n n BW y y y y y y n y Distinct y y y n y y y y y Pathway y y y y y y y PathWay.OS2 y y y n y y PC-NFS y y y s y y n y LWPD y y y s s y y y HP y y y y y n n s NCSATel n n n m CUTCP n n n m QVT/Net n n n m MSLanMan y y y TTCP y y y s n n s TCPOpen y y y y y y n y WinNT y y y n y n n Piper/IP y y y y y y ICE-TCP y y y Notes: Many packages include drivers for many different network adapters, and/or can use interfaces to existing drivers. Packet driver compatibility implies NDIS and ODI compatibility through the use of dis_pkt and odipkt. ------------------------------------------------------------------------------- G-2. Protocol support comparison chart of different products. It is presumed that a TCP/IP package supports TCP, IP, UDP, ICMP, and ARP, so these are not listed. ID BootP Client RARP DNS NetBIOS (2) --------- ------------ ---- ------- ------- AIR n n y y PC/TCP y y y Chameleon y y n Super-TCP y y y y IBM/DOS y y y BW y y y y Distinct Pathway y y y PathWay.OS/2 y y y PC-NFS y(3) y n y LWPD y y y y HP n y y NCSATel n y CUTCP y n y QVT/Net y y TTCP n(1) y y n(1) TCPOpen y y y y WinNT n n y y Piper/IP y y ICE-TCP ? Notes: (1) Version 2.0 will have bootp support. (2) RFC 1001/1002 NetBIOS over TCP/IP, not level 3 coexistance with NetBIOS over NetBUI. (3) PD Bootp workaround by Thomas Dwyer III available from: ftp.york.ac.uk:/pub/pc-nfs/utils/bootp.exe ------------------------------------------------------------------------------- G-3. MS-Windows applications and support chart of different products. Columns: All Apps -- all applications are Windows based Some Apps -- some are Windows, some are DOS or character All DLL -- stack is implemented as "100% Windows DLL" code WinSock -- supports Windows Socket API (1.1) VxDev -- includes a virtual device drive to support DOS apps running under Windows ID All Apps Some Apps All DLL WinSock VxDev --------- -------- --------- -------- ------- ----- AIR n y y y PC/TCP n y n y y Chameleon y n y y Super-TCP y (1) y(1) y y IBM/DOS n y n(2) y BW n y n n(3) Distinct y n y y Pathway y n(3) PathWayOS/2 y n n PC-NFS n y n y LWPD n y n n(3) HP n n n n NCSATel n n n n CUTCP n n n n QVT/Net y n n n TTCP n y n n(3) TCPOpen n y n y Piper/IP n y WinNT n(4) n(4) n(4) y Notes: (1) Super-TCP/NFS includes DOS based applications and an optional TSR. (2) The stack is protected mode code that sits entirely in extended memory except for a small interface TSR. (3) Winsock is coming RSN, as an update or in the next version. (4) Windows NT doesn't run on top of DOS, and TCP/IP is part of the system. Some of the applications are graphical, many utitities character-based. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Additional codes: d = DOS or character-based application w = Windows based application FTP NNTP SNMP NFS ID Telnet TN3270 client server SMTP POP (3) Client Agent Client --------- ------ ------ ------ ------ ---- ------- ------ ----- ------ AIR d w d w d w w w w3 d w PC/TCP d w d d w d d d2 d3 d y d w Chameleon w w w w w w2 n y x Super-TCP w w w w w w2 w3 w w dx wx IBM/DOS d w d w d w d d w d2 n y x BW d w d w d w d w w w2 w3 n y x Distinct w n w w Pathway d w d w d w d d d w PathWayOS2 y y y y y PC-NFS d w x d w d d w d23w23 n y d w LWPD d w d wx d w d w n n n y x HP d d NCSATel d w (5) d w w n n n n n CUTCP d d d d n n n n n QVT/Net w n w w n w w n n TTCP v2.0 (1) d w TCPOpen w w d w w w w3 n n d w WinNT w n d(4) (6) n n n y Piper y y y y y y y Notes: (1) terminal emulation products sold separately (3) POP (Post Office Protocol): 2 = version 2, 3 = version 3, and implies an SMTP client to send mail (4) "d" here means "character based" (5) get TN3270 (CUTCP) package from Clarkson University (6) server for NT will be in production version ------------------------------------------------------------------------------- G-4. Utilities available with different products. setclock ID ping lpr lpd finger talk whois (rdate) rcp rsh rexec stats --------- ---- --- --- ------ ---- ----- -------- --- --- ----- ----- AIR y y y y y y PC/TCP y y x y n y y y y y y Chameleon y x n y n y n n n n y Super-TCP y x x y y n n y y y y IBM/DOS y y y y n n y y y y y BW y y y y y y y y y n y Distinct y y Pathway y y y n n n y y n n PathWayOS/2 y y y PC-NFS y (3) y n y y y y n y LWPD y y n y y n n y y y y HP y n n n n n n y y n n NCSATel (1) y n y n n y n y y n CUTCP n y n n n n n (2) n n n QVT/Net n y n n n n n (2) n n n TTCP y y y y y TCPOpen y y y y y y y y y n WinNT y y n y n n n y y y y Piper y y y y n y y y y y y Notes: (1) although NCSA Telnet does not come packaged with many utilities, many are available on various FTP servers. (2) has an RCP server, but not a client. (3) printing suported via pcnfsd (in common with most other products) ------------------------------------------------------------------------------- G-5. Telnet features of different products. Terminal Emulation Builtin 3270 options (1) ----------------------- INT14 FTPserv ---------------------- ID VT100 VT220 3270 tk4010 Redir (4) models X-streams graph --------- ----- ----- ---- ------ ----- ------- ------ --------- ----- AIR y y y y PC/TCP y y y n y y y y n Chameleon y y y n n y n(3) n Super-TCP y y y n y n(2) n n n IBM/DOS y y y n n(2) y y n BW y y y y n(2) y n n Distinct Pathway y y y y PathWayOS2 y y y y y y y PC-NFS d w d w x (5) n LWPD y y x y y y y n HP NCSATel y n n n n CUTCP y n y y n y n n n QVT/Net y y n n n n TTCP TCPOpen y y y n y y WinNT y n n n n n n Piper y y n y Notes: (1) models -- can emulate different 3270 models X-streams -- supports extended data streams graph -- supports 3270 graphics (either vector or symbol sets) (2) A separate FTP server runs in the background (without Windows). (3) A patch is available for extended data streams, but it did not work for me (cjs). (4) Built-in FTP server doesn't have much utility for Windows based telnet since an FTP server can be running the same time as Telnet. (5) Will be available shortly (as unsupported add-on) ------------------------------------------------------------------------------- G-6. Support for other network protocols on the same wire Novell Banyan MS-LAN Windows 4 Product Netware VINES X.25 Manager Appletalk DECnet Workgroups Lantastic ------- ------- ------ ---- ------- --------- ------ ---------- --------- AIR y n n n PC/TCP y y y y n n y Chameleon y Super-TCP y y y y n y y y IBM/DOS n BW y n y Distinct y Pathway y y y y(o) y(o) PathWay.OS/2 y y y n n PC-NFS y n y(t) y n n y y NFS/Share n n n n y y n n LWPD y y(t) n HP n NCSATel n n n n y(o) n n n CUTCP n n n n y(o) n n n QVT/Net y(s) n y(s) TTCP TCPOpen y y y y y WinNT y y n n y Piper/IP y y y n (o) option (t) third party software (s) Use a shim ------------------------------------------------------------------------------- G-7. Features of X servers. X11 Window Dev. Product Release Fonts XDMCP ICCCM Video Manager XRemote Kit Winsock ------- ------- ----- ----- ----- ------- ------- ------- --- ------- eXceed 5 y y xevs8t m y y y eXcursion 5 s y w eXodus 5 y y vsx mod y n X-Lite 4 vs mod n n n X-WIN 5 y vhs mod n n y Multiview 4 b y w n n n Xware 5 stb y y cevs8txo mow y y y Xview 4 y y mcevs8tx mo y y XLink 5 sdp vso8 y n DECWin 4 sa n y ev8o n n n Xsight 4 evh w n y Xappeal 5 y vs od n n n Xoftware 5 s y y evs8 mow n y y Xvision 5 satb y y od y y y IBM X-OS/2 5 y y evs8xo p n y y --------------------------------------------------------------------------- Key: Fonts: s - SNF, a - adobe, t - TrueType, b - BDF, p - PCF, d - SPD Video: e - EGA, v - VGA, s - SVGA, m - mono, 8 - 8514, t - TIGA, x - XGA c - CGA, h - Hercules, o - others (MCGA, DIGA, Japanese, etc) Window Manager: m - Motif, o - OpenLook, d - DECWindows, w - MS-Windows, p - Presentation Manager ------------------------------------------------------------------------------- Section H: Information Sources ============================== ------------------------------------------------------------------------------- H-1. CHEST - Council for Higher Education Software Transfers Chest is run in the United Kingdom for all higher educational bodies for the provision of educational software pricing. The run an information service called NISS [telnet niss.ac.uk] which is full of useful information on software deals. Their current director is Mike Johnson. Each educational site has a local representative. Users wanting to deal should contact their local representative. The address for the CHEST & NISS Centre is given below: CHEST & NISS Centre, University of Bath, Bath BA2 7AY, UK +44 (0) 225 826042 There is a discussion list associated with the CHEST product deal at mailbase@mailbase.ac.uk and Chest-Xwindows@mailbase.ac.uk. They have associated archives full of information. To join the list you send a message to mailbase@mailbase.ac.uk with the message body containing "subscribe chest-pcnfs (real name)" ------------------------------------------------------------------------------- H-2. X/Open. The X/Open Company is an international group of vendors which acts as a standards body for API system compatibility of different platforms. They create the X/Open Portability Guide (XPG) which includes a description for portability of a Unix system. The following are the addresses, phone and FAX numbers for the X/Open Company: X/Open Company Ltd. X/Open Company Ltd. Apex Plaza, Forbury Rd., Karufuru-Kanda Bldg., 9F Reading, Berkshire RG1 1AX 1-2-1 Kanda Suda-Cho United KIngdom Chiyoda-Ku, Tokyo 101, Japan Phone: +44 734 508311 Phone: +81 3 251 8321 FAX: +44 734 500110 FAX: +81 3 251 8376 X/Open Company Ltd. X/Open Company Ltd. 1750 Montgomery Street, 1055 Washington Blvd., 6th Floor San Francisco, CA 94111 Stamford, CT 06901 USA USA Phone: +1 (415)773-5383 Phone: +1 (203)975-7778 FAX: +1 (415)421-4278 FAX: +1 (203)975-7744 ------------------------------------------------------------------------------- H-3. Books. Bloomer, John "Power Programming with RPC" O'Reilly & Assoc, 1992 ISBN 0-937175-77-3 US$29.95 --- This covers the details of distributed application developement using RPCs. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comer, Douglas E. "Internetworking with TCP/IP Volume I: Principles, Protocols and Architecture" Second edition, Prentice Hall, 1991. ISBN 0-13-468505-9 --- One of the best referrences on TCP/IP with good examples +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comer, Douglas E., Stevens, David L., "Internetworking with TCP/IP Volume II: Design, Implementation and Internals" Prentice Hall, 1991. ISBN 0-13-472242-6 --- Followup to Comer's very successful Vol 1. Descriptions on specific applications and services +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comer, Douglas E., Stevens, David L., "Internetworking with TCP/IP Volume III: Client-Server Programming and Applications" (BSD Socket Version) Prentice Hall, 1993 ISBN 0-13-474222-2 --- Book 3 has a good description on network programming via RPC & TCP/IP +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Corbin, John, "The Art of Distributed Programming-Programming Techniques for Remote Procedure Calls" Springer-Verlag, New York, New York. 1991. ISBN ?? --- Basic description of RPC and XDR and how to program distributed applications using them. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Engst, Adam "The Internet Starter Kit for Macintosh" Hayden Books, Indianapolis, 1993 ISBN 1-56830-064-6 US$29.95 Canada $37.95 --- Adam has outdone himself in this whimsical starter book for Macintosh users wanting to know about the Internet and how to connect to it. A must read book if you're a novice. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Hunt, Craig "TCP/IP Network Administration" O'Reilly & Assoc., 1992 ISBN 0-13-015389-3 --- Another in O'Reilly's System administration series. Good practical referrence for sysadmins. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Kehoe, Brian "Zen and the Art of the Internet" Prentice-Hall, 1992 ISBN 0-13-010778-6 --- A comprehensive Internet book for beginners. It can be ftp'd from world.std.com:/obi/Internet/zen-1.0 as well It is available in Microsoft Rich Text Format (as in the Help format) from: ftp.york.ac.uk:/pub/pc-nfs/doc/zen10.hlp +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Krol, Ed "The Whole Internet: User's Guide & Catalog" O'Reilly & Assoc, 1992 ISBN 1-56592-025-2 --- A good introduction to the Internet covering the basics such as email and news and expands into new developments as well. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ LaQuery, Tracy, Ryer, Jeanne C. "The Internet Companion: A Beginner's Guide to Global Networking" Addison-Wesley, 1993 ISBN 0-201-62224-6 --- Another introductory book for novices on Internet services. The book informs users on how to find information. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Malamud, Carl "Analyzing Sun Networks." Van Nostrand Reinhold, 1991. ISBN ?? --- Mr. Malamud is a very well known author on networking standards and this book gives a good description of Sun's ONC. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Miller, Mark A. "Troubleshooting TCP/IP" ISBN ?? -- Teaches how to analyze TCP/IP problems and discusses platforms and case studies. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Rose, Marshall T. "The Simple Book: An Introduction to Management of TCP/IP-based Internets" Prentice Hall ISBN ?? -- The first of Mr Roses books on Network management. A new edition is coming out soon, I think. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Rose, Marshall T. "The Internet Message: Closing the Book on Electronic Mail" Prentice Hall ISBN 0-13-092041-7 -- A good book on Internet mail systems by a very enjoyable author. Great for developers not users. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Santifaller, Michael "TCP/IP and NFS." Addison Wesley, 1991. ISBN ?? --- No info. opinions welcome. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Stern, Hal "Managing NFS and NIS." O'Reilly & Associates, 1991. ISBN 0-937175-75-7 --- Very handy troubleshooting book on NFS & NIS problems +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Stevens, W. Richard, "Unix Network Programming" Prentice Hall, 1990. ISBN 0-13-949876-1 --- A good book on the details of Unix network systems with good exercises. Mr Stevens is a very well known author on Unix systems. The source code and errata list are available from ftp.uu.net:/published/books +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Stephen Roge "Unix System V Network Programming" Addison-Wesley, 1993 [Brand new book (July 93), I have not read it yet. Any opinions welcome] ------------------------------------------------------------------------------- H-4. Related papers (published) Glover, Fred, "TNFS Protocol Specification," Trusted System Interest Group, INTERNET-DRAFT, May 24, 1992. -- Proposed draft standard for security extensions to NFS. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Israel, Robert K., Sandra Jett, James Pownell, George M. Ericson, "Eliminating Data Copies in UNIX-based NFS Servers," Uniforum Conference Proceedings, San Francisco, CA, February 27 - March 2,1989. -- Describes two methods for reducing data copies in NFS server code. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Jacobson, V., "Congestion Control and Avoidance," Proc. ACM SIGCOMM `88, Stanford, CA, August 1988. -- The paper describing improvements to TCP to allow use over Wide Area Networks and through gateways connecting networks of varying capacity. This work was a starting point for the NFS Dynamic Retransmission work. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Juszczak, Chet, "Improving the Performance and Correctness of an NFS Server," USENIX Conference Proceedings, USENIX Association, Berkeley, CA, June 1990, pages 53-63. -- Describes reply cache implementation which avoids work in the server by handling duplicate requests. More important, though listed as a side-effect, the reply cache aids in the avoidance of destructive non-idempotent operation re-application-improving correctness. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Kazar, Michael Leon, "Synchronization and Caching Issues in the Andrew File System," USENIX Conference Proceedings, USENIX Association, Berkeley, CA, Dallas Winter 1988, pages 27-36. -- A description of the cache consistency scheme in AFS. Contrasted with other distributed file systems. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Macklem, Rick, "Lessons Learned Tuning the 4.3BSD Reno Implementation of the NFS Protocol," Winter USENIX Conference Proceedings, USENIX Association, Berkeley, CA, January 1991. -- Describes performance work in tuning the 4.3BSD Reno NFS implementation. Describes performance improvement (reduced CPU loading) through elimination of data copies. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Mogul, Jeffrey C., "A Recovery Protocol for Spritely NFS," USENIX File System Workshop Proceedings, Ann Arbor, MI, USENIX Association, Berkeley, CA, May 1992. -- Second paper on Spritely NFS proposes a lease-based scheme for recovering state of consistency protocol. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Nowicki, Bill, "Transport Issues in the Network File System," ACM SIGCOMM newsletter Computer Communication Review, April 1989. -- A brief description of the basis for the dynamic retransmission work. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Pawlowski, Brian, Ron Hixon, Mark Stein, Joseph Tumminaro, "Network Computing in the UNIX and IBM Mainframe Environment," Uniforum `89 Conf. Proc., (1989) -- Description of an NFS server implementation for IBM's MVS operating system. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [RFC1014] Sun Microsystems, Inc., "External Data Representation Specification," RFC-1014, DDN Network Information Center, SRI International, Menlo Park, CA. -- Proposed standard for canonical format for data exchange, used with RPC. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [RFC1057] Sun Microsystems, Inc., "Remote Procedure Call Specification," RFC-1057, DDN Network Information Center, SRI International, Menlo Park, CA. -- Remote procedure protocol specification. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [RFC1094] Sun Microsystems, Inc., "Network Filesystem Specification," RFC-1094, DDN Network Information Center, SRI International, Menlo Park, CA. -- NFS version 2 protocol specification. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Sandberg, R., D. Goldberg, S. Kleiman, D. Walsh, B. Lyon, "Design and Implementation of the Sun Network Filesystem," USENIX Conference Proceedings, USENIX Association, Berkeley, CA, Summer 1985. -- The basic paper describing the SunOS implementation of the NFS version 2 protocol, and discusses the goals, protocol specification and trade-offs. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Srinivasan, V., Mogul, Jeffrey C. "Spritely NFS: Implementation and Performance of Cache Consistency Protocols", WRL Research Report 89/5, Digital Equipment Corporation Western Research Laboratory, 100 Hamilton Ave., Palo Alto, CA, 94301, May 1989. -- This paper analyzes the effect of applying a Sprite-like consistency protocol applied to standard NFS. The issues of recovery in a stateful environment are covered in [Mogul]. Electronically available: ftp gatekeeper.dec.com:/pub/DEC/WRL/WRL-TR-89.5.ps.Z +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Mogul, Jeffrey C. "A Recovery Protocol for Spritely NFS", WRL Technical Note 27, Digital Equipment Corporation Western Research Laboratory, 100 Hamilton Ave., Palo Alto, CA, 94301, April 1993. -- No abstract. Electronically available: ftp gatekeeper.dec.com:/pub/DEC/WRL/WRL-TN-27.ps.Z +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ X/Open Company, Ltd., "X/Open CAE Specification: Protocols for X/Open Internetworking: XNFS", X/Open Company, Ltd., Apex Plaza, Forbury Road, Reading Berkshire, RG1 1AX, United Kingdom, 1991. -- This is an indispensable reference for NFS version 2 protocol and accompanying protocols, including the Lock Manager and the Portmapper. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ X/Open Company, Ltd., "X/Open CAE Specification: Protocols for X/Open Internetworking: (PC)NFS Developer's Specification", X/Open Company, Ltd., Apex Plaza, Forbury Road, Reading Berkshire, RG1 1AX, United Kingdom, 1991. -- This is an indispensable reference for the PC implementation of the NFS version 2 protocol. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Hall M., Towfiq M., Arnold G., Treadwell D., Sanders H. "Windows Sockets: An Open Interface for Network Programming under Microsoft Windows, version 1.1" 1992. -- This is the specification of the Windows Sockets API which is the current standard for Windows PC network socket calls. A must read for current developers. ------------------------------------------------------------------------------- H-5. FTP Sites The official FTP sites for comp.protocols.nfs are: bcm.tmc.edu: /nfs ftpserver.massey.ac.nz src.doc.ic.ac.uk FAQ draft current location: seagull.rtd.com: /pub/tcpip/FAQ.pcnfs.v1.5.Z or pcnfsfaq.zip Other FTP sites: calvin.sfasi.edu: /pub/dos/network/ftp-pctcp dorm.rutgers.edu: /pub/msdos/bws ftp.bws.com: /pub/bw ftp.cica.indiana.edu ftp.cnidr.org: /pub/NIDR.tools/wais/pc/windows ftp.com ftp.netmanage.com ftp.novell.com: ftp.york.ac.uk: /pub grape.ecs.clarkson.edu lister.cc.ic.ac.uk microdyne.com: /pub/winsock [RFCs] nic.ddn.mil: seagull.rtd.com: /pub/tcpip sgi.sgi.com [ODI] sjf-lwp.novell.com: sorokin.anu.edu.au: /pub/nfs5-addons sunsite.unc.edu: /pub/micro/pc-stuff/ms-windows/winsock vax.ftp.com ------------------------------------------------------------------------------- H-6. Related FAQs, USENET lists, email lists etc. You can find FAQs, FAQlets, and other lists on USENET related to the topic of PC's and TCP/IP Networks in general at the following sources: A. Comp.protocols.tcp-ip.ibmpc FAQlet by Bernard Abouba This covers details of running the IP protocols and intermixing different packages on IBM PC & compatible systems. It is posted bi-weekly on the corresponding USENET group. You can also FTP a copy from the following site: netcom1.netcom.com: /pub/mailcom/IBMTCP B. "Features of TCP/IP Packages for DOS and Windows" (Version 0.5 5/13/93) by C.J.Sacksteder This is another comparison of TCP/IP packages for DOS and MS-Windows PC systems. It is posted to comp.protocols.tcp-ip.ibmpc. C. Packet Drivers FAQ by Russell Nelson This covers questions concerning the installation, maintainence and compatibility of the Packet Drivers suite available as freeware on the Internet. It is posted to comp.protocols.tcp-ip.ibmpc. D. Windows Sockets API FAQ This covers questions on the Windows Sockets API standard. There is also a USENET newsgroup for this: alt.winsock. The FAQ is available on the newsgroup and also from the official site for the standard: microdyne.com: /pub/winsock/FAQ/FAQ E. Windows Sockets API mailing list This mailing list can be joined by email request to: winsock-request@microdyne.com F. Sun RPC on Windows This mailing list discusses Sun's Open Network Computing RPC's running on Windows. You can subscribe by mailing to: rpc4win-request@wco.ftp.com G. NFS version 3 mailing list The mailing list for the new NFS specification can be joined my emailing: nfs3@eng.sun.com H. The UK CHEST program mailing list This mailing list contains information on (PC)NFS distributed by CHEST [Z-1]. Email to: mailbase@mailbase.ac.uk with a header "subscribe chest-pcnfs (real name here)" ------------------------------------------------------------------------------- H-7. Glossary These are brief descriptions of the terms used in PC & TCP/IP networking. ANSI American National Standards Institute. A standards making body of the US Federal system. API Application Programming Interface. AppleTalk A proprietory network protocol developed by Apple Computers, Inc. and available on Macintosh systems. ARP Address Resolution Protocol. Nodes use these to determine the hardware address of a given IP address if directly available. Described in RFC 826. BOOTP Bootstrap Protocol. This allows a client to determine its IP address given its hardware address (to some BOOTP server). Described in RFC 1084. client A program which is used to communicate with another which provides special services (eg. an NFS client communicates with an NFS server to mount remote file systems locallly.) DECNET A proprietory networking system developed by Digital Equipment Corp. DLL Dynamically Linked Library. This is a set of shared functions and procedures used by applications that can be loaded or unloaded at any time by the applications. Many TCP/IP packages now come as DLLs. DNS Domain Naming System/Server. This is a system of Internet hosts which provide IP name to IP address resolution. Described in RFCs 1034 and 1035. Email Electronic Mail. This is a method of communication electronically using different methods of delivery. On the Internet the email protocol most commonly used (and the standard) is SMTP. Ethernet This is a physical and data link layer system connecting hosts in a bus-topology network. It is described by IEEE 802.3 and the DIX (Digital, Intel, Xerox) Ethernet II specifications. Both are compatible on the same physical wire but differ slightly in utility. FDDI Fibre Distributed Data Interface. This is a physical layer and data link layer standard for a fibre optic ring-topology network as approved by ANSI. finger A remote check utility to see users and hosts. FTP File Transfer Protocol. This is an application to transfer files from one IP host to another. The client initiates a connection to the server and sends commands to it to indicate which files and the method of transfer. gopher An client-server networked information service. Host A general referrence to a computer system on a network. hostname On IP networks, this refers to the English (sort of) name given to the machine. Can be the same as IP name. ICMP Internet Control Message Protocol. This is a diagnostic protocol for IP data delivery used by various programs such as Ping. Described by RFC 792. Internet The Internet is a very large system of networks spanning the globe. The word "internet" (with small 'i') is also used to describe a WAN. IP Internet Protocol. The transport layer which describes a packet format for data to pass on a TCP/IP network and on the Internet. Described in RFC 791. IP name The Englishlike name given to an IP host. IP address The "dotted-decimal" format identifier for each IP host. Eg. 192.0.0.2 IPX Internet Packet Exchange. Novell's Netware packet delivery system similar in concept to IP. ISDN Integrated Services Digital Network. A hardware description for direct links between two areas by way of special telephony. LAN Manager A proprietory networking system developed by Microsoft. LocalTalk Apple Computer's proprietory cabling scheme for connecting Macintosh systems together. The Appletalk software protocols run over LocalTalk. login To connect to a host. logout To disconnect from a host. LPD Line Printer Daemon. This is a print server for requests by LPR from other hosts on the network. Described in RFC 1179. LPR Line Printer. This was originally a Unix system command which has expanded to include network printing as well on hosts with the LPD MHS Mail Handling System. A email distribution protocol similar to SMTP. MIME Mail Interface Multimedia Extensions. This is a newer email protocol which actually resides above the delivery protocol and describes the content format of the email message. It provides extensions for multimedia email. Described by RFC 1341, 1344, 1426, 1428, 1437, Netware A protprietory networking system developed by Novell, Inc. NDIS Network Driver Interface Specification. This is an data-link layer interface for different systems using a network device. Described by the NDIS papers by Microsoft and 3Com. NFS Network File System. Please see (A-X). NIC Network Information Center of the Internet: internic.net NIS Network Information System. This is Sun Microsystems version of coordination of network information like hostnames and account information. Partially similar to DNS. NNTP Network News Transfer Protocol. This is the distribution method protocol for USENET newsservice between servers and newsreaders (clients). Described in RFC 977 & 1036. ODI Open Data-Link Interface. Novell's data-link layer interface similar to NDIS for systems using the network interface. OSI Open Systems Interconnect. An alternative to the IP suite of protocols developed by the International Standards Organization (ISO). ISO has its own set of protocols available in the Blue Book. Packet Drivers These are series of software for the data-link layer interface, similar to NDIS and ODI but on a lower level for programmability. Described by the Packet Driver Specification by John Romkey of ftp Software, Inc. (see B-3) PCNFSD The daemon utility for authorization of PC-NFS systems. Version 2 is the current common usage version. Ping This is a utility for checking reachability between Internet hosts. POP Post Office Protocol. This is a protocol for server-based e-mail packages. Described by POP2 & POP3 descriptions: RFC 918, 937, 1081, 1082, 1225 PPP Point-to-point Protocol. A data link layer for connecting two hosts directly by serial, modem, or wide-area links. It can carry IP and other protocols. Described (for IP) by RFC 1331-1333. RARP Reverse Address Resolution Protocol. This is used by hosts to map a given hardware address to an IP address. Described by RFC826 RCP Remote Copy. This utility allows a user to copy files from one host to another on a TCP/IP network. REXEC Remote Execute. This utility allows a user to execute commands on a remote host from a local host over a TCP/IP network. RFC Request For Comments. The set of standards and protocol definitions now approved by the Internet Engineering Task Force which describes the Internet and all its protocols. .rhosts This is a file which contains permissions for different accounts and hosts to access that user account. Used by RCP, REXEC, RLOGIN and RSH. RLOGIN Remote Login. This is a application program to connect to remote IP hosts similar to the Telnet program. Described by RFC 1258, 1282 RSH Remote Shell. This allows a user to open a shell on a remote system over a TCP/IP network. SLIP Serial-Line Internet Protocol. This is a data-link layer describing Internet connectivity via a serial line or modem between two hosts. It is similar to PPP. Described in RFC 1055. SMTP Simple Mail Transfer Protocol. The common protocol used in TCP/IP networks and the Internet for email delivery. Described by RFC 821. SNMP Simple Network Management Protocol. The first version of the network management protocol which allows monitoring hosts from remote. Described by RFC 1067, 1098, 1157 SNMPv2 SNMP Version 2. This is the latest version of the SNMP protocol which is compatible with the original version but includes many extensions such as security. Described by RFC 1444, 1446, 1447, 1448, 1450 tar A Unix backup utility both local and remote. TCP Transmission Control Protocl. This is a connection oriented protocol which provides reliable communication between two IP hosts. Described by RFC 793. Telnet This is a remote connectivity application between IP hosts. Described by RFC 764, 854. Token-Ring This is a physical and data-link layer description for a ring-based topology network. topology A somewhat visual description of a network wire system. TSR Terminate and Stay Ready. This is a DOS based program which stays in memory after it is started and allows the user to continue using other DOS programs. UDP User Datagram Protocol. This is a connectionless communication protocol providing non-reliable data delivery between IP hosts. Described by RFC 768 USENET The news system on the Internet providing information by users of the network. UUCP Unix to Unix Copy Program. This is a protocol for network connectivity by non-interactive distribution of files. VTxxx A series of terminal types developed by Digital Equipment Corp. which has become a de facto standard. VxD Virtual Device Driver. This is a driver specification which allows DOS applications to access network services in MS-Windows. WAIS Wide Area Information Services. Another networked information service. This one uses the Z39.50 document format for storage. WINSOCK Windows Sockets API. Please see (F-2). WWW World Wide Web. Yet another networked information service. X.25 A network layer protocol developed by ISO and part of the OSI suite. Xserver A program which allows the user to display X windows applications. Xwindows A networked windowing system commonly found on many workstations and Unix systems ------------------------------------------------------------------------------- Section Y: Third Party & Related Software ========================================= ------------------------------------------------------------------------------- Y-1. eNFS: INTERSTREAM Company : INTERSTREAM, Inc. Contact : Phone : (800) 677-7876 (412) 323-8000 FAX : (412) 323-1930 Email : info@interstream.com Postal mail : INTERSTREAM, Inc. 1501 Reedsale St. Pittsburgh, PA 15233-2329 USA Product : eNFS Current Version: ?? Pricing : $995 [desktop] $1995 [server] Support : ?? Systems : SPARCstation 1, 2, SPARCserver 490,690 Services : server: optimized server board for NFS Size : - Features : - ----------------------------------------------------------------------------- Y-2. Multinet: TGV, Inc Company : TGV, Inc. Contact : SALES@TGV.COM or as call and ask for a salesperson. Phone : (800) TGV-3440 (408) 427-4366 FAX : (408) 427-4365 Email : info@tgv.com [general questions] sales@tgv.com [sales questions] service@tgv.com [technical questions] Postal mail : 603 Mission St Santa Cruz, CA 95060 USA Product : Multinet, NFS Server, NFS Client, MultiWare NetWare server for VMS Current Version: 3.2 Pricing : call for quotation Support : support contract available, Call. Systems : Any VAX/VMS system V5.0 and later. Any OpenVMS AXP system V1.0 and later. Services : [call for customization] Size : [depends on configuration] Features : (NFS Server option supports pcnfsd v2) Very complete ONC implementation. ------------------------------------------------------------------------------- Y-6. SOSS: Rich Braun Company : -- Contact : Richard Braun [rbraun@spdcc.com] Phone : -- FAX : -- Email : rbraun@spdcc.com stan@cs.uiuc.edu Postal mail : -- Product : SOSS [Son of Stan's Server] Current Version: 3.2 Pricing : free Support : none Systems : MS-DOS 5.x Services : server: nfs Size : ?? Features : uses packet drivers. Available from FTP site: grape.ecs.clarkson.edu ------------------------------------------------------------------------------- Y-7. TCPWare for VMS: Process Software Corp. Company : Process Software Corp. Contact : Phone : (508) 879-6994 FAX : Email : Postal mail : 959 Concord St. Farmingham, MA 01701 USA Product : Current Version: Pricing : Support : Systems : Services : Size : Features : ------------------------------------------------------------------------------- Y-12 MacPPP Company : Merit Network & Univ. of