This share won't be accessible to anyone on the public side of my router. 192.168.0.0/255.255.255.0 means that the only systems who are allowed to access it will be on the 192.168.0.x subnet, which, for me, means everything behind my router.
home is the directory on the server to share. You should modify that to suit your specific needs. Then set the config to share the /home directory over the network. First, install the NFS server: sudo apt-get install nfs-kernel-server My server is running Debian Squeeze, but these instructions should translate well to other distributions.
There are two parts to this configuration - a server and some clients. In brief, I servicized the mounting and unmounting of the network drive, and the control script I wrote for it also places netdrive symbolic links in each non-system user's home directory if a directory on the share exists in their name. Relying on the network for processes like booting and logging into a desktop ended up being a deal-breaker for me having automounted network home directories.īut I did settle on a solution that works well. Even when the mount worked properly, having it mounted at /home caused performance problems. However, if the share was mounted to /home on the client machine, logging into a desktop environment would fail on account of none of the config files being available. Ubuntu 10.04 would error on boot, but give you the opportunity to skip the mount and continue booting.
I had problems where Ubuntu 12.04 would fail to boot if the system failed to mount the network drive properly when the mount was in the fstab. I tried a few configurations before landing on the one described here. One reason I build this server in the first place was so that I could set up roaming home directories for all my Linux PCs in the house. As I mentioned in my last post, I just built out a dedicated server at home, and I'm migrating a bunch of services to it.
0 kommentar(er)
