From owner-freebsd-current@FreeBSD.ORG Tue Dec 4 23:34:12 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4839653; Tue, 4 Dec 2012 23:34:12 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD4C8FC13; Tue, 4 Dec 2012 23:34:12 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so5905812oag.13 for ; Tue, 04 Dec 2012 15:34:11 -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=SXVgzq0WNPPG/a1uhxEUSDQzzb1dwJQBMw94XTa1rPY=; b=QKFykCh3QozquODFki6g6NBdKNieqgcsV5Zb/2JRfVfM3LnXdwhFCUuCJvZzz/0N9P TXpWiogKyMAcg/FkZPkRh2nGuWwnmeBFTR63LNsx2pcXhgLfoyVh36dGk1BSFq41SX8+ 7iq/AsFqsa0jCOj7hCP/wWvIpYpJj+5MRg4yv3Qvdupf/buGWKtwvo7BXmnFAWwt1O10 BoYpJSVWae2rWpGXNGeK1xC0GFiiXdFyy0FgM3FIroMGYjbpK26jpm3REjl9coi92omR Uquu/d6RIWudyenVgYshtBb2QO3H+GoAY8QDTfrFtEksHIzSjBURanvU2TD3hzmXjFSL 1RqQ== MIME-Version: 1.0 Received: by 10.60.172.229 with SMTP id bf5mr12885078oec.81.1354664051456; Tue, 04 Dec 2012 15:34:11 -0800 (PST) Received: by 10.60.170.167 with HTTP; Tue, 4 Dec 2012 15:34:11 -0800 (PST) In-Reply-To: <80F27F05-232F-4014-98C5-31AC5FCF2188@bsdimp.com> References: <1167404891.20121103170049@serebryakov.spb.ru> <534994431.20121104025602@serebryakov.spb.ru> <80F27F05-232F-4014-98C5-31AC5FCF2188@bsdimp.com> Date: Wed, 5 Dec 2012 01:34:11 +0200 Message-ID: Subject: Re: FreeBSD as read-only firmware From: Alexander Yerenkow To: Warner Losh Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Garrett Cooper , lev@freebsd.org, freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 23:34:12 -0000 2012/12/4 Warner Losh > [ replying to an old thread, sorry ] > > On Nov 3, 2012, at 4:56 PM, Lev Serebryakov wrote: > > > Hello, Alexander. > > You wrote 4 =CE=CF=D1=C2=D2=D1 2012 =C7., 2:12:03: > > > > AY> Quick glance to nanobsd give me impression that: > > AY> 1) nanobsd is MBR based, so : > > AY> 2) nanobsd is disk-name-change sensitive. > > Here are patches to support GPT > > I'd love to see those... The mailing list must have eaten the original > ones. > > > AY> GPT way is better - I'm using r${REV} as label, and root can be > mounted no > > AY> matter how many other "firmware's" present, or how disks are ordere= d. > > > > AY> BTW, due to bug 173309 I had to rebuild and update my server, which > took > > AY> only few minutes for reboot. > > > > AY> Well, nanobsd is great thing, I'll look into it a bit more, but it'= s > goal > > AY> to have minified FreeBSD, while I need read-only one. > > No. Its goal is to have RO and ACID-upgradable system (with two code > > slices for this). > > Yes. NanoBSD's way isn't the best, and if there's better ways for it to d= o > its thing, then I'm all for updating it to cope better. I have a bit of = a > backlog of NanoBSD patches to get to, which is why this caught my eye, an= d > since 9.1 will soon be a totally done deal, what better time to hack on > NanoBSD and merge... > I'm using these simple scripts https://github.com/yerenkow/freebsd-vm-image/tree/master/freebsd-firmware to build RO-images both for VMs and for SD cards (GPT or MBR for buggy BIOSes). I don't like idea of upgrading something (via some doubling partitions, or else), at this stage; it's still potential room for problems= . Have one release image fully replaced by other release image - is what seems fit for my goals and requirements; possibility of adding some checksums would be nice too. Probably this could be implemented in nanoBSD too. > > Warner > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " --=20 Regards, Alexander Yerenkow