From owner-freebsd-arm@freebsd.org Sun Jan 22 15:35:40 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6FAFCBCF62 for ; Sun, 22 Jan 2017 15:35:40 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9238A909 for ; Sun, 22 Jan 2017 15:35:40 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cVKB1-0001dc-2G for freebsd-arm@freebsd.org; Sun, 22 Jan 2017 16:35:31 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Subject: Re: Durable/serious arm hardware ? References: <45d41ec7-3004-ea6c-560e-50bdff9b997a@caliopea.com> <185dbbb3-15eb-b63a-799f-d209858257b9@zyxst.net> Date: Sun, 22 Jan 2017 16:35:29 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <185dbbb3-15eb-b63a-799f-d209858257b9@zyxst.net> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 4b95630a2805109a2fafe329e7ec4fd6 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2017 15:35:40 -0000 On Sun, 22 Jan 2017 12:35:32 +0100, tech-lists wrote: > 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. My solution to this is a tmpfs mounted dir. from /etc/fstab: tmpfs /tmp tmpfs rw,size=64M 0 0 tmpfs /var/tmp/ports-build tmpfs rw,size=512m 0 0 from /etc/make.conf WRKDIRPREFIX?=/var/tmp/ports-build Most ports build within a couple of MBs, so there isn't anything written to disk during the build stage. Chances are high on my system something else which is unused is swapped out when needed (which is on an USB-stick). Ronald. > > I haven't been able to get vanilla freebsd/aarch64 running on the rpi3 > yet.