Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <398F0F75.82839993@veritas.com> Date: Mon, 07 Aug 2000 12:35:17 -0700 From: Bob McGowan Organization: VERITAS Software X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin@sources.redhat.com Subject: Re: Some comment about Cygwin1.1.4 References: <398EF5AD.97DC2CEC@onera.fr> <200008071749.NAA01544@envy.delorie.com> <398EFA1C.6EC280E7@onera.fr> <200008071834.OAA01863@envy.delorie.com> <398F0A7F.CD49D864@vinschen.de> <200008071916.PAA02265@envy.delorie.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit DJ Delorie wrote: > > > echo $BASH_VERSION ? > > No, because if you run sh from bash, it may inherit that environment > variable. By default, it should not be exported, but a user could export it themselves. How about a double check of RANDOM? If it gets exported, the inherited value in (a)sh appears to be constant, while in bash it changes with each access. The only problem I can see with this is that a user could unset RANDOM, then make a new variable with that name, but which will not have the special feature. I would think that this is rare enough to maybe be ignored? -- Bob McGowan Staff Software Quality Engineer VERITAS Software rmcgowan@veritas.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com