linux-kernel - Re: how to handle indirect kconfig dependencies

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <455DBF3D.40801@s5r6.in-berlin.de>
Date:	Fri, 17 Nov 2006 14:55:09 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	lkml <linux-kernel@...r.kernel.org>, zippel@...ux-m68k.org,
	jejb <james.bottomley@...eleye.com>
Subject: Re: how to handle indirect kconfig dependencies

Randy Dunlap wrote:
> I have a (randconfig) build of 2.6.19-rc5-mm2 with:
[...]
> so the question is:
> (How) can kconfig follow the dependency chain and either
> - prevent this odd config combination or
> - see that 'select DEBUG_FS' implies 'select SYSFS' and then enable SYSFS
> ?
> 
> I don't believe that the right answer is to add
> 	depends on SYSFS
> to DEBUG_READAHEAD.

I know this doesn't concludingly answer your question, but: All of the
various shipped tools to generate .config need to be fixed to recognize
"select" to imply a dependency like "depends on" does.

[...]
> ~Randy [or just kill off select]

Or this. ("select" appears to be useful for dialog driven creation of
.config in cases where developers are able to predetermine preferences
of users --- nothing more and nothing less.)
-- 
Stefan Richter
-=====-=-==- =-== =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/