yep all my files look that way......all i need to do i set the suid bit
on /bin/su and i think that i'll be set.. :-)
~kurth
BTW anyone try mozilla M18? i'm using it now and i love it...i think
that i need a faster chip tho...this cel400 isn't cuttig it.......
:-)
~kurth
Benjamin Scott wrote:
> On Thu, 2 Nov 2000, Kurth Bemis wrote:
>
>> i can't su to root anymore....look what i get..
>>
>> ================snip===========
>> usa:kurth[~]$ su
>> Password:
>> initgroups: Operation not permitted
>> usa:kurth[~]$
>> ===============snip============
>>
>> i'm in the group root...i don't have a wheel group..
>
> Well, the immediate problem is that when su(1) called initgroups(3), which
> is part of the process of changing your identity, it returned an error of
> EPERM. Given your previous crisis, I'd suspect you missed changing the
> ownership on something somewhere, or a file mode got changed as well
> somewhere.
>
> You might try running an strace(1) on /bin/su and looking at the arguments
> that are getting passed to the low-level system calls. You might find some
> clues there.
>
> Here's a directory listing of some files from my Red Hat system... compare
> it to yours and see if that yields any insight. In particular, check the SUID
> bit on the /bin/su file.
>
> -rwsr-xr-x 1 root root 14k Mar 7 2000 /bin/su*
> -rw-r--r-- 1 root root 553 Aug 10 14:05 /etc/group
> -r-------- 1 root root 456 Aug 10 14:05 /etc/gshadow
> -rw-r--r-- 1 root root 1.0k Oct 5 10:28 /etc/passwd
> -r-------- 1 root root 890 Oct 13 09:11 /etc/shadow
>
>
>> i'm using debian... that should answer a lot of your questions right
>> there....
>
> Pitty. If you were using an RPM-based system, "rpm -Va" would likely find
> the problem.
>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
