Yeah, until sshd breaks due to incompatible dependency and I cannot login. There are exceptions though. For example, RedHat does a good job (in contrast to some other distros) and I always had auto update on for RedHat systems. Windows works like a Swiss clock in this regards, and it is the biggest selling point for me. Slap, update and forget. It just works then without any manual intervention, and most importantly, does not break things after updates.
> Yeah, until sshd breaks due to incompatible dependency and I cannot login.
I can't say I've every had that happen to me or anyone else I've dealt with. Do you have any references to relevant bugs/issues? A properly running package manager should not allow this unless there is a serious bug in the packages themselves.
The closest I can think of otherwise is someone getting locked out of a remote machine where root was the only active account and was authenticated buy user/pass not by key, and he accepted the "start blocking password logins for root" change in a distribution upgrade (so he was warned so his own fault!).
Even for updating domain controllers? This has not been the case for me. At the basic level pretty much any option will "just work", but for complex setups... I have found Windows to be difficult to use and difficult to learn about, with lots of proprietary software solutions for problems that should be easy to solve with the OS-provided tools, but aren't.
> until sshd breaks due to incompatible dependency and I cannot login.
I've never had that happen, but thankfully remote (virtual) serial consoles are commonplace. Something I wish was more common in Windows environments, as I've had remote access dump on Windows many times, leaving me with no options other than a long drive or call in to a remote DC.
