Date: Tue, 17 Feb 2009 10:29:10 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Marcel Moolenaar <marcel@FreeBSD.org>, FreeBSD current mailing list <current@freebsd.org> Subject: Re: boot0cfg -s vs. GEOM_PART_*? Message-ID: <D1292F9E-BF53-443F-9E63-92D527A41A3B@mac.com> In-Reply-To: <20090217113718.N53478@maildrop.int.zabbadoz.net> References: <20090217113718.N53478@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
> I am wondering how to change it from a rnning system now, as
>
> dopt# gpart set -a active -i 3 ad4
> gpart: pre-check failed: Device not configured
Fixed in revision 188723.
Sorry about that.
--
Marcel Moolenaar
xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D1292F9E-BF53-443F-9E63-92D527A41A3B>