One time I did `apt-get upgrade` on debian and my terminal stopped rendering text. And when I restarted my computer it couldn't find the boot partition.

nostr:nevent1qvzqqqqqqypzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hszyrhwden5te0v5hxummn9ekx7mp0qyv8wumn8ghj7enpvf5kzm3wdehhxarjxyhxxmmd9uqzp8mgrsgrlkl4ammc7dqq0ddynag3t3t6sum8j09vnd8ftnm8m6rwvuwhjl

Reply to this note

Please Login to reply.

Discussion

Debian likes update foreplay before going straight to upgrade

Yes, also anytime serious warnings are issued to you from apt before an upgrade is a bit of a quick scare

when I was learning linux I just make sudo chmod 777 -R / to stop asking for folder permission and corrupt the system, I became unable to shutdown using the system or connect pendrive

Reminds me of that time that I deleted an iSCSI disk (disk no. 5) and then disks no. 6, 7 and 8 for some reason were renamed automatically, on-the-fly, to no. 5, 6 and 7. Fileserver started writing to the mailserver disk, mailserver started writing to a webserver disk, etc. Shit was beyond repair and I spent much of the weekend doing disaster recovery

This was also the weekend I was taught the disadvantage of RAID 5 the hard way (it's slowwww 🐌), RAID 10 ftw

lol that sounds extremely painful

nodejs isn't the nightmare it was 6 years ago but it's still pretty nasty, i mostly don't have any problems these days, but back then, endless problems with dependencies in NPM and version this and polyfill that

Yeah, it's marginally better, but now the complexity comes from the million different toolchains that arose in an attempt to fix the require/esm compatibility stuff, plus typescript