I. Basic NFS Configuration
 

A. NFS Server
 

1. Download and install the nfs-server RPM package from linux.fnal.gov . Or select NFS server dring the install.

2. To configure a Linux system as an NFS server the nfs daemon must be installed and started and the /etc/export file must contain volume, machine and permission entries. An example entry looks like this:
 

/mnt/51home/redhat-5.1 topaz.fnal.gov(ro)

This specifies that the directory /mnt/51home/redhat-5.1 can be exported to topaz.fnal.gov in read-only mode.

3. Restart the NFS daemon with 'exportfs.'
 

B. NFS Client
 

1. To configure a machine as an NFS client one only needs to do one of two things:
 

a. specify the server volume and mount point on the command line (as root):
 

mount sapphire.fnal.gov:/mnt/51home/redhat-5.1 /mnt/51home

b. add an entry to the /etc/fstab file ,so it mounts at boot time, to look like this:
 

sapphire.fnal.gov:/mnt/51home/redhat-5.1 /mnt/51home nfs soft,intr,ro 0 0

This specifies the machine, volume, mount point, filesystem type, options, dump and fsck order, respectively. The options specify that this is a soft connection, i.e., if it is broken it will not re-establish, it is interruptible, and it is mounted as read-only.

II. Basic NIS Configuration
 

A. NIS Client
 

1. Download and install the ypbind and yp-tools RPM packages from linux.fnal.gov. Should be installed by default.

2. Set the domainname first manually by typing 'domainname <domain name>' where <domain name> is the obvious. To set this permanently, edit the /etc/sysconfig/network file and add the line NISDOMAIN=<domain name>.

3. Start the ypbind daemon. Run 'ntsysv' to make sure the daemon is added to the list of at-boot services.

4. Caveats:
 

a. Experience has shown that ypbind does not work with quotas .

B. NIS Server
 

1. Download and install the ypserv RPM package.

2. Set the domainname as above.

3. Run ypinit -m

4. Make sure the ypserv daemon is added to the services that is started at boot time. Run 'ntsysv' to do this.