linux-kernel - Re: Announcement: Plans for v2.6.34-longterm

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]

Message-ID: <20101205165034.GA15738@kroah.com>
Date:	Sun, 5 Dec 2010 08:50:34 -0800
From:	Greg KH <greg@...ah.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...nel.org,
	jason.wessel@...driver.com, Andi Kleen <andi@...stfloor.org>,
	lwn@....net
Subject: Re: Announcement: Plans for v2.6.34-longterm

On Sat, Dec 04, 2010 at 08:16:44PM -0500, Paul Gortmaker wrote:
> [Re: Announcement: Plans for v2.6.34-longterm] On 04/12/2010 (Sat 09:28) Greg KH wrote:
> 
> > On Fri, Dec 03, 2010 at 04:07:19PM -0500, Paul Gortmaker wrote:
> > > With that in mind, it is our intention to also maintain a 2.6.34
> > > longterm tree.  Jason and I work at Wind River, which already has
> > > released products based on v2.6.34, and as such it only makes sense
> > > to have a public long-term tree that others who are also based on
> > > 2.6.34 can make use of.
> > 
> > Other than Wind River, what other distros/userbases are using .34 as a
> > platform for their products?
> 
> Well, since we create more of a distro builder, than a distro itself,
> anyone who uses WR to in turn create a distro for their own hardware or
> product will of course be using 2.6.34.  The Yocto project is currently
> using the 2.6.34 kernel and I'm sure there are others I'm not
> immediately aware of.

I thought Yocto was going to be using .35, hence Andi and Tim's work to
get that one "longterm"?

Anyway, that's fine, I was just curious, thanks.

> > And how long do you expect to be maintaining this .34 branch for?
> 
> The expectation is that maintenance will be ongoing for years, since
> we'll largely be needing to do that work anyway.  I plan to follow your
> lead on how you handled .27 -- i.e. the "early" releases will possibly
> be rich with content, but as it gets to be closer to EOL (i.e. on the
> order of 10 releases removed from current), then it will only be the key
> CVE-like fixes and similar which will be added.

That sounds very reasonable.

If there's anything I can do to help out, let me know.

thanks,

greg k-h
--
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/