From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipfire on Arm
Date: Mon, 23 Mar 2015 16:46:15 +0100 [thread overview]
Message-ID: <1427125575.14172.138.camel@ipfire.org> (raw)
In-Reply-To: <551031F0.2020309@redcor.ch>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
That means that it is not supported right now and that we do not plan to
support it in the future.
The Raspberry Pi Boards are just garbage. They are slow. Their
peripheral devices are unnecessarily unstable because of a poor board
design. So there is no way this could ever be properly used as a
firewall.
-Michael
On Mon, 2015-03-23 at 16:32 +0100, robert rottermann wrote:
> Hi there
> On 22.03.2015 22:11, Michael Tremer wrote:
> > Hey Bill,
> >
> > this hardware is actually supported at the moment:
> >
> > http://wiki.ipfire.org/en/hardware/arm/start
> >
> >
> how comes, that on that list raspberry 2 is "black"(listed) ..
>
> robert
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-23 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 18:02 William Pechter
2015-03-22 21:11 ` Michael Tremer
2015-03-23 15:32 ` robert rottermann
2015-03-23 15:46 ` Michael Tremer [this message]
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=1427125575.14172.138.camel@ipfire.org \
--to=michael.tremer@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