RealLarry wrote: ↑Wed Dec 29, 2021 7:05 am
Attached is my NFS mount script. Place it into /media/fat/Scripts and run it once.
Based on cifs_mount.sh but totally revamped. Feel free to use and comment.
Hi, I've just got my MiSTer and I'm in the process of setting it up and the first thing I wanted to do after getting it installed and updated was to point it at my NFS server...which is how I've ended up here.
Many thanks for providing a pre-built kernel image with NFS enabled as it's saved me having to so it.
I was just looking at your mount script, and due to some broadband issues over the weekend (my service has been going up and down) I just spotted something that I'm curious about in your mount script.
When wait for server is enabled, why is it checking for IP connectivity by pinging google rather than the NFS server?
Was this done for a specific reason? It would make more sense (at least it would to me!) to ping the NFS server, I can't image there are many people who have their NFS server in this situation external to their LAN (or subnet).
If it's purely connectivity that is desired, then then pinging 1.1.1.1 with a TTL of 1 would at least limit the check so that DNS resolution is not required, but it would at least check that connectivity/routing as far as the gateway is at the very least working.
I really appreciate you providing both the kernel and the script as they'll be a big time saver, but it was just something I noticed, mainly because at that exact moment, my broadband went down and I was a little confused as to why it thought there was no IP.