this post was submitted on 30 Dec 2023
150 points (94.6% liked)
Asklemmy
43945 readers
493 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
sudo chmod 000 -R /is very fun way of braking your system and is not widely known πCan you recover from that?
I imagine if you can mount from a busybox possibly
Then figure out the correct perms.
Eh, just hit it with the 777 and pray. Then swear at it some more.
Boot from a usb stick, mount the fs, use the live environmentβs chmod command to fix stuff.
I think you'll need to change passwd and shadow, maybe a few other files, but besides that it'll mostly work.
This is the traditional method.
Yeah that's the painful part. A backup would be key here
Worst case you boot up a virtual server with the same OS as your own and just go down the tree learning permissions, and itβs a deep dive learning experience.
chrootin and then syncing the permissions from something like the equivalent offilesystempackage in Arch for your distro should get you goingWhat does this do? nobody can read any file? would sudo chmod 777 fix it at least to a usable system?
The trick is that you loose access to every file on the system.
chmodis also a file. Andls. Andsudo. You see where it's going. System will kinda work after this command, but rebooting (which by a coincidence is a common action for "fixing" things) will reveal that system is dead.Yep. You could run chmod again to fix it (from a different OS / rescue USB), but that would leave all the permissions in a messy state - having everything set to 777 is incredibly insecure, and will also likely break many apps/scripts that expect more restrictive permissions. So the only way to fix this properly would be to reinstall your OS/restore from backups.
How are you gonna run chmod when you don't have permissions to use it anymore?