delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
From: | "Dave Korn" <dave DOT korn AT artimi DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | RE: New installation does not connect stdout to terminal |
Date: | Wed, 11 Jan 2006 16:59:47 -0000 |
MIME-Version: | 1.0 |
In-Reply-To: | <43C53448.3090004@russellonthenet.com> |
Message-ID: | <SERRANOIVvLVKi3s1ws00000076@SERRANO.CAM.ARTIMI.COM> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Russell K Montgomery wrote: > I have installed cygwin on a new Windows XP box and when I run Cygwin I > do not get output from commands on the terminal. The only way I can get > the output is to redirect stdout to stderr "ls -l 1>&2" That's the wackiest bug I've heard of in a while! Does the same happen in a rxvt window and in a DOS box, or is it only one or the other? > I have used Cygwin for several years on Windows 98 and for the past year > on another Windows XP box but have not seen any behavior like this. I > have searched the archives and not found any reports that are similar to > this behavior. Have I overlooked something? No, this is utterly unique and bizarre, and it's very hard to imagine how it could even begin to happen. Maybe someone's gone and created a real file called /dev/console and it's messing with i/o because it's not a special device node? > I'm attaching the results of "cygcheck -s -v -r > chgcheck.out" Well, I'd get rid of the set of clashing unix-alike tools that you have installed under C:\bin, for a start, or at any rate remove them from the $PATH setting, and then give setup.exe a quick re-run to give it a chance to re-do anything that might have gone wrong last time. Otherwise this is going to be definitely a tricky one to track down. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |