X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Mon, 14 Jul 2008 19:50:24 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.7 constantly accesses floppy drive
Message-ID:	<20080714175024.GB24644@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<7CDD82AEE5144D60961BDAD9B1C1A40D AT cit DOT wayne DOT edu> <4877A0FE DOT 1070002 AT cygwin DOT com> <A2A391A08F90454589E846EE99CC2929 AT cit DOT wayne DOT edu> <4877B123 DOT 3080409 AT cygwin DOT com> <F5E0E265274541DCB3A4FD04665CBAB2 AT cit DOT wayne DOT edu> <4877D782 DOT 4000308 AT cygwin DOT com> <15E6E2FA521344A3B74D38BA78E2D7DF AT cit DOT wayne DOT edu> <487B89EA DOT 7060503 AT cygwin DOT com>
MIME-Version:	1.0
In-Reply-To:	<487B89EA.7060503@cygwin.com>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

On Jul 14 13:16, Larry Hall (Cygwin) wrote:
> Lee Maschmeyer wrote:
>>> OK, so perhaps your problem and the Windows path shown by 'cygcheck' are 
>>> two
>>> different issues.
>> My problem is _precisely_ the Windows path shown by cygcheck. Everything 
>> _except_ Cygwin (as shown by cygcheck) is correct as far as I can see.
>
> Actually, you showed me the path that 'bash' has and it contains no
> reference to the 'a' drive in any form.  Since you run from a shell,
> this is the path that's important.  It may be coincidence or it may
> be one externalization of the bug you're seeing but the Windows path
> shown by 'cygcheck' has no bearing on the path that the shell sees.
> Said another way, if 'cygcheck' has a bug that ends up showing you a
> faulty path here, that would have no effect on anything else Cygwin.
> So what we've covered so far doesn't provide a clear reason for the
> behavior you're seeing.
>
>>> I'm back to not being sure why you're seeing accesses on
>>> your floppy drive.  Maybe if you straced a simple operation, you might be
>>> able to tell us who, what, when, why, and/or how the floppy drive gets
>>> accessed.
>> Attached is the output of the command:
>> strace -o strace_ls.log ls 1.7-log.txt
>> I don't think it tells us anything we didn't know. Cygwin, down under the 
>> hood, thinks Windows is on a: but all its variables show that it's on c:, 
>> as do Windows variables.
>
> To me this suggests that there could be a problem with getwinenv() but
> I can't say more than that at the moment.

It's not in getwinenv afaics, but I don't know what the actual problem
is so far.  It has something to do with the existance of the /a, /c etc
mounts, though.  For now, removing the /a mount from /etc/fstab will help
to get back to speed.  I'll try to figure out the cause of this problem.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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