From owner-freebsd-current@FreeBSD.ORG  Sat Nov  3 22:56:10 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 F2406DFB
 for <freebsd-current@freebsd.org>; Sat,  3 Nov 2012 22:56:10 +0000 (UTC)
 (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [IPv6:2a01:4f8:131:60a2::2])
 by mx1.freebsd.org (Postfix) with ESMTP id 81E188FC08
 for <freebsd-current@freebsd.org>; Sat,  3 Nov 2012 22:56:10 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:dc:ffe:46f:81d2])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A5FF34AC31;
 Sun,  4 Nov 2012 02:56:08 +0400 (MSK)
Date: Sun, 4 Nov 2012 02:56:02 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD
X-Priority: 3 (Normal)
Message-ID: <534994431.20121104025602@serebryakov.spb.ru>
To: Alexander Yerenkow <yerenkow@gmail.com>
Subject: Re: FreeBSD as read-only firmware
In-Reply-To: <CAPJF9w=x+iSN9BuEcq8KOM7px1-B_n0oDfeFsyWkWesTCLDjhw@mail.gmail.com>
References: <CAPJF9wmO-oO7cy4XUwnTMb5cpD14TaK430rWW2nqodBFWw54DQ@mail.gmail.com>
 <1167404891.20121103170049@serebryakov.spb.ru>
 <CAPJF9wmVPxMDBqyy=Dqdnb+Z33f_wLDx9CFbk_oSEx4inboK6A@mail.gmail.com>
 <CAGH67wQORX7_N6-ggpeaLFzj0Gcy9H64EO91gHi2pcuGTE3CfQ@mail.gmail.com>
 <CAPJF9w=x+iSN9BuEcq8KOM7px1-B_n0oDfeFsyWkWesTCLDjhw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: Garrett Cooper <yanegomi@gmail.com>,
 freebsd-current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: lev@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Nov 2012 22:56:11 -0000

Hello, Alexander.
You wrote 4 =D0=BD=D0=BE=D1=8F=D0=B1=D1=80=D1=8F 2012 =D0=B3., 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

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 ordered.

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 go=
al
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).


--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>