Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is a double post, but I'm not getting much help at gentoo forums.
I ran chmod 755 * -R in the #$@Q!ing root, instead of somewhere else. Stupid. I realized it when it got to /proc and gave errors. I can SSH in, but I cannot su to root. I still have the root session open though. I changed permissions on /bin/su to be owned by root, but I still get setgid: Operation not permitted setgid: Operation not permitted.
I know this is totally dumb and I should just rebuild. It's Monday morning and I actually have a busy week of work. I won't reboot, but I could lose that session. Can anyone think of a few things I should do to alleviate the pain a little? The first is getting root access whenever I need it. After that, it should all be fixable with some time.
Updates: Things I can't do but need to. First and foremost, su, as stated above. Ping I can live w/o, but it tells me:
ping: icmp open socket: Operation not permitted
YES: I will rebuild... but I can't now. Maybe not for a few days.
Any help is appreciated.
Yes, you will probably need to re-install to fix everything. On an RPM-based system a lot can be fixed with "rpm --setperms -a", but that only fixes those files and directories that the packages actually install, and I don't know if Gentoo has anything equivalent.
Don't feel too bad. Nearly everyone does it or something equivalent (in my case, it was overwriting the entire system trying to create a filesystem on a single partition).
The problem that remains is that none of the programs have setuid to root, and some programs have access that shouldn't (such as the encrypted password file).
This makes login difficult because some login utilities will not trust a shadow password file that is world readable (it may have been penetrated). It is hard to use su/sudo because both have lost the setuid bit.
The usual solution is to boot into single user mode, and (depending on distribution) force a reinstall to restore the correct permissions. Yo can fix the /etc/shadow file manually as that one is easy to identify, but finding all the others is harder unless you have a backup listing that has all that information (tripwire makes such a file for instance).
Yeah, that doesn't seem like a bad idea. You'd just have to periodically reboot to the new one to update the system. Part of my moaning about a lot of package-based systems is that if you wait too long, you're screwed and have to restart.