On Sat, May 30, 2009 at 06:19:25PM -0500, dsp...@integrasphere.com wrote: >First time writing to this list, forgive me if this is redundant but I >have spent many hours researching this issue and while it seems to be >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:owy3x7pf6oywdx5e+state:results > >I am not using "KVM", but I am using Windows 2003 x64 on Xen, and I am >having the same issue. Cygwin fails to run the postinstall scripts, >and this leaves the environment all but unusable. It comes down to the >fact that bash cannot execute the "test" or "[ x ]" syntax without >throwing a segmentation fault. Running [ 1 ] at the bash prompt >immediately reproduces the bug. The bash prompt can be loaded, but non >of the startup scripts are executed and I just get a bash-3.2$ prompt >in /usr/bin. > >The people who posted at the above link wrote a patch that supposedly >solved the problem, but there is no way for a normal user to try this >without a compiler and it doesn't appear to be in the release Cygwin >code yet. I also tried the Cygwin 1.7 beta and have the same problem.
I didn't see any Cygwin patch there. AFAICT, someone changed kvm. If there is a Cygwin patch you'll need to be more explicit. cgf -- 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/
