Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Feb 2009 22:35:24 +0000
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Marcel Moolenaar <xcllnt@mac.com>
Cc:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, Marcel Moolenaar <marcel@FreeBSD.org>, FreeBSD current mailing list <current@FreeBSD.org>
Subject:   Re: boot0cfg -s vs. GEOM_PART_*? 
Message-ID:  <16678.1234910124@critter.freebsd.dk>
In-Reply-To: Your message of "Tue, 17 Feb 2009 14:10:10 PST." <E842D9CC-DEA8-4198-825F-46ED29437AE0@mac.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <E842D9CC-DEA8-4198-825F-46ED29437AE0@mac.com>, Marcel Moolenaar wri
tes:

>> In message <D29A6039-5105-49CB-B613-DD561CDD1A89@mac.com>, 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16678.1234910124>