From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 22:35:23 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 29E361065678; Tue, 17 Feb 2009 22:35:23 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id E08E48FC27; Tue, 17 Feb 2009 22:35:22 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id A071A3F130; Tue, 17 Feb 2009 22:35:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n1HMZO9C016679; Tue, 17 Feb 2009 22:35:24 GMT (envelope-from phk@critter.freebsd.dk) To: Marcel Moolenaar From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 17 Feb 2009 14:10:10 PST." Date: Tue, 17 Feb 2009 22:35:24 +0000 Message-ID: <16678.1234910124@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: "Bjoern A. Zeeb" , Marcel Moolenaar , 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 22:35:23 -0000 In message , Marcel Moolenaar wri tes: >> In message , Marcel >> Moolenaar wri >> tes: >> >>> For boot0cfg this is probably acceptable, because >>> it only operates on MBRs. But as a generic solution >>> this won't work. >> >> Then pick up the bootcode via ioctls, it does not belong >> in the confxml sysctl. > >On what grounds doesn't it belong in the confxml? Because the way we (currently) implement confxml and the uses it is put to would generally be greatly inconvenienced if you have to include 8KB of hexdump data in the xml stream. >And how do these not apply to ioctls? ioctls was designed and built to move binary blobs across the userland/kernel barrier to and from I/O devices. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.