Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42D273D7.1020800@byu.net> Date: Mon, 11 Jul 2005 07:27:51 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin@cygwin.com CC: "Jon A. Lambert" Subject: Re: Unwanted .exe appended to symlinks References: <1120880636.6400.7.camel@localhost.localdomain> <42CF4C9D.8000708@byu.net> <03d301c58616$166ad5f0$0200000a@agamemnon> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Igor Pechtchanski on 7/11/2005 7:20 AM: > > Yes, I believe Eric already posted that the bug is in the .exe magic > interacting with virtual devices. A workaround is to either use > > cat /dev/null >"$PGDATA"/postgresql.conf || exit_nicely Works. > > or (untested) actually create a stat'able /dev/null using the > create_devices.sh script from > . Won't work. stat("/dev/null") gets intercepted by cygwin before checking for an actual file named "null" in /dev/, so that the stat will succeed (and with the same data) whether or not you have run create_devices.sh. Perhaps creating /dev as a managed mount, though, and populating it with "null.", would work for coreutils 5.3.0-7 (but I wouldn't bother with such a convoluted workaround, especially since 5.3.0-8 will fix it). - -- Life is short - so eat dessert first! Eric Blake ebb9@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC0nPX84KuGfSFAYARAttJAKCFkU3o6udLTvWhvdJwFX+WWWRrjgCgn+VP x4MoG42dbV9KDs6onRQrhOI= =Pame -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/