Follow-up from “Dumbest Thing you have done distro-hopping?”.
Here’s mine - the laptop from which I’m typing right now has a broken touchpad that keeps jumping and clicking randomly, and does not work. Well, I can’t afford to fix it, but at the moment, I was so pissed off I punched the touchpad really hard, and the machine panicked with all the lights blinking. A few more revival abuses, and the machine was back to life, but since I was running a nixos-rebuild switch --upgrade in the background, I blew off my boot partition. I think I just broke the unbreakable distro.
In 2000 I was running my first Linux homelab server, I ran chmod -R 666 /, it did not end well.
I came here to comment basically this. Except I did it last year and accidentally broke that system. Was trying to do the working directory and mistyped and did the root dir.
For those that don’t know, so many elevated permissions commands fail if permissions are too open. And even ssh breaks because your certs and authorized_keys need to be only readable by you.
I luckily was able to wipe and just restore an older image backup.
Yeah and you also need execute permissions to read what’s in a directory, so 666 for the whole system means you basically lose access to 99% of files
Yes, I learned very quickly that +1 in this flag syntax means execution, so first 6 means that owner of the file does not have execution permission, which means that nothing is allowed to execute in the system.