Configuration reload issues…
-
So as I wrote elsewhere, my CF card burnt out, and I had to reinstall (this time on a full-fledged SSD).
Easy as pie right?
- install the OS on the box, which gets an IP address assigned in the lan
- restore configuration, reboot
Not quite: after the reboot, the box will have, for it's current location an invalid configuration, and e.g. all the package reinstalls will fail.
Solution:
- install the OS on the box, which gets an IP address assigned in the lan
- restore configuration, reboot, pull power when the system is trying to restart
- move box to it's proper location, hook up WAN, etc.
- power on
Wrong! At least wrong if you have Verizon FiOS which doesn't take well to having the router swapped, and takes hours until it gives a new router a valid DHCP lease. Needless to say, again, all the package re-installs fail, and the box ends up in a half-assed state.
Sure, it can be fixed: hours later, just restore the configuration a second time, and just to be on the safe side, later on reinstall all optional packages manually, then upgrade to the latest snapshot, with gitsync and hopefully now everything is back to normal.
Still, it would be kind of nice, if the whole procedure of the restore could wait until the WAN interface is BOTH up (incl. valid DHCP lease) and has internet connectivity, and would continue only then. In a normal case, this would probably ad just a few seconds to the overall time it takes to restore a configuration, but in a pathological case as with Verizon's setup, it would save a lot of time, even if it would take hours to finish.
