Date: Mon, 11 Apr 2011 12:53:19 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: =?iso-8859-1?Q?Olivier_Cochard-Labb=E9?= <olivier@cochard.me> Cc: freebsd-embedded@freebsd.org Subject: Re: Does somebody work on NanoBSD? Message-ID: <924400541.20110411125319@serebryakov.spb.ru> In-Reply-To: <BANLkTimh582Lbsn0JmXg1MZmpEB%2BTYr6Gw@mail.gmail.com> References: <116932102.20110411113412@serebryakov.spb.ru> <BANLkTimh582Lbsn0JmXg1MZmpEB%2BTYr6Gw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Olivier.
You wrote 11 =E0=EF=F0=E5=EB=FF 2011 =E3., 11:51:09:
>> =A0Does somebody work on NanoBSD? It was not MFCed for long time on one
>> hand, and on other hand, support of NANO_LABEL, added to CURRENT, is com=
pletely
>> broken and almost useless.
> I'm using the NANO_LABEL support, and I didn't have any problem.
> What's your label problem with nanobsd precisely ?
(1) Copied out "upgrade" image has always ${NANO_LABEL}s1 label, and
needs manual mdconfig+tunefs before dumping on second code partition
(2) updatep2 script uses sed 's/${NANO_DRIVE}s1/${NANO_DRIVE}s2/'
script, and if NANO_LABLE is in use (which sets NANO_DRIVE to
"ufs/labels1") sed complains.
--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?924400541.20110411125319>