Date: Mon, 11 Apr 2011 08:31:50 -0600 From: Warner Losh <imp@bsdimp.com> To: lev@freebsd.org Cc: freebsd-embedded@freebsd.org Subject: Re: Does somebody work on NanoBSD? Message-ID: <62AD945C-4357-433B-8BED-7E5BB9233B75@bsdimp.com> In-Reply-To: <924400541.20110411125319@serebryakov.spb.ru> References: <116932102.20110411113412@serebryakov.spb.ru> <BANLkTimh582Lbsn0JmXg1MZmpEB%2BTYr6Gw@mail.gmail.com> <924400541.20110411125319@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 11, 2011, at 2:53 AM, Lev Serebryakov wrote:
> Hello, Olivier.
> You wrote 11 =C1=D0=D2=C5=CC=D1 2011 =C7., 11:51:09:
>=20
>>> Does 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 =
completely
>>> 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
>=20
> (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.
That hardly qualifies as completely broken.
Those are bugs, and I'll look at fixing them.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62AD945C-4357-433B-8BED-7E5BB9233B75>