X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.7 required=5.0 tests=AWL,BAYES_50,SPF_PASS
X-Spam-Check-By:	sourceware.org
Received-SPF:	pass (mail3.jubileegroup.co.uk: domain of ged AT jubileegroup DOT co DOT uk designates 127.0.0.1 as permitted sender) receiver=mail3.jubileegroup.co.uk; client-ip=127.0.0.1; helo=mail3.jubileegroup.co.uk; envelope-from=ged AT jubileegroup DOT co DOT uk; x-software=spfmilter 0.98-gwh with libspf2-1.2.9;
Date:	Fri, 5 Feb 2010 11:58:11 +0000 (GMT)
From:	"G.W. Haywood" <ged AT jubileegroup DOT co DOT uk>
To:	"Cygwin mailing list." <cygwin AT cygwin DOT com>
Subject:	Re: what's the problem of my cygwin installation?
In-Reply-To:	<1265318819.7472.ezmlm@cygwin.com>
Message-ID:	<Pine.LNX.4.58.1002051050560.28071@mail3.jubileegroup.co.uk>
References:	<1265318819 DOT 7472 DOT ezmlm AT cygwin DOT com>
MIME-Version:	1.0
X-Originating-Country:	localhost
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

Hi there,

On Thu, 4 Feb 2010 Larry Hall wrote:

> Make sure you use the 'setup.exe' from cygwin.com.
>  The current version is 2.680.

It's long seemed to me that there's a case for changing the name of this
file.  On the average Windows box it is not unusual to see several files
called 'setup.exe' descended from entirely unrelated products.  I've just
found 33 of them on a customer's server, the oldest is dated August 1992.
At least one useful ACRONYM was suggested here:

http://www.cygwin.com/ml/cygwin/2005-08/msg00283.html

although they all seem to have fallen on stony ground.

> Remove any previous versions of Cygwin or stray cygwin1.dlls you may
> have hanging around.

Similar - perhaps something like they do for the C libraries:

portakabin2:~$ >>> ls -lar --sort=time /lib/libc-* /lib/libc.so*
-rwxr-xr-x 1 root root 1528742 2007-06-19 21:57 /lib/libc-2.5.so*
-rwxr-xr-x 1 root root 1575187 2008-04-20 07:17 /lib/libc-2.7.so*
-rwxr-xr-x 1 root root 1658350 2009-04-03 11:00 /lib/libc-2.9.so*
-rwxr-xr-x 1 root root 1733115 2010-01-01 03:02 /lib/libc-2.11.1.so*
lrwxrwxrwx 1 root root      14 2010-01-06 15:55 /lib/libc.so.6 -> libc-2.11.1.so*

libc.so.6 -> libc-2.11.1.so	[Slackware current]
libc.so.6 -> libc-2.7.so	[Debian Lenny]
libc.so.6 -> libc-2.3.2.so	[old Red Hat thing laying around here]
...

I understand that there are issues with running more than one version
of the Cygwin DLL, and with NTFS junction points.  I'm just suggesting
that, with a very small amount of effort, things could easily be made
much clearer for everyone - and one possible result of that might be a
little less traffic on the Cygwin mailling list.

Comments?

--

73,
Ged.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -