After modifying /etc/fstab, I ran mkinitrd (as root) and it installed in /boot
But the noauto and soft options don’t seem to be effective on the next system reboot.
The system is still looking for the crypto key during boot, and the nfs startup process is still hanging for the default 5min 30 sec timeout.
Might this be a systemd issue?
Is there additional magic (in addition to mkinitrd) to updating what should go on during boot?
I first used autofs with solaris (I think it had a different name). Back then, the linux automounter didn’t have very good reputation. The solaris one worked well. So when I wanted NFS with opensuse, I decided it was time to check whether the linux automount was doing better. Thus far it has worked pretty well.
Without automount, you can get into a situation where you have a network of several computer each of which has to be booted first >:(
Although this is a desktop, I tried running the Network via Network Manager, since Network Manager when running on a laptop seems to gracefully boot when it can’t reach nfs mounts. But that in fact does not seem to be the case.
Now that I have autofs working, I wish I had made the shift a while ago.
I prefer nfs (and autofs) over Samba (which seems to generally work very well now in 13.x) as I have encound=tered some applications which will not browse to Samba folders/files but are OK with nfs shares.
“soft” is unrelated to mounting. It means system will stop access to mounted NFS filesystem after timeout if server does not respond. Opposite is “hard” where system will retry access to non-responsive server indefinitely. What did you intend to achieve with this option?