SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've never installed a SlackBuild script before, and I don't really know how it is supposed to be done, but I downloaded the truecrypt 4.3a slackbuild script from alien bob's site and ran it. It created a truecrypt tgz package in /tmp. I ran installpkg on that, and it installed. Maybe I did it wrong.
Immediately after running installpkg and before doing anything else at all, I tried to lock my KDE session because I was going to leave my computer for a while. It wouldn't lock. I logged out of KDE and tried to startx again and got a message "cannot execute startx: permission denied".
So I logged out completely and tried to log back in. Now I cannot login with my normal non-root account. I get "Cannot execute /bin/bash: Permission denied".
My root account is not affected. How can I determine what is wrong with my non-root account and fix it so I can login again?
I still get "Cannot execute /bin/bash: Permission denied"
I removed truecrypt package and it made no difference.
I had an earlier version of truecrypt installed, and it appears to still be installed. I compiled and installed it with the truecrypt install.sh script last year. It's version 4.2, and when I run truecrypt -V it reports version 4.2. Interestingly, that's what it showed after I did the slackbuild of 4.3a also.
I have two other non-root users on my system. I can't su to either of them.
One other thing. I noticed that my /lib directory had permissions 710, which seemed odd. That is, -drwx--x---. I changed it to 755 and tried to login my non-root user again. This time I was able to logon (YEAH!), but I got a different error message:
-bash: fortune: command not found.
Could it be that maybe the truecrypt source compile and install or the slackbuild I ran afterwards hosed some other directory and file permissions?
Can someone who has a Slackware 11 stock install with 2.6.18 kernel (the one from test26.s) post the results of ls-al from the root directory (that is, the "/" directory)?
In general, should most of the system directories have permissions of 755? Is there a reference system somewhere that I can compare my possibly hosed permissions to?
Ok looks normal and probably doesn't affect original problem. I did once install a package that messed up some file permissions.
You may want to try some other sig specs with kill. kill -l will list them. I seem to remember kill -s 19 is effective. If that doesn't work maybe you need to find out where truecrypt is starting from, stop it there, then reboot.
OK, so far I've changed /lib and /usr to have 755 permissions. Now I can logon my non-root users, the fortune command executes at logon, and I can startx. But KDE says that KDEinit can't find the firefox executable when I try to start firefox, so I clearly have some other permissions that have gotten hosed.
I think it's just a matter of figuring out what permissions need to be changed now. It would be nice if there were some way for me to just go set all the original distribution directories back to their stock permissions automagically, but I guess I'll have to do it the hard way.
Bummer. I wish I understood what happened to clobber all my permissions.
I believe I've fixed all the damage and I seem to be back to normal now. Thank you dive and mattydee.
NOTE: Just to be clear - the file system permissions damage was my fault, not the fault of the SlackBuild that I used. I simply didn't understand until this instructive episode how a umask of 027 for the root account, which is what is normally used for building and installing scripts that are intended to be world accessible, would affect file system permissions. Needless to say, my root umask is now 022.