From owner-freebsd-stable@FreeBSD.ORG  Fri Oct  1 11:20:44 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1FC89106564A
	for <freebsd-stable@freebsd.org>; Fri,  1 Oct 2010 11:20:44 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
	by mx1.freebsd.org (Postfix) with ESMTP id CCC6F8FC0C
	for <freebsd-stable@freebsd.org>; Fri,  1 Oct 2010 11:20:43 +0000 (UTC)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by kabab.cs.huji.ac.il with esmtp
	id 1P1dfO-000BRI-MZ; Fri, 01 Oct 2010 13:20:42 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
In-reply-to: <20101001090143.GA40450@icarus.home.lan> 
References: <E1P1a0v-0009QQ-Rt@kabab.cs.huji.ac.il> 
	<20101001090143.GA40450@icarus.home.lan>
Comments: In-reply-to Jeremy Chadwick <freebsd@jdc.parodius.com>
	message dated "Fri, 01 Oct 2010 02:01:43 -0700."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 01 Oct 2010 13:20:42 +0200
From: Daniel Braniss <danny@cs.huji.ac.il>
Message-ID: <E1P1dfO-000BRI-MZ@kabab.cs.huji.ac.il>
Cc: freebsd-stable@freebsd.org
Subject: Re: boot0cfg problems 
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 11:20:44 -0000

> On Fri, Oct 01, 2010 at 09:26:41AM +0200, Daniel Braniss wrote:
> > In a not so distant past, boot0cfg -sn ... used to work, then it only
> > partialy worked, it would modify the data in boot but not the mbr, for
> > which 'gpart -s set active -in ...' modified the mbr. Now
> > # boot0cfg -s1 -v /dev/mfid0
> > boot0cfg: write_mbr: /dev/mfid0: Operation not permitted
> > but:
> > # boot0cfg -v /dev/mfid0
> > #   flag     start chs   type       end chs       offset         size
> > 1   0x80      0:  1: 1   0xa5   1023:212:63           63     41943006
> > 2   0x00   1023:255:63   0xa5   1023:169:63     41943069     41943006
> > 3   0x00   1023:255:63   0xa5   1023:126:63     83886075     41943006
> > 4   0x00   1023:255:63   0xa5   1023:201:63    125829081   1046478825
> > 
> > version=2.0  drive=0x80  mask=0x3  ticks=182  bell=# (0x23)
> > options=packet,update,nosetdrv
> > volume serial ID 9090-9090
> > default_selection=F2 (Slice 2)
> 
> Can you try doing "sysctl kern.geom.debugflags=16" first?
>
this is not realy foot-shooting :-), but
- the error msg is gone,
- the slice info is updated,
- but the active bit in the mbr is not! - some bioses rely on it.
looking at changes done to boot0cfg.c there is now an err(...) call which
does an exit, before the boot is updated. I changed it to a warn(...) and the 
old
behaviour is back.
BTW, 
a- gpart command should have been: gpart set -a active -i n ...
b- this works with kern.geom.debugflags=0.

thanks,
	danny