| 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: <46D976D0.7030208@s5r6.in-berlin.de> Date: Sat, 01 Sep 2007 16:27:28 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Bartlomiej Zolnierkiewicz <bzolnier@...il.com> CC: Jeff Garzik <jeff@...zik.org>, "Robert P. J. Day" <rpjday@...dspring.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: maturity and status and attributes, oh my! Bartlomiej Zolnierkiewicz wrote: ... > Part of the problem is that many people (including developers) learn about > things being deprecated/obsoleted after they are actually removed. > > Of course things are not black and white and common sense is required but > moving in the Kconfig direction is an improvement IMO and could speed up > the development in the long-term. ... I basically agree. Most people use precompiled kernel packages though. For them we add kernel log messages, for example. We also preemptively get in touch with user mailinglists and the like, but we reach only a fraction of affected people there either. For people who actually compile kernels, especially distributors, it would indeed be helpful if "make oldconfig" and Co. show a prompt if an option entered feature removal schedule. Actually this has been done before for things like particular sysfs changes, with ad-hoc CONFIG_ variables. -- 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