If you do not want to use YaST, make sure the following systems run on the NFS server:
RPC portmapper (portmap)
RPC mount daemon (rpc.mountd)
RPC NFS daemon (rpc.nfsd)
For these services to be started by the scripts
/etc/init.d/nfsserver when the system is booted, enter
Also define which file systems should be exported to which
host in the configuration file
For each directory to export, one line is needed to set
which machines may access that directory with what permissions. All
subdirectories of this directory are automatically exported as well.
Authorized machines are usually specified with their full names (including
domain name), but it is possible to use wild cards like
? (which expand the same way as in the
Bash shell). If no machine is specified here, any
machine is allowed to import this file system with the given permissions.
Set permissions for the file system to export in brackets after the machine name. The most important options are shown in Table 22.1, “Permissions for Exported File System”.
Table 22.1. Permissions for Exported File System
The file system is exported with read-only permission (default).
The file system is exported with read-write permission.
This ensures that the user
Does not assign user ID
Converts absolute links (those beginning with
Symbolic links remain untouched.
User IDs are exactly the same on both client and server (default).
Client and server do not have matching user IDs. This tells nfsd to create a conversion table for user IDs. The ugidd daemon is required for this to work.
exports file might look like
Example 22.1, “/etc/exports”.
/etc/exports is read by
mountd and nfsd. If you
change anything in this file, restart mountd and
nfsd for your changes to take effect. This can
easily be done with