Updating / keeping current strategies?

[Russell Haley]

Not sure about RPi or bbb but for my imx53 digi som I had my userland on a USB stick and loaded the kernel using tftp from u-boot. That was good for development because I could have two USB sticks and did all my cross compiling on an amd64 box. Tftp is reasonably fast but setup is finiky.  Not so great for production though. 

Remember also Ian Lapore has documented a -DNO_CLEAN option for make.  It's on the wiki but I don't have the page handy. ‎ Not sure which targets it's applicable to.  Also there is an option for specifying parts of the base os to build. I don't Remeber whe name (srcconf?). I submitted a patch for the man pages but it's just sitting there in bugzilla. let me know if you want it and I'll dig my notes out. 

Russ

Sent from my BlackBerry 10 smartphone on the Koodo network.
  Original Message  
From: Karl Denninger
Sent: Tuesday, December 8, 2015 7:13 AM
To: freebsd-arm at freebsd.org
Subject: Updating / keeping current strategies?

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]/