fl42v

That's the scariest horror story in 2 words I've seen so far

Nah, that's when the fun really starts! ;)

Well, on the upside, it definitely works better than coffee or energy drinks :D

Also, nice save with the last one!

Been there with sudo. Fortunately, su still works, as well as going to another tty and logging in as root. Well, as long as the root login is enabled; otherwise that old hack with init=/bin/bash may work, unless you've prohibited editing kernel cmdline in the boitloader or decided on efistub

Been there, and even without encryption: took me to reinstall a few times before I realized I can chroot again and repair 😅

Wow, the last one is quite unexpected. What a useful command

You mean you've removed the service partitions used by windows and grown the main one into the freed space? Than yes, it's not the way. 'Cause creating a new partition instead of growing the existing one shouldn't have touched the latter at all :/

Oh, I just remembered another one or three. So, resizing the partitions. My install at the time had a swap partition that I didn't need anymore. Should be simple, right? Remove the partition and the corresponding fstab entry, resize root, profit. Well, the superblock disagreed. Fortunately, I was lucky enough to be able to re-create the scheme as it was, and then take my time to read the wiki and do the procedure properly (e2fsck, resize2fs and all that stuff).

Some people I've met since, unfortunately, weren't so lucky (as far as I remember, both tried to shrink and were past mkfs already) and had to reinstall. The moral is, one does simply mess with superblocks; read the wiki first!

You can dump the permissions from the working system and restore them. Quite useful when working with archives that don't support those attributes or when you run random stuff from the web 😁

Daaem, I guess the poor dude at the receiving end did not consider it particularly fun. Well, at least they had sbin working, so probably possible to recover without a live cd. Huh, guess who's now spinning up a VM to check it out 🤣

Checked it out: on arch that results in inability to run tty on reboot, then you're dropped into initramfs's rescue shell where you can simply +x new_root's /usr/bin/* and be back up and running

Yeah, a very unfortunate one: probably, the most painful to recover from. I'd just reinstall, honesty 😅 At least with mine I could simply add the necessary stuff from chroot or pacstrap and not spend a metric ton of time tracking all the files with incorrect permissions

Meh, idk tf he says he understands. Like "make [ported adobe CC] popos-exclusive": sure, big brain, how's that supposed to work, exactly? Or "there are 3 desktops ppl GAF about": riiiight, me along with other wm users aren't ppl anymore, apparently.

The whole video pretty much boils down to "I don't need X, hence nobody [«meaning the vast majority of ppl»] needs x". By the same logic, the "vast majority" doesn't need CC either, it's mostly necessary for professional designers, etc 🤷

I mean it's probably possible to choose the windows route and go "we make one steaming pile of garbage that kinda works everyone but perfectly - for nobody", yet linux distros so far have been pro-choice and pro-customization. You want "just works"? Sure, go with X, Y, and Z distros. Wanna something specifically tailored for your workflow? You may start with the same and replace/modify stuff, but also I, J, and K are a great base to build your future setup from the ground up and avoid banging your head against the wall while figuring out what drugs their devs were on. And the same goes for DEs/WMs: gnome is, gnome also works, yet if you want to change it significantly, you'll either have to mess with extensions or maintain a fork of a huge codebase you don't fully understand and most of which you don't exactly need. So, building from scratch may just be an easier solution.

Technically, you can also PR, yet it can easily be rejected, and then you're back to forks.

Unix is like franchising: you can be perfectly SUS, yet no money = not Unix