Re: cygwin-1.7.13-1: mknod console c 5 1 creates invalid device

Dne 19.4.2012 19:21, Christopher Faylor napsal(a): Funny you should pick up on that. I actually had a sheet over my head with two eyes cut out when I was writing the ChangeLog. This should be fixed in the next snapshot. Just checked cygwin1-20120419.dll.bz2 and it fixes this problem. Thanks,

[ANNOUNCEMENT] Updated: openssl-1.0.1a-1, openssl-devel-1.0.1-1, libopenssl100-1.0.1-1, libopenssl098-0.9.8v-1

I've updated the version of OpenSSL to 1.0.1a-1. I also updated the 0.9.8 libs to 0.9.8v-1. This is an upstream security release. The Cygwin release is build from the vanilla sources. Here's the official security advisory: ---

Re: 1.7.10->1.7.13 : output from .NET programs does not get through pipeline to a visual c++ program

>On 2012-04-19 16:14, Christopher Faylor wrote: >> On Thu, Apr 19, 2012 at 12:56:33PM +0100, somebody wrote: >>> Hi all, >>> >>> This started in 1.7.10 and I thought this may be fixed in 1.7.12 due >>> to emails in the mailing list: >>> http://sourceware.org/ml/cygwin/2012-03/msg00666.html >>> >>>

