From owner-freebsd-current@FreeBSD.ORG  Sat Nov  3 22:12:04 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 E91AD197;
 Sat,  3 Nov 2012 22:12:04 +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 923648FC0C;
 Sat,  3 Nov 2012 22:12:04 +0000 (UTC)
Received: by mail-oa0-f54.google.com with SMTP id n9so5896906oag.13
 for <multiple recipients>; Sat, 03 Nov 2012 15:12:03 -0700 (PDT)
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=jE3N/ii00l9QlekqCTseh/C3p7YasvMinYemEWA0OZo=;
 b=hM6rXMNpkB8z6xmsmhvjvNsqwuxu8JqTDlAeJczkILGeGm1X7KHJRB8KzJEZZzPeSt
 fxbobXKv/zGMrv2oyb1AU7WAP+a5d2KiKzzsD1l4oW0bjF5IdqviRRPkjLGR5hWRi63a
 LG1bhr+eRnApB/lREoIbRap1b1eXBU+SUK/CijlmszezaiIh8WMDukO0LXL77q47ZQQq
 9w77sIJeQJ1nBVThs181lz2cMrYlfNfduQFs1Qk889a+AKetcwuQDBHFqPYiu6TJHykK
 7bfWz1wgP/xW8+Wc6/O4GAHCXiThMtvteV8XIL5bUlxEVaN4bGMMyY9FzpD/nd97eaXZ
 AGow==
MIME-Version: 1.0
Received: by 10.60.26.72 with SMTP id j8mr4591062oeg.68.1351980723725; Sat, 03
 Nov 2012 15:12:03 -0700 (PDT)
Received: by 10.60.58.165 with HTTP; Sat, 3 Nov 2012 15:12:03 -0700 (PDT)
In-Reply-To: <CAGH67wQORX7_N6-ggpeaLFzj0Gcy9H64EO91gHi2pcuGTE3CfQ@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>
Date: Sun, 4 Nov 2012 00:12:03 +0200
Message-ID: <CAPJF9w=x+iSN9BuEcq8KOM7px1-B_n0oDfeFsyWkWesTCLDjhw@mail.gmail.com>
Subject: Re: FreeBSD as read-only firmware
From: Alexander Yerenkow <yerenkow@gmail.com>
To: Garrett Cooper <yanegomi@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: lev@freebsd.org, freebsd-current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
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:12:05 -0000

Quick glance to nanobsd give me impression that:
1) nanobsd is MBR based, so :
2) nanobsd is disk-name-change sensitive.

GPT way is better - I'm using r${REV} as label, and root can be mounted no
matter how many other "firmware's" present, or how disks are ordered.

BTW, due to bug 173309 I had to rebuild and update my server, which took
only few minutes for reboot.

Well, nanobsd is great thing, I'll look into it a bit more, but it's goal
to have minified FreeBSD, while I need read-only one.



-- 
Regards,
Alexander Yerenkow