Message-ID: <20090530181925.4hkr5kpty0aogkgs@webmail.integrasphere.com>
Date: Sat, 30 May 2009 18:19:25 -0500
From: dsp435 AT integrasphere DOT com
To: cygwin AT cygwin DOT com
Subject: Cygwin postinstall scripts / bash [ ] syntax fails on Win 2003 x64 	/ Xen
MIME-Version: 1.0
Content-Type: text/plain; 	charset=ISO-8859-1; 	DelSp="Yes"; 	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Hello all,

First time writing to this list, forgive me if this is redundant but I=20=
=20
have spent many hours researching this issue and while it seems to be=20=20
at least a known issue, I can't find any evidence it has been addressed.

The best thing I can do is point you to this post, it is quite telling:
http://markmail.org/message/owy3x7pf6oywdx5e#query:+page:1+mid:owy3x7pf6oyw=
dx5e+state:results

I am not using "KVM", but I am using Windows 2003 x64 on Xen, and I am=20=
=20
having the same issue. Cygwin fails to run the postinstall scripts,=20=20
and this leaves the environment all but unusable. It comes down to the=20=
=20
fact that bash cannot execute the "test" or "[ x ]" syntax without=20=20
throwing a segmentation fault. Running [ 1 ] at the bash prompt=20=20
immediately reproduces the bug. The bash prompt can be loaded, but non=20=
=20
of the startup scripts are executed and I just get a bash-3.2$ prompt=20=20
in /usr/bin.

The people who posted at the above link wrote a patch that supposedly=20=20
solved the problem, but there is no way for a normal user to try this=20=20
without a compiler and it doesn't appear to be in the release Cygwin=20=20
code yet. I also tried the Cygwin 1.7 beta and have the same problem.

I am an experienced Cygwin user of many years and dozens of solid=20=20
installs. I often setup the sshd server for remote access to remote=20=20
servers running Windows. This is the first time I have had these kinds=20=
=20
of problems.

Any help would be appreciated, such as news about the status of this=20=20
bug, how I can find more information about the issue, or if a fix is=20=20
planned for a future release. This bug also appears as if it could be=20=20
viewed as a Xen bug, but I'd like to understand what your position on=20=20
that actually is.

Thank you,
Dan


--
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/