Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles; site ea.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!inuxc!pur-ee!uiucdcs!ea!mwm From: mwm@ea.UUCP Newsgroups: net.unix Subject: Re: newgrp(1) - inconsistent - (nf) Message-ID: <13400012@ea.UUCP> Date: Tue, 7-Aug-84 02:49:00 EDT Article-I.D.: ea.13400012 Posted: Tue Aug 7 02:49:00 1984 Date-Received: Fri, 10-Aug-84 01:00:15 EDT References: <753@aecom.UUCP> Lines: 24 Nf-ID: #R:aecom:-75300:ea:13400012:000:941 Nf-From: ea!mwm Aug 7 01:49:00 1984 #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.