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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 20 Nov 2006 19:13:19 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	lkml <linux-kernel@...r.kernel.org>, zippel@...ux-m68k.org,
	jejb <james.bottomley@...eleye.com>
Subject: Re: how to handle indirect kconfig dependencies

On Fri, Nov 17, 2006 at 02:55:09PM +0100, Stefan Richter wrote:
> 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.
>...

BTW:
"All of the various shipped tools ... need to be fixed" is a bit 
misleading since one of the features of the 2.6 kconfig is that this 
code is shared by all tools.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/