From owner-freebsd-stable@FreeBSD.ORG Fri Oct 1 07:45:10 2010 Return-Path: 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 039BF1065696 for ; Fri, 1 Oct 2010 07:45:10 +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 B521A8FC1B for ; Fri, 1 Oct 2010 07:45:09 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1P1a0v-0009QQ-Rt for freebsd-stable@freebsd.org; Fri, 01 Oct 2010 09:26:41 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Oct 2010 09:26:41 +0200 From: Daniel Braniss Message-ID: Subject: boot0cfg problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2010 07:45:10 -0000 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)