Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
From:	Matt <matt AT use DOT net>
X-Sender:	matt AT cesium DOT clock DOT org
To:	cygwin-developers AT sources DOT redhat DOT com
Subject:	cygcheck floppy checking
Message-ID:	<Pine.NEB.4.10.10012031636500.25290-100000@cesium.clock.org>
MIME-Version:	1.0
Date:	Sun, 3 Dec 2000 16:41:42 -0800

I've noticed that cygcheck was taking an extraordinary amount of time to
execute on my laptop. This appears to be because my external floppy drive
is not hooked up, which begs the question:

Should cygcheck bother checking the floppy drives (a: and b:)? Or, should
a switch be added to eliminate floppy drive checking?

Whatever the consensus is is what I'll (try to) implement.


--
it's better to burn out
than to fade away

- Raw text -