From owner-freebsd-arch Tue Jan 16 15:29:26 2001 Delivered-To: freebsd-arch@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id D449537B400; Tue, 16 Jan 2001 15:29:08 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id A06E031BA; Tue, 16 Jan 2001 23:29:08 +0000 (GMT) Date: Tue, 16 Jan 2001 23:29:08 +0000 From: Josef Karthauser To: Marc Slemko Cc: John Baldwin , arch@FreeBSD.ORG Subject: Re: no newgroup/newgrp in FreeBSD? Message-ID: <20010116232908.D1731@tao.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from marcs@znep.com on Tue, Jan 16, 2001 at 02:50:41PM -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 02:50:41PM -0800, Marc Slemko wrote: > > A non setuid wrapper would still not provide the same functionality that > newgrp does, which is part of what I'm repsonding to. > > And login -f does not preserve things like environment, cwd, etc. like > newgrp does which matters when you have environment variables that vary > (eg. ssh authentication agent). And you are then logged in twice. I've often wished for this, when in sysadmin mode and logged into a remote server over a difficult to replicate method :) (like ssh over ppp over brian;). Joe > > Sure, there are lots of other ways to do nearly the same thing. > Including simply logging out and logging in again. The point is simply > that newgrp would not be a noop on freebsd if it were implemented and does > have some useful, if minor, functionality. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message