Little accident with chmod
Hi,
I was trying to get my canon mp540 to work in Slackware 13.37... (which it does now btw, so yay) While i was changing some permissions in /usr/lib/cups i somehow managed cd myself to /usr/lib and there i executed the beautiful command : chmod 777 * So... There are some 137 files with their permissions screwed up... Most stuff seems to work so that is not a real problem for now but I was wondering what are the consequences ? Do I need to fix this ? And ... how should I go about fixing it ? Thanks |
I would think that
Code:
cd /usr/lib |
Hello,
Most likely, you will be safe by running the following within that directory: Code:
chmod 644 * Cheers, Josh |
thanks,
I have no idea if the permissions were indeed 755... Is it some kind of well known fact that the default permissions on those files is normally 755 ? Is there any way to be sure that those were the correct permissions on all those files in /usr/lib ? |
Quote:
I'll try something like that... Would it be ill advised if I keep the permissions set to 777 ? |
Um, on my -current system it looks like directories are 755 (drwxr-xr-x) but at least some files are 644 (rw-r--r--)
Code:
root@xxxxxxxx:/usr/lib# ls -l | grep -e "-rw-" |
Thanks for the overview!
|
3 Attachment(s)
Most of the .la and .so files are 755 with the exception of a few.
I have attached what I have. |
Quote:
this is a somewhat odd response in an unrelated thread - but unfortunately you don't have private messages on the board enabled: when responding to the e-Mail you sent me earlier today my mail got bounced by hotmail with a 550 Requested action not taken: mailbox unavailable (state 14). Can you please contact Jeremy directly with your initial inquiry? Regards, Tink |
Quote:
I changed my LQ settings and emailaddress (was still using an old one that has been disabled). |
All times are GMT -5. The time now is 05:56 PM. |