Date: Tue, 17 Feb 2009 20:27:39 +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: <15768.1234902459@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 17 Feb 2009 12:23:26 PST." <F04BCAF6-2478-4724-A7E6-94BD43BE77DB@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <F04BCAF6-2478-4724-A7E6-94BD43BE77DB@mac.com>, Marcel Moolenaar wri tes: >> We do not want arbitrary large binary blobs in the confxml >> output. > >I'm not going to start a discussion on arbitrariness >and largeness of bootcode. Instead, let me just ask: > >Do you have alternatives? Open the parent device, use read(2) to get it. You can always open an geom device for reading (subject to filesystem permissions). -- 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?15768.1234902459>