Date: Fri, 11 Jun 2010 12:28:58 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Alexander Leidinger <Alexander@leidinger.net> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-hackers@freebsd.org, Ilya Bakulin <webmaster@kibab.com>, Garrett Cooper <yaneurabeya@gmail.com> Subject: Re: GSoC: registration of optional kernel features via sysctl: a question to the community Message-ID: <AANLkTimTVmKz2b50GWTDktRTqJaKMsxOz4Uuo6wJP2Rj@mail.gmail.com> In-Reply-To: <20100610160109.19585782fyr3buw4@webmail.leidinger.net> References: <20100609121453.095d92b4@kibab.com> <4C0F9394.9030202@dataix.net> <20100609132543.GI83316@deviant.kiev.zoral.com.ua> <A4C894EA-8039-459B-B4C8-8F7CC98421F8@gmail.com> <20100610101801.742fac25@ernst.jennejohn.org> <20100610160109.19585782fyr3buw4@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
How about exposing a simple userspace API for doing this, rather than doing it via sysctl? That way you could "simply" tie alternative overrides in as needed for builds (eg, environment variables setting overrides; and/or pointing to a configuration file with such) but not affect any runtime detection the rest of the system is doing. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimTVmKz2b50GWTDktRTqJaKMsxOz4Uuo6wJP2Rj>