From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 62521 invoked by alias); 12 Feb 2016 21:58:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 62484 invoked by uid 89); 12 Feb 2016 21:58:18 -0000 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 Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 12 Feb 2016 21:58:17 +0000 Received: by mail-lb0-f182.google.com with SMTP id bc4so52603783lbc.2 for ; Fri, 12 Feb 2016 13:58:16 -0800 (PST) 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) Received: by 10.25.86.196 with HTTP; Fri, 12 Feb 2016 13:58:13 -0800 (PST) In-Reply-To: <4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com> References: <56BA9DB2.3080106@cygwin.com> <56BB6FD1.6000208@molconn.com> <56BB7220.5010101@cygwin.com> <56BCCE7D.6040605@gmail.com> <4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com> Date: Fri, 12 Feb 2016 21:58:00 -0000 Message-ID: Subject: Re: Last Version of Cygwin for XP From: Erik Soderquist To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00178.txt.bz2 On Fri, Feb 12, 2016 at 2:20 PM, Warren Young wrote: > I hope not. Extended support ended nearly two years ago. That=E2=80=99s= 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 ti= me 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 th= e only reason Cygwin hasn=E2=80=99t jettisoned XP support yet is that it=E2= =80=99s more work than ignoring that old code. I have the same impression. Perhaps Corinna can confirm that? > Eventually, Cygwin=E2=80=99s gonna have to scrape that barnacle off the h= ull. You should already have your Cygwin XP install trees packed up in ant= icipation 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