Date: Tue, 17 Feb 2009 19:38:00 +0000 From: Ulf Lilleengen <ulf.lilleengen@gmail.com> To: Marcel Moolenaar <xcllnt@mac.com> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD current mailing list <current@freebsd.org> Subject: Re: boot0cfg -s vs. GEOM_PART_*? Message-ID: <20090217193759.GA27739@carrot> In-Reply-To: <D1292F9E-BF53-443F-9E63-92D527A41A3B@mac.com> References: <20090217113718.N53478@maildrop.int.zabbadoz.net> <D1292F9E-BF53-443F-9E63-92D527A41A3B@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090217193759.GA27739>