From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 18:37:13 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CCC710656C8 for ; Tue, 17 Feb 2009 18:37:13 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from bene2.itea.ntnu.no (bene2.itea.ntnu.no [IPv6:2001:700:300:3::57]) by mx1.freebsd.org (Postfix) with ESMTP id E8FA08FC08 for ; Tue, 17 Feb 2009 18:37:12 +0000 (UTC) (envelope-from ulf.lilleengen@gmail.com) Received: from localhost (localhost [127.0.0.1]) by bene2.itea.ntnu.no (Postfix) with ESMTP id 42A359000C; Tue, 17 Feb 2009 19:37:11 +0100 (CET) Received: from carrot (unknown [IPv6:2001:700:300:3::184]) by bene2.itea.ntnu.no (Postfix) with ESMTP id E11509000B; Tue, 17 Feb 2009 19:37:10 +0100 (CET) Date: Tue, 17 Feb 2009 19:38:00 +0000 From: Ulf Lilleengen To: Marcel Moolenaar Message-ID: <20090217193759.GA27739@carrot> References: <20090217113718.N53478@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) X-Virus-Scanned: Debian amavisd-new at bene2.itea.ntnu.no Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: boot0cfg -s vs. GEOM_PART_*? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 18:37:14 -0000 On Tue, Feb 17, 2009 at 10:29:10AM -0800, Marcel Moolenaar wrote: > > On Feb 17, 2009, at 3:46 AM, Bjoern A. Zeeb wrote: > > > with a fresh kernel and world from last night I get: > > > > dopt# boot0cfg -s 3 ad4 > > boot0cfg: /dev/ad4: ad4 > > boot0cfg: /dev/ad4: ioctl DIOCSMBR: Inappropriate ioctl for device > > > > is this GEOM_PART_* fallout and can it be fixed? > > boot0cfg is not (yet) supported by GPART. It should not > be too hard: > 1. We need to expose the current bootcode through > kern.geom.confxml > 2. boot0cfg grabs the bootcode from the XML, makes > the changes in memory and then uses existing > g_part ctlreq to update the bootcode. Mhm, this seems to be a good way to do it. Also, fdisk and bsdlabel might need a sweep as well. -- Ulf Lilleengen