From: "Theodore Ts'o" <tytso@mit.edu>
To: John Gilmore <gnu@toad.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Macs and future unix derivatives
Date: Tue, 9 Feb 2021 14:02:34 -0500 [thread overview]
Message-ID: <YCLcSkeMUXnpDLuT@mit.edu> (raw)
In-Reply-To: <5372.1612853750@hop.toad.com>
On Mon, Feb 08, 2021 at 10:55:50PM -0800, John Gilmore wrote:
>
> That was true decades ago, but no longer. In the intervening time, all
> the major Linux distributions have stopped releasing OS's that support
> 32-bit machines. Even those that support 32-bit CPUs have often
> desupported the earlier CPUs (like, what was wrong with the 80386?).
> Essentially NO applications require 64-bit address spaces, so arguably
> if they wanted to lessen their workload, they should have desupported
> the 64-bit architectures (or made kernels and OS's that would run on
> both from a single release). But that wouldn't give them the
> gee-whiz-look-at-all-the-new-features feeling.
So there is currently a *single* volunteer supporting the 32-bit i386
platform for Debian, and in December 2020 there was an e-mail thread
asking whether there were volunteer resources to be able to provide
the necessary support (testing installers, building and testing
packages for security updates, etc.) for the 3.5 years of stable
support. I don't believe the final decision has been made, but if
more people were willing to volunteer to make it happen, or to pay $$$
to provide that support, I'm sure Debian would be very happy to keep
i386 on life support for the next stable release.
Ultimately, it's all about what people are willing to support by
providing direct volunteer support, or by putting the money where
their mouth is. "We have met the enemy, and he is us."
- Ted
next prev parent reply other threads:[~2021-02-09 19:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 18:11 Will Senn
2021-02-08 18:21 ` Larry McVoy
2021-02-08 18:32 ` Justin Coffey
2021-02-08 18:39 ` Larry McVoy
2021-02-09 1:59 ` Theodore Ts'o
2021-02-12 13:48 ` Angel M Alganza
2021-02-08 18:42 ` Henry Bent
2021-02-09 6:55 ` John Gilmore
2021-02-09 7:05 ` Michael Huff
2021-02-16 22:55 ` Greg A. Woods
2021-02-09 7:17 ` Will Senn
2021-02-09 19:02 ` Theodore Ts'o [this message]
2021-02-10 1:34 ` Larry McVoy
2021-02-09 22:59 ` Wesley Parish
2021-02-08 18:43 ` Dan Stromberg
2021-02-12 13:39 ` Angel M Alganza
2021-02-08 18:45 ` Thomas Paulsen
2021-02-25 22:45 ` Dave Horsfall
2021-02-08 20:07 ` Al Kossow
2021-02-09 5:10 ` Andrew Warkentin
2021-02-09 7:42 ` [TUHS] QNX John Gilmore
2021-02-09 11:03 ` Robert Brockway
2021-02-09 18:24 ` Nemo Nusquam
2021-02-09 20:18 ` Jose R Valverde via TUHS
2021-02-09 14:05 ` Larry McVoy
2021-02-09 3:58 [TUHS] Macs and future unix derivatives M Douglas McIlroy
2021-02-09 4:07 ` Adam Thornton
2021-02-09 4:13 ` Will Senn
2021-02-09 5:21 ` Andrew Warkentin
2021-02-09 5:29 ` Theodore Ts'o
2021-02-09 6:37 ` Andrew Warkentin
2021-02-09 16:13 ` Theodore Ts'o
2021-02-09 17:31 ` John Cowan
2021-02-09 19:06 ` Chet Ramey
2021-02-10 2:31 ` Andrew Warkentin
2021-02-09 19:00 ` Jon Steinhart
2021-02-10 1:41 ` Larry McVoy
2021-02-10 1:52 ` George Michaelson
2021-02-10 2:24 ` Larry McVoy
2021-02-10 2:44 ` Dan Cross
2021-02-10 3:10 ` Larry McVoy
2021-02-10 20:03 ` Kevin Bowling
2021-02-10 2:57 ` Warner Losh
2021-02-10 2:56 ` Warner Losh
2021-02-10 3:02 ` Larry McVoy
2021-02-10 3:53 ` Andrew Warkentin
2021-02-09 11:34 ` Thomas Paulsen
2021-02-09 18:29 ` Nemo Nusquam
2021-02-09 8:30 Bakul Shah
2021-02-09 12:22 M Douglas McIlroy
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=YCLcSkeMUXnpDLuT@mit.edu \
--to=tytso@mit.edu \
--cc=gnu@toad.com \
--cc=tuhs@minnie.tuhs.org \
/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 NNTP newsgroup(s).