Date: Fri, 28 Oct 2016 09:40:57 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: Interesting $0 Problem Message-ID: <5a4f0424-cdfa-bd44-9de2-b4860d121584@tundraware.com> In-Reply-To: <516bc76f-f14c-e9a5-a246-2e915a5369ce@qeng-ho.org> References: <b859f7a3-51d1-06f4-e793-332edd212068@tundraware.com> <516bc76f-f14c-e9a5-a246-2e915a5369ce@qeng-ho.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/28/2016 03:34 AM, Arthur Chance wrote: <SNIP> > > > Prepending a dash to a login shell has been standard behaviour since the > BSD days at least. I think it was in version 6 of the original Bell Labs > Unix as well, but after three and a half decades my memories for such > details are a bit hazy. Anyway, it's a standard marker. > Thanks to all who took the time to answer what turned out to be a really stupid question on my part. It's odd that I've never run into this in over 3 decades of working on *NIX ... So now, can someone perhaps answer a couple of other really dumb questions: When is it useful for a script to know it's running in a login context vs. a child of the login shell? Is there another way to determine if your current shell is the login shell? This is more intellectual curiosity than anything ... ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5a4f0424-cdfa-bd44-9de2-b4860d121584>