this post was submitted on 18 Mar 2024
47 points (94.3% liked)
Asklemmy
43336 readers
820 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
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
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
Some time ago I wanted to clean up home directory files permissions to be not readable by group or others. Instead of just removing group/other permissions I hard-set all directories to 700 and all files to 600.
Took quite some time to repair not working scripts and "application containers".
Well I nuked myself with chmod -R on my home directory this morning... My day is now dedicated to reinstalling nixos on my laptop... Glad I didn't do this on a production server...
Will be extra cautious now with the -R commands
PS: I now see the need of timeshift despite of using nixos... I could have backed up my home dir... And restore the prev state
Imagine accidentally running it on / instead ...
But wasn't NixOS not specifically design to be protected against such issues?
I just did this to both Ubuntu and Arch in a matter of days.
๐ heck no! (Just found out)
Nix provides a platform where you define how the system should be by specifying what version of apps to install, and configurations to inherit.
It does not back up any configuration and files that are outside the defined configuration file! And Turns out there are plenty of them.
What, You changed into dark theme on your android studio? Stored on home dir .local, not on nix configuration file
Every app that I customized it whilst inside the app, the changes are thrown on .local.
Again... TIMESHIFT would have saved me sooo much time.
This is me Sangry now
Edit: I hope this post saves someone a world of pain in the future
I'm very confused, I don't see that
-r
is a valid option for chmod. What did you even do? I see no clarification anywhere in this post for what actually happened.I accidentally scrambled all the permissions on my home directory by running sudo chmod -R -755 .
The -R does this recursively through out every sub directory under /home/user/
While this looks somewhat innocent and harmless, most (if not all) files on home directory are owned by normal user. The above command just changed all files ownership to root (privileged user) which has alot of nuisance.
Effects:
It's a world pain by a thousand tinny cuts.
Hope this answers all your questions, and yes, it's -R, not -r
Solutions:
Hey uhm, are you sure? That seems wrong.
For me, the command removes read, write, and execute permissions of the user, and read and execute permissions for everyone else. Which would be expected.
chown
would be the command to change ownership...You could also try and fix the permissions by running
sudo chmod -R u+rwX g+rX /home/user
. That will fix all access permissions first of all. Then, you might have to fix execute permissions (but do this only on files that are meant to be executed!) usingchmod +x path/to/file
.Yes. But you (as the owner) would not even have needed
sudo
for thechmod
command to succeed. I think you might have just slightly misunderstoodchmod
's syntax. Your command as given means "recursively, remove the permissions 755 (you have a-
in front of them!). It sounds like you probably wantedchmod -R 755 ...
(without-
, giving read/write/execute to the owner and read/execute to everyone else). But the descriptive notation above is probably easier to remember. Read the manpage maybe...Very informative, thank you.
Why not just chmod +r