X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3ADFA385842B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1682968060;
	bh=AFhsT8Mo9F0UtfPI9JS25NtZcYBw+4WVN3GtX8SPamw=;
	h=Date:To:cc:Subject:In-Reply-To:References:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=VbOdWw8Nj4Bp5ECw+OX78gioT8Ow3u76O4AQ9IulG9ssmwkluVYbeV/rqdQuBY0Zr
	 jC01O4+/MLWdVNeUaMqcgeL02+GtW9zYMi+gx7gP6Ze9tPOkw84zg2QASdN5yHr45b
	 whaVCODBy6cjY3Yv63ltYyUmn5bVYrZhWkzuQulU=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0DEEC3858D1E
Date: Mon, 1 May 2023 12:07:21 -0700 (PDT)
X-X-Sender: jeremyd AT resin DOT csoft DOT net
To: Brian Inglis <Brian DOT Inglis AT Shaw DOT ca>
cc: cygwin AT cygwin DOT com
Subject: Re: Installing/upgrading only NOARCH packages.
In-Reply-To: <fe3d7db7-d77f-ce98-da43-7b64404997b0@Shaw.ca>
Message-ID: <alpine.BSO.2.21.2305011157150.83057@resin.csoft.net>
References: <CADt9574Ob01qmHsb0W+eyzTtQ_Vp2MU7bqRGukC+Qci0FUkBbA AT mail DOT gmail DOT com>
 <fe3d7db7-d77f-ce98-da43-7b64404997b0 AT Shaw DOT ca>
User-Agent: Alpine 2.21 (BSO 202 2017-01-01)
MIME-Version: 1.0
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Jeremy Drake via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Jeremy Drake <cygwin AT jdrake DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Wed, 19 Apr 2023, Brian Inglis wrote:

> As 32 bit Windows systems are no longer getting security updates,
> recommendations for similar legacy systems include running them in VMs with
> access to update executables and libraries blocked.

There is a 32-bit variant of Windows 10; Windows 10 is scheduled to be
supported until October 2025.

Personally, I have a tablet, which shipped with Windows 8 and has a
64-bit-capable Atom processor, that nonetheless has a 32-bit UEFI firmware
without legacy boot support, and is thus incapable of booting a 64-bit
edition of Windows.  I have gotten the free upgrades to 8.1 (as soon as
I bought it) and then 10 when it came out.

I just wanted to correct the record that 32-bit Windows is already out of
support, or the general implication that they don't really matter anymore.
Maybe they don't, but maybe people don't realize that systems of 64-bit
processor vintage doesn't mean that a system can actually boot a 64-bit
Windows, even though it could otherwise run it (and can in a virtual
machine, though it's painful due to lack of RAM, and now lack of
VM software that still supports 32-bit Windows ;) ).

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