noauto means it won’t be automatically mounted. You can add other options after it if you want. After that, when you want to mount it, run mount /home/james/pool0/incbackup.
Thank you @ersen and @vgaetera for your help. Both solutions work. I am trying to figure out which solution is the “better” one for my use case. Would you mind elaborating on the differences? can gvfs-nfs be considered stable? In the past, I have frequently had nautilus crash or freeze when dealing with network shares.
This depends on your use case specifics and personal preference, but fstab works in kernel space and should be faster than gvfs that works in user space.
You should consider doing a systemd mount with a systemd automount for the share. No need to mess with fstab or manual mount/automount commands, the NFS share will automatically mount when you try to access the path. You can also define how much idle time can pass before it unmounts on its own.
True, but my recommendation for using systemd mounts and automount units wasn’t necessarily related to performance and more with eliminating user intervention for mounting/unmounting the filesystem, and also not having to manually edit the fstab file, which carries more risk.
I wonder why this isn’t installed by default and why the missing “d” in the package name, when it does provide the needed /usr/libexec/gvfsd-nfs binary.