Updating / keeping current strategies?

[Karl Denninger]

What are people doing in this regard with devices like the Raspberry Pi2?

Build times for a "make buildworld" are measured in (many) hours to a
day or more and require a USB-attached disk for temporary storage, as
the ramdisk for /tmp that is typically mounted blows up due to lack of
space and SD cards are slow enough on writes (especially small writes)
as to make the process virtually impossible.  But even with a
USB-attached disk the process is ridiculous in terms of consumed
walllclock time.

Further, "make installworld" sometimes fails inexplicably.

Kernel builds are a bit more reasonable, only requiring a couple of hours.

I'm wondering what the best option is to not only build current code on
a regular basis (since -CURRENT is a "work in progress") but also to
deploy and update existing devices.  What are people doing that has a
history of working well?

-- 
Karl Denninger
karl at denninger.net <mailto:karl at denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2996 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20151208/50608641/attachment.bin>