Using PC/NFS, PC machines can mount NFS filesystems as logical disks and use them as large virtual disks. Note that a client-only implementation does not limit the direction or types of file transfer operations that are possible within PC/NFS. It simply means that the PC is always the active entity in the Windows-NFS server relationship; the user must mount an NFS filesystem on the PC and then copy files between it and the local disk. In this chapter, we'll look at why you would want to use PC/NFS, alternatives to PC/NFS, setting up PC/NFS, and PC/NFS usage issues.
It is beyond the scope of this book to provide a detailed survey of PC/NFS implementations, since they each have unique features, and new releases for each arrive all the time. You can use Internet search engines, Usenet archives from sources like google.com, and as a last resort, queries to Usenet's comp.protocols.nfs newsgroup to get feedback on what products people prefer. You can also look at www.connectathon.org to see which companies test products at the annual Connectathon interoperability testing event. While the Connnectathon web site won't tell you which companies test NFS and which of those have PC/NFS clients, the list of companies is not too long, so you could go to the web site of each and see which have PC/NFS implementations.
turned up this URL:source code for pcnfsd
|9.6. Side effects||10.2. Limitations of PC/NFS|
Copyright © 2002 O'Reilly & Associates. All rights reserved.