Sudo
- Thread starter bobw
- Start date
bobw
The Late: SuperMacMod
This is what I get;
ogin: setgroups: Operation not permitted
Welcome to Darwin!
[localhost:~] bob% su
su: setgroups: Operation not permitted
Password:
su: setgid: Operation not permitted
[localhost:~] bob% chmod 4111 `which sudo`
[localhost:~] bob% sudo
Sorry, sudo must be setuid root.
[localhost:~] bob%
ogin: setgroups: Operation not permitted
Welcome to Darwin!
[localhost:~] bob% su
su: setgroups: Operation not permitted
Password:
su: setgid: Operation not permitted
[localhost:~] bob% chmod 4111 `which sudo`
[localhost:~] bob% sudo
Sorry, sudo must be setuid root.
[localhost:~] bob%
what happened is that you failed to become root. try to enable root access from netinfo manager. its in your utilities folder. open it, click the padlock, and then choose security from the domain window, and enable root access.
if this doesn t work (for example, if it relies on sudo being functional, then it won t work), then we will try single user mode. report back, and i ll tell you how to do that.
do you have any ideas about how your permissions got screwed up? if there are other things with bad permissions, it might be hard to track them all down and fix them, so if we knew how it happened, we might have a better plan for undoing it.
if this doesn t work (for example, if it relies on sudo being functional, then it won t work), then we will try single user mode. report back, and i ll tell you how to do that.
do you have any ideas about how your permissions got screwed up? if there are other things with bad permissions, it might be hard to track them all down and fix them, so if we knew how it happened, we might have a better plan for undoing it.
bobw
The Late: SuperMacMod
Root is enabled. Tried that first.
I used Carbon Copy Cloner a week or so ago to clone my OS X partition to a spare partition on another drive. Worked perfectly, the spare is identical and boots and operates fine.
Added more software and wanted to clone again, erased the spare X partition from OS 9, tried using Copy Cloner again (from OS X) and it now gives me lessages for VolumeIcons.icns and other files below;
Sorry, sudo must be setuid root.
I used Carbon Copy Cloner a week or so ago to clone my OS X partition to a spare partition on another drive. Worked perfectly, the spare is identical and boots and operates fine.
Added more software and wanted to clone again, erased the spare X partition from OS 9, tried using Copy Cloner again (from OS X) and it now gives me lessages for VolumeIcons.icns and other files below;
Sorry, sudo must be setuid root.
well i don t know too much about carbon copy cloner. my fear is that there are going to be lots of permissions problems. but lets assume for now that sudo is the only thing with problems.
restart your computer, holding command-s to boot into single user mode. when you get a command line, type mount -uw / to get the root partition read-write. then chmod 4111 `which sudo`
then exit the shell and it should boot to multi-user. let us know if this does it
restart your computer, holding command-s to boot into single user mode. when you get a command line, type mount -uw / to get the root partition read-write. then chmod 4111 `which sudo`
then exit the shell and it should boot to multi-user. let us know if this does it
no sweat. sorry we couldn t get this one resolved. for the sake of closure, i would like to discuss just a little further.
i can t imagine why the machine would freeze while booting single user. in theory, if it booted single user properly, you would have unrestricted root access, and could change the permissions. do you recall what the error message was when it froze?
i have no idea what went wrong with the carbon copy clone, but i would find it hard to believe that the only thing affected is the permissions of sudo. so i would expect there to be some subtle system wide discrepency in the permissions. for this reason, i think that even if you had managed to change the permissions of sudo in single user mode, you still would have had unforeseen problems cropping up from time to time. so all things considered, perhaps wiping the drive and reinstalling was the wisest course of action.
like i said, i have not used this program, but i m going to take a wild stab in the dark based on your description for the point where the problem might have arisen. you said the system worked ffine after you cloned it, and only broke after you erased the original. so perhaps the cloning program relied on links to the original partition, and some invisible files remained there in use. like perhaps your new partition was relying on user informations from the netinfo dB still on the original partition, and when you erased it, UIDs got mixed up and permissions went haywire. just a stab in the dark.
i have seen threads on the boards discussing the permissions issues that can arise when doing system backups, so maybe one of those experts will come in here and have something more intelligent to say than i.
even though i think it was the best decision for you to reformat, i think we should still try to understand what went wrong, so that we can avoid it in the future. however i m out of ideas.
i can t imagine why the machine would freeze while booting single user. in theory, if it booted single user properly, you would have unrestricted root access, and could change the permissions. do you recall what the error message was when it froze?
i have no idea what went wrong with the carbon copy clone, but i would find it hard to believe that the only thing affected is the permissions of sudo. so i would expect there to be some subtle system wide discrepency in the permissions. for this reason, i think that even if you had managed to change the permissions of sudo in single user mode, you still would have had unforeseen problems cropping up from time to time. so all things considered, perhaps wiping the drive and reinstalling was the wisest course of action.
like i said, i have not used this program, but i m going to take a wild stab in the dark based on your description for the point where the problem might have arisen. you said the system worked ffine after you cloned it, and only broke after you erased the original. so perhaps the cloning program relied on links to the original partition, and some invisible files remained there in use. like perhaps your new partition was relying on user informations from the netinfo dB still on the original partition, and when you erased it, UIDs got mixed up and permissions went haywire. just a stab in the dark.
i have seen threads on the boards discussing the permissions issues that can arise when doing system backups, so maybe one of those experts will come in here and have something more intelligent to say than i.
even though i think it was the best decision for you to reformat, i think we should still try to understand what went wrong, so that we can avoid it in the future. however i m out of ideas.
bobw
The Late: SuperMacMod
I didn't erase the original, I continued to use it, worked fine. After adding more software I wanted to clone it again to have an exact backup on the other drive. That's when the problems started. I erased the cloned partition and tried cloning the original again. The first time I did this the program, Carbon Copy Cloner worked fine. I guess I srewed up something. Tough gettin the hang of a new system, especially one so complicated with permissions, etc.
Thanks
Thanks