From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21397 invoked by alias); 12 Dec 2011 08:01:35 -0000 Received: (qmail 21387 invoked by uid 22791); 12 Dec 2011 08:01:33 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,TW_RX X-Spam-Check-By: sourceware.org Received: from mrvideo.vidiot.com (HELO mrvideo.vidiot.com) (75.100.112.198) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Dec 2011 08:01:20 +0000 Received: from localhost ([127.0.0.1] helo=mrvideo.vidiot.com) by mrvideo.vidiot.com with esmtp (Exim 4.69) (envelope-from ) id 1Ra0os-0002yG-IA for cygwin@cygwin.com; Mon, 12 Dec 2011 02:01:06 -0600 Received: (from brown@localhost) by mrvideo.vidiot.com (8.13.8+Sun/8.13.8/Submit) id pBC814wQ011423 for cygwin@cygwin.com; Mon, 12 Dec 2011 02:01:04 -0600 (CST) Date: Mon, 12 Dec 2011 08:01:00 -0000 From: Mike Brown To: cygwin@cygwin.com Subject: Re: Latest cygwin.bat - need one Message-ID: <20111212080104.GH4028@mrvideo.vidiot.com> References: <20111212054801.GD4028@mrvideo.vidiot.com> <20111212063131.GE4028@mrvideo.vidiot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-12/txt/msg00264.txt.bz2 On Mon, Dec 12, 2011 at 01:13:02AM -0600, Tim McDaniel wrote: > On Mon, 12 Dec 2011, Mike Brown wrote: >> Doing some more digging I found >> the following posting (via google): >> >> > Does changing 'bash' to '/bin/bash' make a difference? >> >> Answering my own question: yes. >> >> There was a change in execvp()'s behaviour to no longer look up >> an executable in the current working directory, wasn't there? I >> can't find it in the ChangeLog though. >> >> You've got to be kidding. Why was the looking into CWD removed? > > PATH specifies the list of directories to search for executables. > So if execvp() ever used "." unconditionally regardless of PATH, > then it violated one of the most long-standing UNIXy rules. Yes, I know all about the "." security hole and have cleaned many things that used it. Even if execvp() was changed to no longer use ".", it should still use the default path for system executables. Cygwin does have a default, does it not? It would seem not, otherwise the absolute path to the shell wouldn't be required. Funny thing is that the rxvt program was found. Ya, I know, Windblows found it, because it does look in the CWD. But, once rxvt was started, wouldn't the default cygwin PATH be brought in so that executables can be found? Therefore execvp() shouldn't have an issue finding system executables. So, based upon what actually happens and the user doc, it seems that at startup, cygwin is deaf, dumb and blind regarding the executables in /bin. You'd think that cygwin would at least know that when it starts. Any particular reason why cygwin can't build itself a default PATH for system executables? MB -- e-mail: vidiot@vidiot.com | vidiot@vidiot.net /~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there. Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple