Changes

<code>/var/nfs/general 203.0.113.256(rw,sync,no_subtree_check)</code>

sudo systemctl restart nfs-kernel-server

Before you can actually use the new shares, however, you’ll need to be sure that traffic to the shares is permitted by firewall rules

To compare the permissions of the General Purpose share with the Home Directory share, create a file Home Directory the same way:

Then look at the ownership of the file:

Output

We created home.test as root via the sudo command, exactly the same way we created the general.test file. However, in this case it is owned by root because we overrode the default behavior when we specified the no_root_squash option on this mount. This allows our root users on the client machine to act as root and makes the administration of user accounts much more convenient. At the same time, it means we don’t have to give these users root access on the host.

sudo nano /etc/fstab

At the bottom of the file, we're going to add a line for each of our shares. They will look like this:

/etc/fstab

Note: More information about the options we are specifying here can be found in the man page that describes NFS mounting in the fstab with the man nfs command.

If you no longer want the remote directory to be mounted on your system, you can unmount it by moving out of the share's directory structure and unmounting, like this:

This will remove the remote shares, leaving only your local storage accessible:

Output

If you also want to prevent them from being remounted on the next reboot, edit /etc/fstab and either delete the line or comment it out by placing a # symbol at the beginning of the line. You can also prevent auto-mounting by removing the auto option, which will allow you to mount it manually.