linux-kernel - Re: Linux 2.6.27.28

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:	Sat, 25 Jul 2009 14:18:56 +1000
From:	Bron Gondwana <brong@...tmail.fm>
To:	Greg KH <gregkh@...e.de>
Cc:	Éric Piel <eric.piel@...mplin-utc.net>,
	webmaster@...nel.org, LKML <linux-kernel@...r.kernel.org>,
	stable@...nel.org
Subject: Re: Linux 2.6.27.28

On Fri, Jul 24, 2009 at 08:30:30PM -0700, Greg KH wrote:
> On Sat, Jul 25, 2009 at 01:49:53AM +0200, Éric Piel wrote:
> > Currently, there is no clue on www.kernel.org that 2.6.27 is a "long
> > term stable" kernel tree. Would it be possible to add a line to the page
> > pointing to the latest version of this type of tree? I'm sure some
> > people would love discovering that such thing exists :-)
> 
> I'm curious as to why someone, if they were inclined to be using such a
> thing, wouldn't already know about this?
> 
> How many people really are relying on this .27 branch, becides the
> distros, these days?  And if you are, why?

We had some instability with .29, and it was annoying enough that I've
"standardised" on 2.6.27.25 across all the new installs of our servers
(largely because that was current back when I build those packages a
couple of weeks ago) - and since I'm reinstalling everything with the
shiny new Debian Lenny personality, we're running .27 on most of our
servers now.

I'm a little cautious about .30 because of the reiserfs changes that went
in.  All our customer data is on reiserfs partitions, and I want to take
it nice and slow testing it...

Er, that about covers it I think.  We'll probably jump to .30 or .31 at
some point.

Oh, yeah.  Bloody ipssend.  If anyone from IBM is reading this, can you
please hit your software distribution people over the head with a big
fat cluebat and provide your raid management tools as a single download
somewhere that's not a self extracting windows executable floppy image or
a .iso containing a self extracting windows executable floppy image, or...
you get the picture.  It's a disgrace.  And while you're at it, build an
ipssend that works with kernels 2.6.28+.  Thanks.

Bron.
--
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/