In message <E842D9CC-DEA8-4198-825F-46ED29437AE0_at_mac.com>, Marcel Moolenaar wri tes: >> In message <D29A6039-5105-49CB-B613-DD561CDD1A89_at_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_at_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.Received on Tue Feb 17 2009 - 21:35:23 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:42 UTC