From owner-freebsd-arm@freebsd.org Mon Dec 14 07:36:05 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 7D0DDA43485 for ; Mon, 14 Dec 2015 07:36:05 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (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 3C2DE1F82 for ; Mon, 14 Dec 2015 07:36:05 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by vkgj66 with SMTP id j66so52211941vkg.1 for ; Sun, 13 Dec 2015 23:36:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BIi0O/6CtU0U2urr4y735EsRmS9eH6Wal+Xd59+IHOI=; b=X6k1aj0wDOztN2rVIHthg1nR83W5xGb+Gp0kn8rhoWNKtNi8OqN17RwBLelVNamd0I yiVdKwMAJOzjiYZXWPIOcXXrhQBugFswyygqXxn6bE3aosOE9vCCgGl6ky86u3YuTefU HD0HFS/nfIY5cBJ4vbKJda4BrwID7zLbGuBnBEoz4SIFylmiI5bIIGaVIuInpVOOajDR i331iIDPOUX/RMvDbD1I+uCECnG5iwzT61Yl75k32xo9djp1I3WHMr3zqiqGhneOn4uJ TatfbbspXXSFwMKNdbSs/SnSfN2NMxYdaRZee0suOXjqaMZFs16eb+zEdxgvmxqY4M7a nQ2Q== MIME-Version: 1.0 X-Received: by 10.31.5.132 with SMTP id 126mr24285742vkf.107.1450078564258; Sun, 13 Dec 2015 23:36:04 -0800 (PST) Received: by 10.31.47.137 with HTTP; Sun, 13 Dec 2015 23:36:04 -0800 (PST) In-Reply-To: References: <5666F37C.4060908@denninger.net> <20151208170304.4386897.13959.1326@gmail.com> Date: Sun, 13 Dec 2015 23:36:04 -0800 Message-ID: Subject: Re: Updating / keeping current strategies? From: Russell Haley To: Warner Losh 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: Mon, 14 Dec 2015 07:36:05 -0000 With sata support soon available (https://reviews.freebsd.org/D4240 ?) is there any thought to look at ZFS on Arm? Russ On Tue, Dec 8, 2015 at 9:29 AM, Warner Losh wrote: > > > 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" >> > >