Date: Thu, 2 May 2013 11:38:36 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-arch@freebsd.org Cc: Stacey Son <sson@freebsd.org> Subject: Re: A General or Miscellaneous Binary Image Activator Message-ID: <201305021138.36554.jhb@freebsd.org> In-Reply-To: <71BF89C0-13F9-41CA-9F7E-A3FDE11C2346@FreeBSD.org> References: <71BF89C0-13F9-41CA-9F7E-A3FDE11C2346@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, May 01, 2013 7:02:49 pm Stacey Son wrote: > Of course, comments, questions, concerns, etc. are welcome. Certainly the ability to cross-build ports in this way is a huge win. I just have a few comments on the kern.binmisc sysctl: It seems to be a bit overloaded and not used like a typical sysctl. A better match would seem to be a /dev/binmisc that you perform ioctl's on. A sysctl might still make better sense for enumerating the interperter entries, but the more typical way to do that would either be to have kern.binmisc.<n> be a sysctl that returns item <n> in the list, or to have the kern.binmisc sysctl that just returns an array of xbe entries (rather than having separate list/lookup operations) similar to how the kern.proc sysctls work. If you were to do this, I would probably prefer the second approach (one sysctl that returns a consistent snapshot). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201305021138.36554.jhb>