From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from odin.INS.CWRU.Edu ([129.22.8.102]) by hawkwind.utcs.toronto.edu with SMTP id <2753>; Mon, 19 Apr 1993 08:03:21 -0400 Received: by odin.INS.CWRU.Edu (5.65b+ida+/CWRU-1.5.4-ins) id AA08814; Mon, 19 Apr 93 08:02:50 -0400 (from chet for rc@hawkwind.utcs.toronto.edu) Date: Mon, 19 Apr 1993 07:59:00 -0400 From: Chet Ramey To: davidf@golem.waterloo.on.ca Subject: Re: rc 1.5 Cc: rc@hawkwind.utcs.toronto.edu Reply-To: chet@po.CWRU.Edu In-Reply-To: Message from davidf@golem.waterloo.on.ca of Sat, 17 Apr 1993 07:51:55 -0400 (id <9304170751.aa04405@golem.waterloo.on.ca>) Message-Id: <9304191159.AA08714.SM@odin.INS.CWRU.Edu> Read-Receipt-To: chet@po.CWRU.Edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii > Actually, /bin/sh, /bin/ksh, and the POSIX.2 shell all check > the current directory for a file named "test", and _then_ > search the path for a file named "test" which is also > executable. This is not true, except in some older versions of sh. Current versions of sh do not do it; I don't think ksh ever did. Posix.2 specifies that only a path search is performed. The current directory is not searched unless it is in $PATH ``to avoid introducing suceptibility to trojan horses that a user might be trying to avoid by leaving `.' out of $PATH.'' Chet -- ``The ballpark is quiet now, save for the sound of droplets landing. That is as it should be. For today there are two fewer boys of summer.'' Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu