From: Mike Brown <brown@mrvideo.vidiot.com>
To: cygwin@cygwin.com
Subject: Re: Latest cygwin.bat - need one
Date: Mon, 12 Dec 2011 08:01:00 -0000 [thread overview]
Message-ID: <20111212080104.GH4028@mrvideo.vidiot.com> (raw)
In-Reply-To: <Pine.NEB.4.64.1112120101590.29339@panix1.panix.com>
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
next prev parent reply other threads:[~2011-12-12 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 5:48 Mike Brown
2011-12-12 6:31 ` Mike Brown
2011-12-12 7:13 ` Tim McDaniel
2011-12-12 8:01 ` Mike Brown [this message]
2011-12-12 15:45 ` Ken Brown
2011-12-12 17:45 ` Mike Brown
2011-12-12 20:19 ` Jeremy Bopp
2011-12-12 20:28 ` Ken Brown
2011-12-12 21:24 ` Mike Brown
2011-12-12 21:30 ` Jeremy Bopp
2011-12-13 0:11 ` Gary Johnson
2011-12-13 1:38 ` Mike Brown
2011-12-13 2:07 ` mintty Mike Brown
2011-12-13 3:07 ` Latest cygwin.bat - need one Ken Brown
2011-12-13 4:24 ` Mike Brown
2011-12-13 3:12 ` Jeremy Bopp
2011-12-13 11:34 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111212080104.GH4028@mrvideo.vidiot.com \
--to=brown@mrvideo.vidiot.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).