I'm switching from Windows to Linux Mint and want to improve the way I configure network storage before installing it on a new desktop. I have a Synology NAS sharing six folders over Samba. On my current system, I mount each share separately through /etc/fstab using a credentials file, with mount points such as /home/USER/mapped/books and options including x-systemd.automount, uid/gid settings, and broad file and directory permissions.
This works, but it means navigating through several layers of folders. I'm wondering whether mounting the shares under my home directory is a good approach, or whether they should go somewhere such as /mnt or /srv. Would it be better to mount all of the NAS content through one parent share, then create symbolic links in my home directory for frequently used folders such as Music, Books, or Videos?
I also use NFS for backups from another Linux system, while a Windows computer still needs Samba for now. Should I continue using Samba for these shares, switch Linux clients to NFS, or use both? What layout, mount options, permissions, and general setup would you recommend so the configuration remains easy to maintain and doesn't break applications that expect familiar folder paths?
3 Answers
Mounting under your home directory is valid, but I prefer a dedicated path such as /mnt/media or /srv/shared. Mount the larger storage location there, then use symbolic links in your home directory for the folders you access frequently. For example, /home/you/Music could point to /mnt/shared/music, while the complete NAS content remains available under /mnt/shared.
That gives you convenient paths without tying the network mount directly to your home-directory layout. If you use fstab, x-systemd.automount and nofail are useful so an unavailable NAS doesn’t unnecessarily delay boot. Also, avoid 0777 unless you specifically need those permissions; use appropriate uid, gid, file_mode, and dir_mode values instead.
Think about application compatibility before replacing standard folders. A symlink such as ~/Music pointing to the NAS can work well for media and documents, but network storage is not ideal for every application’s live database or configuration files. Keep those local unless the application explicitly supports network storage.
For fstab, make sure the mount point already exists, protect the credentials file so only your user can read it, and consider options such as _netdev, nofail, and x-systemd.automount. Test the mounts manually before relying on them during startup. The best setup is the one that gives you a simple everyday path while keeping the actual network storage clearly separated from your local home directory.
There isn’t one mandatory layout. Samba and NFS can coexist: Samba is useful when Windows clients need access, while NFS is often simpler or faster for Linux-to-Linux storage. The important part is deciding how the NAS shares are organized and what permissions each user needs.
If the NAS can export one parent directory containing the six folders, a single mount point can be convenient because new folders appear automatically. If the NAS intentionally exposes separate shares for security or permission reasons, keeping separate mounts is perfectly reasonable. Mounting each one under /mnt/ or /srv/, then linking selected folders into your home directory, is a clean arrangement.
A single parent mount would be easier to maintain, but I may need to adjust how the Synology shares those directories. I’ll check whether they can be presented as one shared hierarchy without weakening the permissions.
That makes sense. I was referring to symlinks when I said soft links. I’ll look at mounting a parent share under something like /mnt/shared and linking only the directories I use regularly. I’ll keep the NAS credentials in a protected credentials file.