Date: Tue, 8 Dec 2015 20:35:01 +0100 From: Ulrich Grey <ulrich-grey@t-online.de> To: Karl Denninger <karl@denninger.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Updating / keeping current strategies? Message-ID: <20151208203501.519ce6dc889894f7a947f989@t-online.de> In-Reply-To: <5666F37C.4060908@denninger.net> References: <5666F37C.4060908@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I am building images natively on my cubox, using the sript: /usr/src/release/release.sh -c arm/<board>.conf I added some lines to arm/<board>.conf: ##CHROOTBUILD_SKIP="yes" CHROOTDIR="/path/to/chroot" ##SRC_UPDATE_SKIP="yes" ##PORTS_UPDATE_SKIP="yes" #SRCBRANCH="base/head@r285417" MAKE_CONF="/etc/local/make.conf" #SRC_CONF="/etc/local/src.conf ... ... To /etc/local/make.conf (host) I write: #KERNFAST=1 MALLOC_PRODUCTION=yes #NO_CLEAN=1 1) Install chroot environment 2) co ports and src into chroot 3) Run script release.sh -c arm/<board>.conf for the first board (about 14 hours) (host) 3a) Rename image 4) Uncomment NO_CLEAN=1 in /etc/local/make.conf (host) 5) Like 3) for second board (about 1 hour) ... The images are saved to <chrootdir>/R --------------------------------- On Tue, 8 Dec 2015 09:13:00 -0600 Karl Denninger <karl@denninger.net> wrote: > 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@denninger.net <mailto:karl@denninger.net> > /The Market Ticker/ > /[S/MIME encrypted email preferred]/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151208203501.519ce6dc889894f7a947f989>