News for hackers. Stuff that matters.

A comment on Systemd as tragedy. Parent comment

Re:Systemd as tragedy by nonbirithm on Tuesday January 29, 2019 @04:43AM (#19025070)
Very recently I had this issue[0] as the result of a systemd upgrade, requiring the use of a recovery disk to downgrade to the previous version as the keyboard input had failed to be initialized.

[0] https://github.com/systemd/systemd/issues/11314

[ Parent | on HN ]
Re:Systemd as tragedy by majewsky on Tuesday January 29, 2019 @05:15AM (#19025197)
If this bug hits you in staging, no big problem, just don't promote that particular update to production. If this bug hits you in production, your lack of a staging environment is the bigger concern IMO.

(I have been hit by the same issue on my private notebook, but I have procedures in place to cleanly recover from failed upgrades on all systems, so it was not a big deal.)

[ Parent | on HN ]
Re:Systemd as tragedy by yjftsjthsd-h on Tuesday January 29, 2019 @06:07AM (#19025411)
"Yeah the software completely broke, but that's fine because you should be able to deal with that" does not make me feel better about the software in question.
[ Parent | on HN ]