This past week has been a computer nightmare… or at least a struggle. PopOS dropped a huge release and after installing it I was able to move my desktop back from a combination of OpenBSD and PopOS laptop to my minisforum twin 43in monitors. Only for one monitor to fail. After three days of diagnostics I was able used the PopOS restore/reset ad it finally started operating normally; granted I still need to reinstall my tools etc which is my major complaint about any and all OS that get tweaks or are not functional OOTB (out of the box).
And while I have documentation that could be executed as a script; I cannot actually. There are are too many usernames, passwords amd ssh keys. It’s gotta be an endless session of copy and paste… and reboots (.profile and fonts).
back in a minute I need a reboot.
No, this was not a BSOD moment… I had to restart my OpenBSD machine with my latest tmux config changes so I could copy them back to my PopOS desktop. Then I had to install the powerline fonts. Finally the reboot was necessary to get PopOS to recognize the font changes. But then maybe that was not necessary and I might only have needed to select the best terminal font which turned out to be the ubuntu-mono font.
back to the title
Let’s look at my lab’s hardware inventory.
Depending on the updates this can take about an hour to complete. Luckily ChromeOS and Android do not publish breaking changes very often but the independent publishers deploy a lot of updates. This is part of the release often strategy as developers do less formal testing and need reasons to hire teams of programmers and so on. (more game theory)
ChromeOS and Android are the ideal way to go about this… the layers of testing are deferred to Google.