X-Spam-Check-By:	sourceware.org
Message-ID:	<001501c694db$15871200$0a3b6080@joehome>
From:	"Science Guy" <sciguy AT comcast DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: bash and CSRSS consuming 100% of CPU
Date:	Tue, 20 Jun 2006 22:33:29 -0400
MIME-Version:	1.0
X-Mailer:	Microsoft Outlook Express 6.00.2800.1807
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

From message http://cygwin.com/ml/cygwin/2006-06/msg00534.html:

> Dave, I think you missed this:
>
>>sciguy wrote:
>>>I am networked to a Linux machine, so I moved the tar file
>>>cygwin-inst-20060614.tar.bz2 over to the Linux machine, created a dummy
>>>cygwin directory to hold the file, and un-tarred it there using this
>>>command:
>>>
>>>% /bin/tar -jxvf cygwin-inst-20060614.tar.bz2
>>>
>>>Then I ftp'd the entire un-tarred file and directory structure over the
>>>cygwin directory of the affected Windows PC.
>
>This is why I kept mentioning that the snapshot cygwin DLL wasn't
>installed in the right location.  I correctly assumed that this step did
>not put the cygwin DLL (or any of the cygwin programs) in c:\cygwin\bin.
>The cygcheck output made this pretty clear.
>
>cgf

Yes, when I untarred the file with "/bin/tar -jxvf
cygwin-inst-20060614.tar.bz2," I found it contained only these two top-level
directories:  /etc and /usr.  It did not contain a /bin directory.

--Joe


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

- Raw text -