Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jan 2017 11:35:32 +0000
From:      tech-lists <tech-lists@zyxst.net>
To:        freebsd-arm@freebsd.org
Subject:   Re: Durable/serious arm hardware ?
Message-ID:  <185dbbb3-15eb-b63a-799f-d209858257b9@zyxst.net>
In-Reply-To: <45d41ec7-3004-ea6c-560e-50bdff9b997a@caliopea.com>
References:  <45d41ec7-3004-ea6c-560e-50bdff9b997a@caliopea.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 22/01/2017 10:19, nowhere wrote:
> 1 raspberry-pi , which was affected by the "micron-ram-chip" bug: except
> with debian, it never booted on freebsd (I even tried netbsd): I just
> trashed it yesterday (bought in 2014 i think).

I have 5 rpi boards:

1x rpi2+
3x rpi2B
1x rpi3

The rpis I treat (mainly) as single-purpose devices and for that they
are (in my experience) very stable. The exception being the rpi3 which
will be a (hardened) freebsd server for the internal network. Most of
these pis are on 24/7. The pi3 is better suited than the pi2x for a
server role. It would be worthwhile attaching a usb hd to the pi3 for data.

Although I've worn out a few microsd cards, I think that's been caused
by my own ignorance in not allocating external media for a busy
filesystem. All the pi hardware still works though, and I've had the
pi2+ abd 2B since they came out.

I've had one of the pi2Bs as a (32-bit) mail server running exim which
failed because of my above mentioned ignorance. The pi3 runs hardenedBSD
entirely in 64bit and seems very stable unless I thrash the microsd by
installing ports and not exporting $WORKDIR to external (and easily
replacable) media, like a usb stick.

I haven't been able to get vanilla freebsd/aarch64 running on the rpi3 yet.
-- 
J.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?185dbbb3-15eb-b63a-799f-d209858257b9>