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:	Wed, 17 Aug 2011 13:20:37 -0700 (PDT)
From:	david@...g.hm
To:	Jeremiah Foster <jeremiah@...emiahfoster.com>
cc:	Greg KH <greg@...ah.com>, Ben Hutchings <ben@...adent.org.uk>,
	linux-kernel@...r.kernel.org, stable@...nel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	stable-review@...nel.org, alan@...rguk.ukuu.org.uk,
	Debian kernel maintainers <debian-kernel@...ts.debian.org>
Subject: Re: [stable] [Stable-review] Future of the -longterm kernel releases
 (i.e. how we pick them).

On Wed, 17 Aug 2011, Jeremiah Foster wrote:

>> Do they need help from the community
>> instead to help define, implement, and maintain this for them?
>
> I think the answer is yes.
>

to expand on this a bit.

it's a lot easier to look at changelogs and see if a -stable or -longterm 
update is relavent to your systems than it is to watch the flood of 
merges to the latest kerenl and then figure out how to backport them. BUt 
people who start up just compiling their own kernels frequently become 
testers, if not contributers to the kernel. If everyone only runs the 
distro kernels, then the upstream kernel quality will suffer because 
nobody is testing it.

people running -longterm kernels on their productionsystems will not be 
testing the llatest -rc kernel on those systems, but they are likely to be 
more interested in watching and testng new kernel releases (at least on 
lab machines) than people who just wait for things to be backported to the 
distro kernel.

David Lang

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