Here’s how to mount an nfs share:
#cat /etc/systemd/system/mnt.data.mount [Unit] Description=nfs mount script [Mount] What=192.168.0.30:/mnt/tank/Media Where=/mnt/data Type=nfs4 [Install] WantedBy=remote-fs.targetI’ve always mounted network shares in fstab, what’s the benefit to doing it with systemd?
(Also, for those of you learning, this method only works on systemd-based distros)
Removed by mod
you can stop and start it via systemctl and systemd is going to make mounts for fstab entries automatically, I just put local drives in my fstab so that way I can copy mount files between machines
With these systemd mount files I don’t need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can’t be mounted then systemd won’t try to start docker.
Systemd can retry mounting based on the restart policy in case you have an interruption.
Kinda interested now, why would you use systemd script for this instead of fstab ?
With these systemd mount files I don’t need to touch the fstab, I can use ansible to copy the file, enable the service then start it. I can also have other services like Docker, Jellyfin or whatever to depend on that service. If the nfs share can’t be mounted then systemd won’t try to start docker.
Oh that’s actually really good reason with docker containers that rely on the NFS share. Thanks, I’m gonna steal this
So you can easily start and stop it as a service and you get your logging easily accessible via journalctl as a unit. But practically speaking there’s not much difference.
Yeap! You can even make an automount unit too! That way it’s mounted on demand! Makes life sooo much easier. I even do it for my external drives I use for backups
deleted by creator
I’ve had Linux problems before too when I was still trying to use it and I’d post the issues on like 4-5 different active forums and never get anything to solve it. So posting a meme acting like something is impossible seems like an amazing way to get instant help from the Linux knights.
and btw, the i never though about monting using systemd, no i came for the memes, and learned something
Fwiw, as someone also recently new to Linux, I thought this captured part of the experience brilliantly, and without malice.
Of course op probably went on to google (and find) the answer, so I agree with you that getting the answer with this post was probably not the point. But it’s a quality shitpost, and I endorse it! 😀
Linux user here, this would have been super helpful to me in the past. I don’t think it’s that the world is full of master Linux users that don’t post, it’s that new people need more help and have more questions.
An now explain how to setup Kerberos
What=Kerberos Where=pamNo idea, I don’t use Kerberos.
Oh that’s easy! I have this friendly multi-page PDF that assumes you have an active directory domain already (god rest your soul if you’re raw dogging kerberos and ldap raw) that walks you through the instructions step by step and…
mount.nfs4: access denied by server
Meanwhile I found a solution using fstab.
What’s the advantage of using a systemd script?
I’ll probably switch to simple script, since I don’t like the idea of my laptop shouting my NAS access credentials into any available random network on startup.
How would you do this with fstab? (Working with an smb share which I’m assuming is standard)
I described what I did here.
You may want to consider adding nofail and x-systemd.device-timeout opinions on the mount as well if the NFS isn’t critical to the device booting, and speed up your boot process a bit.
That sounds useful, thank you very much.
Googling an issue and copy pasting the first terminal code you see on the first result.
It looks like the command you're trying to paste contains danger---yes, yes I know what paste is let gooooo
rm -rf --no-preserve-root /Best practice
My wifi stopped working
Googling is so difficult for a Linux noob, and it takes a whole weekend to go through forums looking for solutions and commands to paste. I’m having much more success asking ChatGPT. ChatGPT and the Steam Deck have been the biggest factors in making me use Linux more and more.
Oh wow, why haven’t I thought about asking chat gpt? That seems like a good place to start.
I remember when Valve first announced SteamOS in 2013. It made me start to tinker with Linux. I ended up setting up and breaking (so much breaking) an OMV install on my old gaming PC turned NAS.
[ $[ $RANDOM % 6 ] == 0 ] && rm -rf --no-preserve-root / || echo *Click*Or a version for pussies:
[ $[ $RANDOM % 6 ] == 0 ] && echo '*You dead*' || echo '*Click*':() :;:
deleted by creator
man you need --help
man, you need
manmanis intenseWHAT IS A
man?! hurl goblet …a miserable pile of secrets…!
I use SSHFS and some pretty simple helper scripts for all my shared folder needs. Works pretty well IMO. I’ve never really used NFS nor mounted SMB shares on a Linux machine.
Something that works fairly well for me:
- Make a copy of the file you’re working
sudo copy /etc/fstab /etc/fstab.bak - Ask a particular question to ChatGPT
How do I mount a samba share in Ubuntu Server 22.04? - Read through the commands and try them out. ChatGPT is great for stuff like this, especially with follow-up questions, and giving you detailed info on error messages.
- If you fubar, then simply restore your backup file and try again.
- ChatGPT gives bad command, system fails to boot
- Drops into emergency shell
- Ask ChatGPT how to fix fstab from emergency shell
- Goto 1), rinse and repeat
You can also replace ChatGPT with Devin and achieve the same results*
*Your mileage may vary depending on the quality of your Devin
- Make a copy of the file you’re working
Me, trying to create a compressed tar archive
Compress Zee Vucking Files: tar -czvf out.tar files.
I know the image you mean, but I can’t find it.
I always say out loud “Compressed Zipped Verbose File” or “eXtract Zipped Verbose File”
I saw that you figured it out using
fstab. Since it’s a network share, you may wanna check outautofstoo.I’ll definetly look deeper into this, thank you very much.
This is why the year of the Linux desktop will never come, common Linuxcuck L, many such cases!
