Also, all those tracks with previously un-editable tags -- now editable. So, sudo is no longer required to do a make in $HOME. Perhaps using sudo for that in the first place created some of the problems, so in future, I'll check permissions first!
*I've been advised (thanks, Mamarok!) that 777 is a bad idea, since it gives permission to any and all. chown -R username folder/ is better.
Hmm this works but is a poor solution, what you just did is make everything in your home world readable (anybody with access to your system), including things like private keys, mails etc.
ReplyDeleteThis might not be an issue on your system but the proper change would have been to change the owner, not the access rules.
call is similar:
chown -R USER:GROUP path
This sets you as the owner of everything in your home directory, fixing permissions is mostly about setting correct owners.
Valorie, this command made everything in all your users' homes readable/writable for everyone on the system. It's complete overkill for solving a permissions problem, and returns security and privacy for your users' data to the levels of a Windows 95 system.
ReplyDeleteI strongly recommend *not* chmodding your home dir to 777. That means any user on your system has full access to modify and delete your files. That's totally not safe!
ReplyDeleteSomething like 755 or 644 would be better, and keep your files safe. Just make sure to leave the directories executable.
Hmmm, blogspot seems to be swallowing comments -- I approved three. This is the second time this has happened. If you have commented, and it hasn't shown up, please feel free to comment again.
ReplyDeleteI have a one-user laptop, and it is passworded, so security isn't a big concern. Can any of you recommend a site or article where I could read more about this? My solution solved my problem, but I certainly don't want to cause damage to my system.