From owner-freebsd-arm@freebsd.org Tue Dec 8 17:29:34 2015 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 3F0DD9D4018 for ; Tue, 8 Dec 2015 17:29:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0151D1AB8 for ; Tue, 8 Dec 2015 17:29:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by qgea14 with SMTP id a14so26744706qge.0 for ; Tue, 08 Dec 2015 09:29:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=s2FsGUtBrds41YepNvlfCZZd3plgnPxyPEu2lMgw6bg=; b=Xn1aQPs2gv/c269V3DQ7KclBuVeHrxSZWSxxJ0p/YYJn4gQXq16Mq4ALBTfwdDFgZ/ c0NB+I9Djz+pHVsIVJCS+InPzHppHptj38Vld2NwxQb7vnLzNP+SqhH4h2uHWrHchV// 5WeoGLs5bvNdv+7LqRkfXkw+hVlzccePDz1sDtNXk9ckXjniMy5rKc8F/wuqnSSDL5WU TW2t0D06vEDx4dkCa+rUHuG7eFJTbg2XYHIeR4VATTxPRdS/lP6Wo3DZZHE5bGN+L7Pr ZxQNAwHOCHLMYJrtylvEbpDcvpxTF/6KGxy9XiQjgYuV/uMO9uR1bj7y4ukPUGY/fM1n tEZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=s2FsGUtBrds41YepNvlfCZZd3plgnPxyPEu2lMgw6bg=; b=SIf7AXMFQX17POLNYVMq8bOsKuSmf4ioaT9LWqLFOSIWUKtYjMXVKb/MnoF0h5npbF 2ztuPJscRtvVr92ilaQy2WU7i2bTIAlnpQk0b/u4txtaEvnRfSEAi5/mfvt5oKVY2YnA gyBUZebeTX5/zNGYMHQ/JjG2pZzS4pMvXFgIgkCIMBuddK4J1ZVvGbhrv5S93t3ZYfvE 4ZVfnxYcXgNNSnom0LM/hB83vj23FapUC3ThptWYs+TWKgfyOTpxWquYVmnb15PxQvBM rqwy4jEOaMC/oGSOQY6dAuSN0xl1aVD4DQMmIy0LTC4CXO/gUdpBWU1M4vOB6aAsgcG+ 2AIg== X-Gm-Message-State: ALoCoQkiqGvtXe+JK5191Y6bLDg45F1+1yuEWtrw7V+GVZJwVQs7/p1WNSyLOH2edTrR8NZpLIYkK8kHhd1mvpxayKt61vhMsw== MIME-Version: 1.0 X-Received: by 10.140.176.143 with SMTP id w137mr6825193qhw.20.1449595772866; Tue, 08 Dec 2015 09:29:32 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.27.181 with HTTP; Tue, 8 Dec 2015 09:29:32 -0800 (PST) X-Originating-IP: [2601:280:4900:3700:4d3f:8eba:ea86:7700] In-Reply-To: <20151208170304.4386897.13959.1326@gmail.com> References: <5666F37C.4060908@denninger.net> <20151208170304.4386897.13959.1326@gmail.com> Date: Tue, 8 Dec 2015 10:29:32 -0700 X-Google-Sender-Auth: _zL-PcLkGAdEcRVtg3XFmDA5-Xs Message-ID: Subject: Re: Updating / keeping current strategies? From: Warner Losh To: Russell Haley Cc: Karl Denninger , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2015 17:29:34 -0000 On Tue, Dec 8, 2015 at 10:03 AM, Russell Haley wrote: > We do a ping pong at work for our embedded linux upgrades. It ensures that > we can fall back to the original install if the update fails. However, we > use a sata drive. Do you gave an documentation for this? > It's a work in progress, but https://www.freebsd.org/doc/en/articles/nanobsd/article.html has the basics. Warner > Thanks > > Russ > > Sent from my BlackBerry 10 smartphone on the Koodo network. > Original Message > From: Warner Losh > Sent: Tuesday, December 8, 2015 7:55 AM > To: Karl Denninger > Cc: freebsd-arm@freebsd.org > Subject: Re: Updating / keeping current strategies? > > On Tue, Dec 8, 2015 at 8:13 AM, Karl Denninger 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? > > > > I've been updating for years. But usually building on another machine and > then > installing to the media of the embedded machine via NFS. This mostly works > and isn't too sucky. But there are problems with this approach, since high > write work loads tend to bog down the embedded box due to crappy storage > being used (eg SD cards, USB attachment or both). > > You may have noticed some commits to nanobsd I've been making lately. > I'm moving all my local boards over to nanobsd with a ping-pong partition. > I'd create a new image for a new partition, splat it on to the 'pong' > partition, > adjust the active flags and reboot. NanoBSD has supported this operation > for a while, and this works well in the hand-built images I've done. > > I'm polishing off the rough edges for this by making it possible to > dynamically > resize the first time. FreeBSD supports this for one partition today. But > it > doesn't provide a good way to do a divide by 2. The support in FreeBSD > for writing MSDOS partitions as a regular user is also weak, so there's > bits from mtools in my build. I've also not completely integrated the > u-boot > ports into the build. There's also an open question about the proper way > to install packages on these boxes. One school of thought says that nanobsd > should put the packages you want onto the image, and that's all you'll > ever get. Another says that nanobsd should keep the database of packages > off the ping or pong partitions so that when you upgrade, the packages > are refreshed to the old set. There's other in-between positions I've heard > articulated. > > So I can't help you today, but I'll be able to help you soon. > > Warner > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >