From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: On demoting i586 to "legacy" status
Date: Thu, 06 Aug 2020 17:55:38 +0300 [thread overview]
Message-ID: <20200806145538.GD13914@tarvainen.info> (raw)
In-Reply-To: <6007DE2A-8CFD-41F9-8373-84C88917EB35@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On Thu, Aug 06, 2020 at 03:26:34PM +0100, Michael Tremer (michael.tremer(a)ipfire.org) wrote:
> As stated before, kernel support for 32 bits is bad. None of the
> big commercial Linux distributions is releasing a 32 bit version any
> more. RHEL, Ubuntu, CentOS, Arch do not exist for i686 AFAIK.
CentOS actually still does:
https://wiki.centos.org/SpecialInterestGroup/AltArch/i386
And Debian and Slackware do (although Debian now requires i686,
but even I don't have any pre-PAE i586 things left).
Of course they're not commercial distributions, but reasonably big and
well-maintained nonetheless.
> Hence we have to fix all the bugs on our own which we simply can’t do.
In my experience Debian is pretty good at that.
> We knew that this has been coming for a while now. See here:
>
> https://blog.ipfire.org/post/32-bit-is-dead-long-live-32-bit
>
> We are trying our best here, but if usage of that architecture
> drops below 5% or so we can rather invest our time into something
> else that benefits more users.
I appreciate that. But if it's now at over 20%, it may take
surprisingly long before it falls belos 5%.
Anyway, I've already been planning to replace those ancient machines,
but I can't see getting it done this year in any event. So I just ask,
please don't rush it any more than you must.
--
Tapani
next prev parent reply other threads:[~2020-08-06 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 12:08 Michael Tremer
2020-08-05 12:24 ` Michael Tremer
2020-08-06 14:21 ` Tapani Tarvainen
2020-08-06 14:26 ` Michael Tremer
2020-08-06 14:55 ` Tapani Tarvainen [this message]
2020-08-06 15:50 ` Michael Tremer
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=20200806145538.GD13914@tarvainen.info \
--to=ipfire@tapanitarvainen.fi \
--cc=development@lists.ipfire.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