newgrp(1) - inconsistent - (nf)

[mwm at ea.UUCP]

#R:aecom:-75300:ea:13400012:000:941
ea!mwm    Aug  7 01:49:00 1984

/***** ea:net.unix / aecom!naftoli /  9:31 am  Jul 29, 1984 */
Why were such pains taken to make the newgrp(1) command overlay
the current shell?  It seems to me that it's more natural to have it
fork off a seperate shell just like su(1) does.  In fact, I prefer
it that way.  Anyone else have any comments?
-- 
Robert Berlinger
...{philabs,cucard,pegasus,ihnp4,rocky2}!aecom!naftoli
"If you're not where you are, you're nowhere"
/* ---------- */

There are reasons for not wanting it to do behave that one. One good one
is that you can make it behave that way if you want to. With csh, try
adding "alias newgrp /bin/newgrp" to your .login. Worked like a charm on 4.1
(4.2 doesn't have newgrp, so I can't test it).

As to why you might want this: I create multiple shells with different
accesses, and use process control to bounce around among them to work on
different things.  I assume that layers would let you do similar things.

	<mike