public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Erik Soderquist <ErikSoderquist@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Last Version of Cygwin for XP
Date: Fri, 12 Feb 2016 21:58:00 -0000	[thread overview]
Message-ID: <CACoZoo1J1sOA+X30rbKXsCWgV-2gwqibNyr+_KZcuOOngvEnAA@mail.gmail.com> (raw)
In-Reply-To: <4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com>

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

  reply	other threads:[~2016-02-12 21:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  1:37 Jonathan Brenster
2016-02-10  2:17 ` Yaakov Selkowitz
2016-02-10 17:14   ` LMH
2016-02-10 17:24     ` Yaakov Selkowitz
2016-02-11 18:09       ` cyg Simple
2016-02-12 19:20         ` Warren Young
2016-02-12 21:58           ` Erik Soderquist [this message]
2016-02-12 22:42             ` Warren Young
2016-02-13  0:37               ` Erik Soderquist
2016-02-13 17:41                 ` Tony Kelman
2016-02-14  0:41                   ` Erik Soderquist
2016-02-15 14:53                     ` Eric Blake
2016-02-13 17:20             ` Corinna Vinschen
2016-02-10  2:20 ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACoZoo1J1sOA+X30rbKXsCWgV-2gwqibNyr+_KZcuOOngvEnAA@mail.gmail.com \
    --to=eriksoderquist@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).