Hitchhiker's Guide to Openbsd

Mounting NFS Filesystems
NFS filesystems can be mounted from a client without needing to enable any services or daemons. They 
can be mounted just like any other filesystem. 
NFS filesystems should be mounted via mount(8), or more specifically, 
mount_nfs(8)
. To mount a 
filesystem 
/work
on host 10.0.0.1 to local filesystem 
/mnt
, do this (note that you don't need to use an 
IP address; mount will resolve host names): 
http://www.openbsd.org/faq/faq6.html (18 of 33)9/4/2011 10:02:06 AM

---

6 - Networking
# mount -t nfs 10.0.0.1:/work /mnt
To have that filesystem mounted at boot, add something like this to /etc/fstab: 
10.0.0.1:/work /mnt nfs rw 0 0
It is important that you use 
0 0
at the end of this line so that your computer does not try to fsck the NFS 
filesystem on boot. The other standard security options, such as 
noexec
, 
nodev
, and 
nosuid
, should 
also be used where applicable. For example: 
10.0.0.1:/work /mnt nfs rw,nodev,nosuid 0 0
This way, no devices or setuid programs on the NFS server can subvert security measures on the NFS 
client. If you are not mounting programs which you expect to run on the NFS client, add noexec to this 
list. 
When accessing an NFS mount as the root user, the server automatically maps root's access to username 
"nobody" and group "nobody". This is important to know when considering file permissions. For 
example, take a file with these permissions: 
-rw------- 1 root wheel 0 Dec 31 03:00 
_daily.B20143
If this file was on an NFS share and the root user tried to access this file from the NFS client, access 
would be denied. This is because the server uses the credentials of the user "nobody" when root tries to 
access the file. Since the user nobody doesn't have permissions to access the file, access is denied. 
The user and group that root are mapped to are configurable via the 
exports(5)
file on the NFS server.