Why /usr/bin/*.dll must be executable?

Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to find the real executable applications (*.exe). Since *.dll files are only libraries

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-20 21:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to find the real executable applications (*.ex

Re: Why /usr/bin/*.dll must be executable?

On 20 April 2012 15:02, De-Jian Zhao wrote: > Hi, > > When I type "cyg" and Tab, many executables starting with "cyg" are listed > (Display all 262 possibilities? (y or n) y). I find that many of them are > *.dll libraries under /usr/bin/. This is inconvenient to find the real > executable applicat

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to f

RE: 1.7.10->1.7.13 : output from .NET programs does not get through pipeline to a visual c++ program

I ran into similar issues, which seemed to be fixed in 1.7.12 - but if you are still having issues even on the current Cygwin version of 1.7.13, I'd be interested to know if they can be resolved. If it's anything like the issue I found, it has to do with erroneous pipe handling in Cygwin and nothi

Re: Why /usr/bin/*.dll must be executable?

On Apr 21 00:17, De-Jian Zhao wrote: > On 2012-4-20 21:07, Václav Zeman wrote: > >On 20 April 2012 15:02, De-Jian Zhao wrote: > >>Hi, > >> > >>When I type "cyg" and Tab, many executables starting with "cyg" are listed > >>(Display all 262 possibilities? (y or n) y). I find that many of them are > >

RE: Why /usr/bin/*.dll must be executable?

From: Corinna Vinschen > Windows requires the x bit for DLLs to be loadable as executable code > into the address space of a process. As Václav wrote, it's a Windows > thing. So, I had to play with "chmod -x cyg*.dll" and, of course, it totally hosed Cygwin. I recovered by reinstalling from scra

Change dark blue terminal colour

Hello all, I am a new Cygwin user. I have been looking online for a way to change the default ANSI BLUE to CYAN, as it is very difficult to see on the black terminal background. However, all I have been able to find were suggestions to use Putty's terminal or Console 2 instead of Cygwin's terminal.

Re: Why /usr/bin/*.dll must be executable?

On 4/20/2012 1:25 PM, Nellis, Kenneth wrote: From: Corinna Vinschen Windows requires the x bit for DLLs to be loadable as executable code into the address space of a process. As Václav wrote, it's a Windows thing. So, I had to play with "chmod -x cyg*.dll" and, of course, it totally hosed Cyg

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I fin

Re: Change dark blue terminal colour

On 4/20/2012 1:26 PM, Dotan Cohen wrote: Hello all, I am a new Cygwin user. I have been looking online for a way to change the default ANSI BLUE to CYAN, as it is very difficult to see on the black terminal background. However, all I have been able to find were suggestions to use Putty's terminal

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-21 1:29, Larry Hall (Cygwin) wrote: On 4/20/2012 1:25 PM, Nellis, Kenneth wrote: From: Corinna Vinschen Windows requires the x bit for DLLs to be loadable as executable code into the address space of a process. As Václav wrote, it's a Windows thing. So, I had to play with "chmod -x

RE: Why /usr/bin/*.dll must be executable?

From: Larry Hall (Cygwin) > What's wrong with "chmod +x cyg*.dll"? As I said, Cygwin was hosed, so I couldn't enter that command. --Ken Nellis

Re: Why /usr/bin/*.dll must be executable?

On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many executables starting with "cyg" are listed (Displa

Re: cygwin 1.7.13-1: can't execute shell scripts on samba share

-Len On Apr 19, 2012, at 4:29 AM, Michel Bardiaux wrote: > 2 suggestions: > > 1. What happens if len.sh is in your Cygwin home, that is on the local > drive? lgiambro@lorien ~ $ ./len.sh it works > > 2. What happens with "sh -x ./len.sh" (on the network drive)? > lgiambro@lorien //kits

Two probable basing issues causing fork failures: (1) cygreadline7.dll has ASLR enabled, (2) default base address conflicts with ASLR-relocated/system DLLs

Hi, Before I describe the issues I think I've found, I'd like to clarify my understanding. In the past, I have periodically run into random issues when starting new programs from the bash shell. The errors are always random and cryptic ("bad address", etc. - that sort of thing). Today this issu

Re: cygwin 1.7.13-1: can't execute shell scripts on samba share

-Len On Apr 19, 2012, at 7:37 AM, Earnie Boyd wrote: > On Wed, Apr 18, 2012 at 3:44 PM, Len Giambrone > wrote: >> No. That works. presumably because it's executing "bash" and not >> the script itself. > > http://cygwin.com/acronyms/#TOFU > > And does the script contain #! /bin/sh or the

Re: Why /usr/bin/*.dll must be executable?

On 4/20/2012 1:37 PM, De-Jian Zhao wrote: On 2012-4-21 1:29, Larry Hall (Cygwin) wrote: On 4/20/2012 1:25 PM, Nellis, Kenneth wrote: From: Corinna Vinschen Windows requires the x bit for DLLs to be loadable as executable code into the address space of a process. As Václav wrote, it's a Windows

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote: Hi, When I type "cyg" and Tab, many exe

Re: Why /usr/bin/*.dll must be executable?

On 4/20/2012 1:47 PM, De-Jian Zhao wrote: On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wrote: On 20 April 2012 15:02, De-Jian Zhao wrote

Re: Why /usr/bin/*.dll must be executable?

On 4/20/2012 1:47 PM, De-Jian Zhao wrote: Oh and... At least, *.exe does not respect or even is blind to the -x operation of Cygwin, as abovementioned. Cygwin creates its Windows ACLs to support POSIX permisssions. See the Cygwin Users Guide for more:

Re: Change dark blue terminal colour

On Fri, Apr 20, 2012 at 13:34, Larry Hall wrote: > If you're using mintty, edit ~/.minttyrc or change directly through the > "Options" dialog in the System menu.  If you're using cmd.exe (you should > update), change the colors through the "Properties" and "Default" dialogs > in the System menu. >

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-21 1:57, Larry Hall (Cygwin) wrote: On 4/20/2012 1:47 PM, De-Jian Zhao wrote: On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao wrote: On 2012-4-20 21:07, Václav Zeman wro

Re: Why /usr/bin/*.dll must be executable?

On 4/20/2012 2:21 PM, De-Jian Zhao wrote: On 2012-4-21 1:57, Larry Hall (Cygwin) wrote: On 4/20/2012 1:47 PM, De-Jian Zhao wrote: On 2012-4-21 1:40, Larry Hall (Cygwin) wrote: On 4/20/2012 1:32 PM, De-Jian Zhao wrote: On 2012-4-21 0:27, Corinna Vinschen wrote: On Apr 21 00:17, De-Jian Zhao w

Re: Why /usr/bin/*.dll must be executable?

On 20/04/2012 14:02, De-Jian Zhao wrote: > When I type "cyg" and Tab, many executables starting with "cyg" are listed > (Display all 262 possibilities? (y or n) y). I find that many of them are > *.dll libraries under /usr/bin/. This is inconvenient to find the real > executable applications (*.exe

Re: Change dark blue terminal colour

On 20 April 2012 18:26, Dotan Cohen wrote: > Hello all, I am a new Cygwin user. I have been looking online for a > way to change the default ANSI BLUE to CYAN, as it is very difficult > to see on the black terminal background. However, all I have been able > to find were suggestions to use Putty's

Re: Two probable basing issues causing fork failures: (1) cygreadline7.dll has ASLR enabled, (2) default base address conflicts with ASLR-relocated/system DLLs

On Fri, Apr 20, 2012 at 05:44:38PM -, James Johnston wrote: >[snip] >... Today this issue came >to a head on one installation of Cygwin 1.7.9,... >[snip] >Thoughts, anyone? Yep. Update your Cygwin installation. You're four revisions out of date. It should come not too great a surprise that

Re: Why /usr/bin/*.dll must be executable?

On 4/21/2012 5:21 AM, De-Jian Zhao wrote: ... Then, what limitations does the Windows loader have? As far as I know, there is no x bits for windows, right? How does the "chmod a-x" affect the file behavior under Windows if this is a Windows thing? I am completely confused. When I ran "chmod a-x

Re: Change dark blue terminal colour

On 4/20/2012 11:05 AM, Dotan Cohen wrote: On Fri, Apr 20, 2012 at 13:34, Larry Hall wrote: If you're using mintty, edit ~/.minttyrc or change directly through the "Options" dialog in the System menu. If you're using cmd.exe (you should update), change the colors through the "Properties" and "De

Re: Why /usr/bin/*.dll must be executable?

On 2012-4-21 3:06, Jon TURNEY wrote: On 20/04/2012 14:02, De-Jian Zhao wrote: When I type "cyg" and Tab, many executables starting with "cyg" are listed (Display all 262 possibilities? (y or n) y). I find that many of them are *.dll libraries under /usr/bin/. This is inconvenient to find the rea