Hello everyone:)
I ran the command sudo chown -R <username> /usr/bin
, to be able to save files with VScode.
Was that a bad idea?
EDIT:
It wasn’t the /usr/bin
folder. It was the /bin
folder.
Hello everyone:)
I ran the command sudo chown -R <username> /usr/bin
, to be able to save files with VScode.
Was that a bad idea?
EDIT:
It wasn’t the /usr/bin
folder. It was the /bin
folder.
I don’t know what /etc/bin
is but if you did that with /usr/bin
, then, yes, that was a bad idea.
Many of your commands probably don’t even run anymore. I suspect you can no longer use sudo
for example.
Switch to a TTY, login as root and then run sudo chown -R root /usr/bin
Thank you for your answer.
I’m so stupid. It wasn’t the /usr/bin
or /etc/bin
folder. It’s the was the /bin
folder.
Is /bin
problematic?
Is it a problem to have “/home/(user)/bin” instead?
(user) = name of your regular user to log in
I first saw this with Bunsen Labs Beryllium.
That is the same as /usr/bin
. /bin
is linked to /usr/bin
Ordinary user should typically write only to the /home/“your-user-name” folder tree.
Only if you know exactly what you are doing, and you have a valid reason, you can write outside your $HOME folder. Otherwise you probably will create a security risk.
Note that well behaved apps should not typically write to folders other than under your $HOME.
If an app wants to write elsewhere, it should ask for proper permissions, and you must decide if the app should be given those rights.
Okay, i changed it back.
Many of your commands probably don’t even run anymore. I suspect you can no longer use
sudo
for example.
Every command I tried including sudo
still worked btw.
Thank u again for your response
Good to know!
Thank you too
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.