Ok, so that went just fine @theitsage and then the upgrade to 10.12.6ß went as expected as well.
One thing that haunts me is that I really feel like we need to have a safety net in place by getting ssh working in single user mode "just in case." I had a situation where this was needed recently and I'm en route to get that going.
Having something like /start_ssh with the following contents might work, but I've not been able to test it and work out the kinks yet:
#!/usr/bin/env bash
mount -rw /
launchctl load /System/Library/LaunchDaemons/com.apple.kextd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.notifyd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.configd.plist
launchctl load /System/Library/LaunchDaemon/com.apple.DirectoryServices.plist
launchctl load -w /System/Library/LaunchDaemons/ssh.plist
systemsetup -setremotelogin on
And then of course setting that `chmod +x`.
That way if everything comes crashing down and you start your system with cmd-s, you can just blindly fire off that script and then be able to ssh in as usual to do recovery work, even if it's more in-depth than just needing to modify the usual files.
One thing that haunts me is that I really feel like we need to have a safety net in place by getting ssh working in single user mode "just in case." I had a situation where this was needed recently and I'm en route to get that going.
Having something like /start_ssh with the following contents might work, but I've not been able to test it and work out the kinks yet:
#!/usr/bin/env bash
mount -rw /
launchctl load /System/Library/LaunchDaemons/com.apple.kextd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.notifyd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.configd.plist
launchctl load /System/Library/LaunchDaemon/com.apple.DirectoryServices.plist
launchctl load -w /System/Library/LaunchDaemons/ssh.plist
systemsetup -setremotelogin on
And then of course setting that `chmod +x`.
That way if everything comes crashing down and you start your system with cmd-s, you can just blindly fire off that script and then be able to ssh in as usual to do recovery work, even if it's more in-depth than just needing to modify the usual files.