From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1854 invoked from network); 27 Jun 2001 13:03:47 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Jun 2001 13:03:47 -0000 Received: (qmail 18727 invoked by alias); 27 Jun 2001 13:02:56 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15121 Received: (qmail 18709 invoked from network); 27 Jun 2001 13:02:55 -0000 Date: Wed, 27 Jun 2001 09:02:40 -0400 (EDT) From: Brian Harvell X-X-Sender: To: Bart Schaefer cc: Andrej Borsenkow , Subject: Re: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF) In-Reply-To: <1010627074605.ZM5083@candle.brasslantern.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 27 Jun 2001, Bart Schaefer wrote: > > I think the question should always be "Any real reason to change the > current behavior?" So far I think not. > You could make the security argument since it's like having '.' at the front of your path. If there was some bug found that would let a user change the inode data of a file but not overwrite the file they could remove execute bits to something like ls and put their own somewhere else. I know that's far fetched but it might be nice to make it an option if it's not that difficult. Brian -- Brian Harvell harvell@aol.net http://ToolBoy.com/ echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc