Moving an issue from here as Sorgelig doesn't want to adapt this to MiSTer's Linux-Build.
Maybe you will adapt two lines of code (umount ... and dhcpcd -k) to dont_download.sh just before line 1148 ("reboot now") to ensure a proper reboot of MiSTer for those user who are using network mounts and/or "advanced networks" like I'm doing.
I'm running a well hung local DHCP/DNS setup, which is setting top-notch names in my local DNS zone. When rebooting the MiSTer, dhcpcd (the init script) doesn't release it's IP and DNS, so the DNS record is "already set" and the DNS server grumbles about this.
This is tolerable, but from time to time the DHCP server argues that "this IP address and DNS record is already in state and active", > gives another IP and the DNS record ("forward map") fails. So no resolvable name and an unknown IP.
A proper fix would be easy by instructing dhcpcd to release it's settings just before shutting down the network interface:
> As you can see, in my case I'm unmounting all possible network ressources I'm using somethimes just to be sure. A shutdown of the network interface _without_ unmount leads to a hanging system when rebooting. If nothing is mounted, the unmount command keep quite and is doing nothing.
Moving an issue from here as Sorgelig doesn't want to adapt this to MiSTer's Linux-Build. Maybe you will adapt two lines of code (umount ... and dhcpcd -k) to dont_download.sh just before line 1148 ("reboot now") to ensure a proper reboot of MiSTer for those user who are using network mounts and/or "advanced networks" like I'm doing.