Date: Thu, 1 May 1997 22:20:15 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Cc: chet@po.CWRU.Edu Subject: Re: /bin/sh -c and ENV Message-ID: <19970501222015.EJ31428@uriah.heep.sax.de> In-Reply-To: <9705011332.AA06946.SM@odin.INS.CWRU.Edu>; from Chet Ramey on May 1, 1997 09:32:30 -0400 References: <87rafr6a0o.fsf@erlenstar.demon.co.uk> <9705011332.AA06946.SM@odin.INS.CWRU.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
As Chet Ramey wrote: > It's a bug. A post-publication POSIX.2 interpretation made it clear > that ENV should be executed only for interactive shells. Interesting. (And just braindead the other way round. I wonder why Mr. Korn didn't stick to the commonly used .foorc file, and had to invent this crap instead.) Do you have any reference for it? I notice that ksh93 is the only Bourne-alike shell on my system that doesn't... ah no, zsh doesn't source it either. My bash is probably way too old. I'm not using it except for comparisions. (In case you wonder why i think it's braindead the other way round: setting up something like your favourite $PATH for a remote shell execution is very easy if you're a C-shell user. It's totally impractical or even impossible for Bourne-alike shell users. bash excepted, it has a .bashrc as well.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970501222015.EJ31428>