Date: Sun, 4 Nov 2012 00:12:03 +0200 From: Alexander Yerenkow <yerenkow@gmail.com> To: Garrett Cooper <yanegomi@gmail.com> Cc: lev@freebsd.org, freebsd-current <freebsd-current@freebsd.org> Subject: Re: FreeBSD as read-only firmware Message-ID: <CAPJF9w=x%2BiSN9BuEcq8KOM7px1-B_n0oDfeFsyWkWesTCLDjhw@mail.gmail.com> In-Reply-To: <CAGH67wQORX7_N6-ggpeaLFzj0Gcy9H64EO91gHi2pcuGTE3CfQ@mail.gmail.com> References: <CAPJF9wmO-oO7cy4XUwnTMb5cpD14TaK430rWW2nqodBFWw54DQ@mail.gmail.com> <1167404891.20121103170049@serebryakov.spb.ru> <CAPJF9wmVPxMDBqyy=Dqdnb%2BZ33f_wLDx9CFbk_oSEx4inboK6A@mail.gmail.com> <CAGH67wQORX7_N6-ggpeaLFzj0Gcy9H64EO91gHi2pcuGTE3CfQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPJF9w=x%2BiSN9BuEcq8KOM7px1-B_n0oDfeFsyWkWesTCLDjhw>