From owner-freebsd-embedded@FreeBSD.ORG Mon Apr 11 14:35:27 2011 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 665CE1065675; Mon, 11 Apr 2011 14:35:27 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA4F8FC1A; Mon, 11 Apr 2011 14:35:27 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p3BEUobi064552 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Mon, 11 Apr 2011 08:31:51 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=koi8-r From: Warner Losh X-Priority: 3 (Normal) In-Reply-To: <924400541.20110411125319@serebryakov.spb.ru> Date: Mon, 11 Apr 2011 08:31:50 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <62AD945C-4357-433B-8BED-7E5BB9233B75@bsdimp.com> References: <116932102.20110411113412@serebryakov.spb.ru> <924400541.20110411125319@serebryakov.spb.ru> To: lev@freebsd.org X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Mon, 11 Apr 2011 08:31:51 -0600 (MDT) Cc: freebsd-embedded@freebsd.org Subject: Re: Does somebody work on NanoBSD? X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 14:35:27 -0000 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