From owner-freebsd-current  Wed Dec  4  5:17:43 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6BBB937B401
	for <freebsd-current@freebsd.org>; Wed,  4 Dec 2002 05:17:42 -0800 (PST)
Received: from MX1.estpak.ee (ld1.estpak.ee [194.126.101.98])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DD4ED43E88
	for <freebsd-current@freebsd.org>; Wed,  4 Dec 2002 05:17:41 -0800 (PST)
	(envelope-from kalts@estpak.ee)
Received: from tiiu.internal (80-235-36-70-dsl.mus.estpak.ee [80.235.36.70])
	by MX1.estpak.ee (Postfix) with ESMTP id 8104F8886B
	for <freebsd-current@freebsd.org>; Wed,  4 Dec 2002 15:16:42 +0200 (EET)
Received: from tiiu.internal (localhost [127.0.0.1])
	by tiiu.internal (8.12.6/8.12.6) with ESMTP id gB4DHdL7001993
	for <freebsd-current@freebsd.org>; Wed, 4 Dec 2002 15:17:39 +0200 (EET)
	(envelope-from vallo@tiiu.internal)
Received: (from vallo@localhost)
	by tiiu.internal (8.12.6/8.12.6/Submit) id gB4DHdCE001992
	for freebsd-current@freebsd.org; Wed, 4 Dec 2002 15:17:39 +0200 (EET)
	(envelope-from vallo)
Date: Wed, 4 Dec 2002 15:17:39 +0200
From: Vallo Kallaste <kalts@estpak.ee>
To: freebsd-current@freebsd.org
Subject: unable to use boot0cfg
Message-ID: <20021204131738.GA1940@tiiu.internal>
Reply-To: kalts@estpak.ee
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.1i-ja.1
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Hi

I'm using both -current and -stable on the same machine, very
common. Boot0cfg has -s [12345] flag to set the slice to boot on and
it has been working so far. Beginning from Dec 1, I'm unable to set
the slice:

root:vallo# boot0cfg -v ad0     
#   flag     start chs   type       end chs       offset         size
1   0x80      0:  1: 1   0xa5   1023: 15:63           63     16382961
2   0x00   1023:255:63   0xa5   1023: 15:63     16383024     16383024

version=1.0  drive=0x80  mask=0xf  ticks=182
options=packet,update,nosetdrv
default_selection=F1 (Slice 1)
root:vallo# boot0cfg -v -s 2 ad0
boot0cfg: /dev/ad0: Operation not permitted
root:vallo# disklabel -W ad0
disklabel: /dev/ad0: Operation not permitted

This is probably related to recent (re)work to protect disk labels,
but I'm not authoritative. This is not a fair way to stick me to
-current :-)
-- 

Vallo Kallaste
kalts@estpak.ee

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message