X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=e8sU5kuev9i6jCzJ
	VtrOhTbjz0pA0GmZ5655fg7MDSQlAfAI9ouUFzhROw9KUhC6o8doXAE4fiVsvUwm
	j5/BD8swXtlXA/cBWRHbH2aiFRckdt3RpdFghtWguVAvsqwOAiZhPRCiL2S/D/KB
	r2/APCG7MqVz3iXhtRgRR2YLtsU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; s=default; bh=9PkftEkLMMGz0cXgrxmqX4
	6ytK4=; b=u9eXjcgVeAF6qms8E6PKeSvYKPsuifXThBqGfzpoKgM9CUWVAtybV6
	IvPJYgqu4+7hR+e0HZDKHMeNEuBcoU2Tkk8hOgz9gaMSjJ9p/fFISGZI2t5DF1wU
	Oz42q6hiGcuHldI4YQsl9q2keWu5isQOn5NwtvQ33ysr8ebapmqm0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=anticipation, footprint, 1.5, hasn
X-HELO: mail-lb0-f182.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:sender:in-reply-to:references:date         :message-id:subject:from:to:content-type:content-transfer-encoding;        bh=yoSiYG3jdHVXnMNXUSkx+yjurNrzpt9cp7Ar+OKPvjs=;        b=EshEayfBoqs53Bkt0CmmOsz1ZyueQnq+H4AyPqjAR72AqhPgN6yMcX2YHiisDKMNkl         f/AY3vMECGdboG2V29pfZFC6sF8UItd+OfvYDEDHmZ2K3BLDdlRZwD04744LSJzuP2+1         g+jtkLO5f+GbApwzTViOwzwyS+CE4CclmyJgDYuFiy9j6B2JpFR1hMHuNvnEZh9BQb7V         zMltkQ3anFlg1XY+TKGv0Eq/+XInFP7OwGU5jg83G79v0cpcXA+UP2FXcGPaXLVRmnak         wvuRQy38Im9SbilEiHHM27RMLcKEmfpZOJznNbzvLiqrGi5p0iO7jYhx0zcVYkpefZ1P         rwkg==
X-Gm-Message-State: AG10YOQPuG468P4So5m65rL6UWXm2ThrXRlVTpVyPYSSbzyMcXFwCr+ptDV2cM/LMGzw7VbgEFlXm7VPIjIumA==
MIME-Version: 1.0
X-Received: by 10.112.160.199 with SMTP id xm7mr1417207lbb.32.1455314294014; Fri, 12 Feb 2016 13:58:14 -0800 (PST)
In-Reply-To: <4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com>
References: <CA+0JN2rG-bH3cWeEVfek5Y3xRVY_BB+Jpxspch95YOKJ+tyUdg AT mail DOT gmail DOT com>	<56BA9DB2 DOT 3080106 AT cygwin DOT com>	<56BB6FD1 DOT 6000208 AT molconn DOT com>	<56BB7220 DOT 5010101 AT cygwin DOT com>	<56BCCE7D DOT 6040605 AT gmail DOT com>	<4D4ECA09-53B3-4A16-89BC-E9C7054A22C7 AT etr-usa DOT com>
Date: Fri, 12 Feb 2016 16:58:13 -0500
Message-ID: <CACoZoo1J1sOA+X30rbKXsCWgV-2gwqibNyr+_KZcuOOngvEnAA@mail.gmail.com>
Subject: Re: Last Version of Cygwin for XP
From: Erik Soderquist <ErikSoderquist AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u1CLwVXD009664

On Fri, Feb 12, 2016 at 2:20 PM, Warren Young wrote:
<snip>
> I hope not.  Extended support ended nearly two years ago.  That’s 22 months of unfixed security problems, bugs, and regressions with respect to the state of the world.  (By the latter, I mean things like outdated time zone rules.)

When your use case doesn't require fixes to these issues, why waste
the resources on newer (and more bloated) packages?  My use case has
XP + Cygwin in multiple VMs that do not even have NICs to begin with,
and do repeat processing on data sets using Windows-only software.
These VMs have a memory footprint of less than 300 MB each, and a disk
footprint under 10 GB, including 3 different snapshots (effectively 3
separate variants of the machine).  The smallest I was able to make
this using Windows 7 was 1.5 GB memory/50 GB disk footprint each, it
benchmarked 30% slower, and offered zero functional benefit.

While mine is very certainly a corner case, such corner cases do
exist, and I get very tired of people consistently implying (or
outright saying) that not upgrading XP is some form of stupidity or
insanity.  Would I trust one of these hosts on the internet at all?
No; that is the key reason they do not even have NICs in the VM
configuration.  All file transfer is done via the virtual
environment's folder sharing mechanism, and the VM host is a Linux box
that has a cron job checking for updates nightly.

So far my only concession to the lack of updates has been to configure
the timezone as UTC/no daylight saving time, and that has worked well.

> The last time this topic came up, I came away with the impression that the only reason Cygwin hasn’t jettisoned XP support yet is that it’s more work than ignoring that old code.

I have the same impression.  Perhaps Corinna can confirm that?

> Eventually, Cygwin’s gonna have to scrape that barnacle off the hull.  You should already have your Cygwin XP install trees packed up in anticipation of that day.

I agree, and for my purposes, the Cygwin I use for these special
purpose hosts is already frozen and archived.


-- Erik

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