| 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: <20100924092929.GC5453@cr0.nay.redhat.com> Date: Fri, 24 Sep 2010 17:29:29 +0800 From: Américo Wang <xiyou.wangcong@...il.com> To: Geoffrey Said <geoffrey@...com> Cc: Américo Wang <xiyou.wangcong@...il.com>, stable@...nel.org, linux-kernel@...r.kernel.org, greg@...ah.com Subject: Re: Long maintenance kernel versions. On Fri, Sep 24, 2010 at 07:42:50AM +0200, Geoffrey Said wrote: >Thanks for the prompt reply, > >but this puts us at a disadvantage as we will not know which kernel >will be long term supported when starting the development process. > That is true, unfortunately. >Take our case for the 34 kernel. I knew that SuSE were going to use >the 34 kernel in their 11.3 and since it was the latest we started >work on the integration. Now after the work is almost over, we hear >that it will not be maintained anymore and we need to move to 35. I >do not think that this is a good system for people like us which have >limited resources at their disposal. > Why not just pick .32? And backport features from 34 to 32. That should not be hard. >Can I suggest that their is a road map and long term maintenance >kernels are ear marked before hand by the major Linux distributions? >This will enable us to wait and integrate kernels fully confident that >they will be long term supported. > I think Greg is the right person to answer this question. :) Thanks! -- 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