Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!columbia!cunixc!nwc
From: nwc@cunixc.columbia.edu (Nick Christopher)
Newsgroups: comp.os.minix
Subject: Re: ST Minix/Zenith Eazy
Message-ID: <645@cunixc.columbia.edu>
Date: 30 Apr 88 15:41:58 GMT
References: <2243@ubc-cs.UUCP>
Reply-To: nwc@cunixc.columbia.edu (Nick Christopher)
Organization: Columbia University
Lines: 33

To: ncoverby@ndsuvax.UUCP
Subject: Re: /lib/cem /lib/cpp
Newsgroups: comp.os.minix
In-Reply-To: <858@ndsuvax.UUCP>
References: <964@unccvax.UUCP> <647@naucse.UUCP> <621@cunixc.columbia.edu>
Organization: Columbia University
Cc: 
Bcc: 


I eventually found the problem on my own.  Its a bug (I think) is su. 
The problem was that:

su root != login root

i.e. there are lots of things you can do when you originally login as root
that you can not if you su to root.  For instance rm does not override
protections as su-root but does as login-root. Also su-root can not use chown.
I thought that su'ing to and id made you have that ID's uid and that programs
checked the uid.  Well if I am right and su is broken maybe I'll fix it and
post it.

\n
-- 
		"I am the Lorvax. I speak for the machines."
______________________________________________________________________________
nwc%cunixc@columbia, columbia!cunixc!nwc  BITNET: nwcus@cuvma 
            USENET: topaz!columbia!cunixc!nwc
-- 
		"I am the Lorvax. I speak for the machines."
______________________________________________________________________________
nwc%cunixc@columbia, columbia!cunixc!nwc  BITNET: nwcus@cuvma 
            USENET: topaz!columbia!cunixc!nwc