On Sat, Apr 18, 2020, 8:42 AM wrote:
> Send Cygwin mailing list submissions to
> cygwin@cygwin.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://cygwin.com/mailman/listinfo/cygwin
> or, via email, send a message with subject or body 'help' to
> cyg
ccess to the machines and am unable to install Windows directly (not
under Xen).
That's it.
-Original Message-
From: Stephen Quintero
Sent: Friday, August 08, 2008 11:02 AM
To: cygwin@cygwin.com
Subject: RE: bash builtin "test" kills bash on Win 2003 Server R2 x64 (
Thank you for your replies. Some notes:
"[ -d /bin ]" causes the bash shell to terminate
"/bin/[ -d /bin ]" does not
"/bin/strace.exe [ -d /bin ]" does not cause the shell to terminate, spits out
a lot of info, and exits 0x0.
If you refer to the original post by Brian Johnson
(http://sourcew
using the same VM (an exact block level copy), cygwin
works on one set of hardware and not on another.
It truly does appear to be a hardware dependent problem with bash.
Stephen
-Original Message-
From: Stephen Quintero
Sent: Wednesday, August 06, 2008 9:08 AM
To: 'cygwin@
This subject has been raised before in this thread:
http://sourceware.org/ml/cygwin/2008-01/msg00579.html
but I cannot find any resolution of the problem.
In my case, I built a Win 2003 Server R2 x64 SP2 virtual machine under xen on
one physical machine and cygwin worked fine. Copying the VM t
Using cmd.exe as the login shell, ctrl-c terminates the ssh session (rather
than being propagated to the process on the remote server).
I have read that the shell is not a Windows console but rather a Cygwin pseudo
tty session. Hence there is no Windows console signal handling to take care of
6 matches
Mail list logo
