lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <26703.1192942058@turing-police.cc.vt.edu>
Date: Sun, 21 Oct 2007 00:47:38 -0400
From: Valdis.Kletnieks@...edu
To: Sam Ravnborg <sam@...nborg.org>
Cc: Henrik Carlqvist <hc1@...lhem.se>, linux-kernel@...r.kernel.org
Subject: Re: tristate and bool not enogh for Kconfig anymore
On Sat, 20 Oct 2007 21:17:00 +0200, Sam Ravnborg said:
> On Sat, Oct 20, 2007 at 02:42:38PM +0200, Henrik Carlqvist wrote:
> > I think there is a need for Kconfig to specify that a functionality could
> > be built as a module or not built at all.
>
> I assume
> depends on MODULES
>
> should do the trick.
Umm... I think that will work backwards, and give you CONFIG_FOO=y
if.f the kernel *supports* modules. What he needs is to be able to say
CONFIG_FOO=n or CONFIG_FOO=m, but *ban* CONFIG_FOO=y.
(At least, in my kernel, I have MODULES=y, and several other things
from init/Kconfig have 'depends on MODULES' and also end up 'y':
% zgrep MODULE /proc/config.gz
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_MODULE_VERIFY_ELF=y
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists