###################################################################
# If you change this file, then the effects will not be seen
# until you restart the NFS server.  This requires killing the
# NFS Server first and then restarting it.  The portmapper does
# not need to be restarted.
#
#	Windows 95 : Use the task manager to kill "NFS"
#		     nfs (no arguments)
#	Windows NT : nfs stop
#		     nfs start
###################################################################
# These are the supported options for this NFS Server
#
#   access=host:host...		Only machines whose host names are
#				given in this list are allowed to
#				mount the exported file system.
#   path=path_name		Specifies the exact path of the
#				directory that is being exported
#   anon=id			This option maps the user ID of 0
#				to the given ID "id".  This prevents
#				root access to the file system if
#				"id" is non-zero.  The default is
#				anon=65535
#   root=host:host...		This option allows the machines whose
#				host names are listed to mount and
#				access the file system as root (overrides
#				any anon=id spec).
#   ro=host:host...		Specifies the hosts to which the file
#				system is exported with read-only
#				permissions.
#   uid=n	Makes all files in the given file system
#		appear to be owned by a user whose UID is n.
#   gid=n	Makes all files in the given file system
#		appear to be owned by a group whose GID is n.
#   umask=m	By default, all files have permissions rwxrwxrwx unless
#		the file is marked as read-only.  Read only files appear
#		to have r-xr-xr-x permissions.  This mask allows you to
#		remove permission bits.
#			004 - removes 'other' read permissions
#			002 - removes 'other' write permissions
#			001 - removes 'other' execute permissions
#			040 - removes 'group' read permissions
#			020 - removes 'group' write permissions
#			010 - removes 'group' execute permissions
#		Use any combination of these flags.  For example
#		umask=026 removes write permissions for the group
#		and removes read/write permissions for other. You
#		cannot remove permissions for the user.  To remove
#		write permissions for everyone, use a read-only
#		option.  The umask=026 causes files to have a default
#		permission of rwxr-x--x.
#
#  Use the umask,uid,gid feature to export various user accounts
#  with restricted priveleges.
#
#  SYNTAX
#	Any line of the exports file beginning with #, a space,
#	or a tab is ignored.  The syntax of a line is
#		export_name	-option=value,option=value,...
#	The "export_name" is the name that will be seen by the
#	remote machine as the name of the file system being
#	exported.
#
#	This "export_name" must coincide with the real name of the
#	directory being exported, unless a "path=" option is used
#	to specify a different path for the directory being exported.
#	Using an export name that is different from the Windows
#	path name is probably a good idea, since UNIX machines
#	are not fond of "\" characters in export names.
#
#	The first option must begin with a "-".  Subsequent options
#	must be preceeded by a comma.  Multiple items for a value
#	are colon ":" delimited.  A entry cannot be continued
#	across multiple lines.
#
#  EXAMPLES
#	Simple case.  The entry
#		/c	-path=c:\
#	is used to export "c:\" to remote machines.  The remote
#	machines see the mount point as "/c", which is a useful
#	alias for UNIX machines.  The "/c" must start in the first
#	column of the line.  The "path=" should be the last option
#	of the line.
#
#	By default, an exported file system is exported to *all*
#	remote clients.  This is not good unless you really want
#	to share your disk with everyone.  Use the "access="
#	option to restrict mounting priveleges to specified
#	hosts.  For example,
#		/c	-access=sgir10k:sunsol,path=c:\
#	is used to export "c:\" only to the machines whose host
#	names are sgir10k or sunsol.  Notice that the first option
#	starts with a "-".  A comma is used to delimit further
#	options.  A ":" is used to separate multiple items in
#	an option value (such as host names).
#
#	All files appear to be owned by root, unless you
#	specify an alternative user id or group id.  The entry
#	/c	-access=sgir10k:sunsol,uid=100,gid=200,umask=026,path=c:\
#	exports "c:\" to sgir10k and sunsol as "/c".  All the
#	files appear to be owned by the user whose user id is 100
#	whose group id is 200.  The default permission for files
#	is rwxr-x--x
#
#	Here is a way to export different directories with different
#	permissions.  We are exporting "c:\users\tom" as "/users/tom",
#	and all files in that directory will appear to be owned
#	by a user with ID 100(uid=100).  User and group will have the
#	same permissions on all these files, but 'other' will have no
#	permissions (umask=007).  Consequently, anyone in the group
#	whose ID is 200 (gid=200) will have read/write priveleges.
#	But others will be unable to access the files at all.
#
# /users/tom -access=host1:host2,uid=100,gid=200,umask=007,path=c:\users\tom
# /users/gary -access=host1:host2,uid=101,gid=200,umask=007,path=c:\users\gary
# /users/fred -access=host1:host2,uid=102,gid=200,umask=007,path=c:\users\fred
########################################################################
#
# Sample file to get started.  Be sure to add -access=host1:host2...
#
/c -path=c:\
/d -path=d:\
