| 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
| ||
|
Date: Thu, 31 Aug 2006 10:01:16 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Roman Zippel <zippel@...ux-m68k.org> CC: Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org, Christoph Hellwig <hch@...radead.org>, David Howells <dhowells@...hat.com>, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2] Roman Zippel wrote: > On Thu, 31 Aug 2006, Adrian Bunk wrote: [...] >> sending users from one menu to another for first manually >> selecting this or that option is less easy for the user than the usage >> of select. > > How often does he have to do that? Is it really worth it fucking with the > kconfig system? Adrian, Roman, both the comment hack and the 'select' hack introduce redundancy into the Kconfig files and add maintenance cost. In addition, 'select' currently brings a danger of inconsistent configuration. As I said before, the proper solution would be enhancements to the "make XYZconfig" UIs to comfortably present unfulfilled dependencies, based on 'depends on' alone. Alas my posting here is yet another one without a patch included... -- 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/
Powered by blists - more mailing lists