From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Time is running out for 32-bit ARM
Date: Tue, 02 Aug 2022 10:08:42 +0000 [thread overview]
Message-ID: <540965b3-4417-8fb1-7802-a36f5fc63b93@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hello *,
in January [1], we already discussed the situation of 32-bit ARM, and settled on
demoting this architecture as "legacy" on [2], and advising people from buying new
32-bit ARM hardware in the wiki.
To some extends, this architecture shares a similar fate than 32-bit Intel did:
Security features are not backported to it, maintenance requires a lot of effort
due to missing upstream support, hardware base is diminishing, and its IPFire
userbase does not justify the resources required for keeping the distribution
reasonably maintained on this architecture.
The other night, we have therefore agreed on putting an end to IPFire support for
32-bit ARM, and take the question of the anticipated timeframe to this mailing list.
[3]
At the time of writing, Fireinfo reports 0.94% of all IPFire installations to run
on supported 32-bit ARM devices, to give you a figure. [4]
Personally, since these devices are unlikely to run in enterprises or other critical
environments, I would be fine with announcing EOL for 32-bit ARM at the end of
this year. However, as I am not running any affected IPFire installations, my
opinion is biased - let's hear yours. :-)
Thanks in advance for your reply, and best regards,
Peter Müller
[1] https://wiki.ipfire.org/devel/telco/2022-01-03
[2] https://www.ipfire.org/download
[3] https://wiki.ipfire.org/devel/telco/2022-08-01
[4] https://fireinfo.ipfire.org/
next reply other threads:[~2022-08-02 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 10:08 Peter Müller [this message]
2022-08-06 12:24 ` Michael Tremer
2022-08-06 12:40 ` Adolf Belka
2022-08-06 15:31 ` Michael Tremer
2022-08-14 16:29 ` Michael Tremer
2022-08-14 17:21 ` Peter Müller
2022-08-14 17:23 ` Michael Tremer
2022-08-14 16:30 ` 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=540965b3-4417-8fb1-7802-a36f5fc63b93@ipfire.org \
--to=peter.mueller@ipfire.org \
--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