> I know what NFS does but I'm > struggling to logon to it. You don't logon to it. You specify what filesystems you want to be visible to clients on the server side (called exporting the filesystems, controlled by /etc/exports or the equivalent on your OS), and on the client side, you use 'mount' to select which server filesystems you want to use, and where you want them located in your client filesystem tree. They behave just like a local filesystem at that point -- you read and write the files just as if they were local.
Example: To make filesystem /server exported by disk.foobar.com available on my desktop workstation as /remote/server, I do (as root): mkdir /remote mkdir /remote/server mount disk.foobar.com:/server /remote/server I can then use the files in /remote/server as if they were local. Note that for this to work securely, you must make sure the numeric UIDs in /etc/passwd match on server and client (not the text userids, the numeric UIDs, which is what NFS uses for "security"). If I wanted that mount to be permanent, I would put it in /etc/fstab with the other filesystems. > Do I need a separate client installed in my > workstation in order to transfer the files between my workstation and > the mainframe? You need NFS client software on any system that will be using the data you export from your NFS servers. > Please help off what client software can I use to > accomplish my experiment. If you are on Linux, you need the nfs-client package. If you're on a different system, tell us what it is, and we can suggest some alternatives. --db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
