public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: IT Superhack <itsuperhack@web.de>
To: development@lists.ipfire.org
Subject: Question concerning the IDS2016 log
Date: Thu, 08 Sep 2016 16:30:00 +0000	[thread overview]
Message-ID: <b1bd68ef-0e47-33fa-08ca-c334be8d2085@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

Hello Michael,
hello development-list,

I have a question concerning the IDS2016 (URL: http://wiki.ipfire.org/ids/2016/log),
where it says: "Dropping i686 + armv5tel - No need for it any more"

To me, it has not become fully clear if this means the architecture or the whole
release format. For example, nearly nobody (Fireinfo says: 0,07%) is running
an IPFire system with the armv5tel architecture - these are afaik mostly old
systems like the Raspberry Pi which are certainly not suitable for a firewall
purpose.

On the other hand, > 80% run an i686 system, and I guess it wouldn't make
sense to make these installations unusable because of EOL. But maybe "dropping"
means that you will remove some specific patches for i686, so these will
run with i586 afterwards.

Within the ARM stuff, the situation is not that clear for me. Are you panning
to remove the ARM support at all? Or are you going to remove ARMv5 devices from
the "supported ARM devices list"?

Sorry if there is a misunderstanding here - got way little coffe today. ;-)

Best regards,
Timmothy Wilson


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

             reply	other threads:[~2016-09-08 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 16:30 IT Superhack [this message]
2016-09-08 17:35 ` Michael Tremer
2016-09-10  3:54   ` R. W. Rodolico
2016-09-12 20:53     ` Michael Tremer
2016-09-13  0:24       ` R. W. Rodolico
2016-09-13 12:53         ` Michael Tremer
2016-09-11  9:48   ` IT Superhack
2016-09-12 21:04     ` 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=b1bd68ef-0e47-33fa-08ca-c334be8d2085@web.de \
    --to=itsuperhack@web.de \
    --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