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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Suddenly my sudo stopped working. I am trying to mount usb to one of the directory
#sudo mount /dev/sdb /mnt/test
It throws me the error sudo: must be setuid root
Please let me know how to set the bit. Also for me chown/chmod is also not working.. buntu@ubuntu-desktop:~$ sudo chmod 4755 /usr/bin/sudo
sudo: must be setuid root
If you didn't do any updates/upgrades ... did you play with
chmod on the /usr directory?
If you didn't (I can't help but notice that your sudo is
ancient) I'd like to move this to Security as perms
changing spontaneously doesn't ring normal or healthy.
"Allowed"? As root (or user w/ sudo privileges) you can do
anything. Should you? Absolutely not. Unless you want to end
up in a situation like yours - it's certainly a great learning
experience.
To set things straight you can either boot or a rescue-cd and
fix the perms on sudo from there, or you could try booting into
single-user mode (not that I know how *buntu derivatives behave
when doing that in terms of root access).
To set things straight you can either boot or a rescue-cd and
fix the perms on sudo from there, or you could try booting into
single-user mode (not that I know how *buntu derivatives behave
when doing that in terms of root access).
I highly doubt that he going into rescue mode and fixing the permissions will solve the issue. mswamy78 mentioned that he may have used chmod, and I suspect that it was with -R, that's the only way he could have changed the permission on sudo binary. There will be other binary's as well which are not showing issues as of now but may at a later stage come up with an issue.
The best I can suggest is to reinstall. To save himself from all the troubles .
I also have this problem. I was the cause of it. During some computer problems, booted the laptop from a live CD. Since I was having some problems accessing the hard drive on the PC and was in a hurry, I did chmod -R 777 * big mistake, I now see.
Since you have chmod'ed the whole system, as it seems (in which directory have you done that?) it may also be possible that a clean re-install is the easiest and fastest solution for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.