So, just a light post, I upgraded my Pi4 last night and found the Linux firmware breaks a 32bit install.
I’ve been meaning to change to 64bit for months, but as it’s my DMZ box for torrents, radicale, etc, then it’s just finding the right time to convert an adhoc setup into my ansible scripts.
Luckily I had a SD backup from September to get it running again
So, what have you broken over the holidays?
I don’t do upgrades (well, not in the sense most people think of them).
My approach is that upgrades are too risky, things always break. It’s also why I don’t permit auto updates on anything. I’d rather do manual updates than dedicated time. Keeping things working is more important, and I have backups.
I run everything virtualized (as much as I can), so I can test upgrades by cloning a system and upgrading the clone. If that fails, I simply build a new system based on some templates I keep. Run in parallel, copy config and data as best I can, then migrate. Just migrated my Jellyfin setup this way.
This is a common methodology in enterprise, which virtualization makes a lot easier for us self hosters.
I haven’t had a disruption from updates/upgrades in 5 years.
It’s not common in enterprise to not auto-update.
It’s extremely common…most production lines I’ve ever been to only do manual updates on equipment, if any at all.
Depends on the company and the system. Some of them need to be done off-hours while people aren’t using them. Some are HA and/or insignificant enough that you can do them any time without interruption.
I have not had any auto update in my entire career but i have always been on the infra side so it was never just my app. Though I do wish the update/outage process would be updated to reflect kubernetes and not just think of everything as monolithic servers.
It’s also not uncommon in enterprises that things break needlessly.