From: Bron Gondwana <brong@fastmail.fm>
To: Greg KH <gregkh@suse.de>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>,
webmaster@kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: Linux 2.6.27.28
Date: Sat, 25 Jul 2009 14:18:56 +1000 [thread overview]
Message-ID: <20090725041856.GA21123@brong.net> (raw)
In-Reply-To: <20090725033030.GA481@suse.de>
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.
next prev parent reply other threads:[~2009-07-25 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 22:27 Linux 2.6.27.28 Greg KH
2009-07-24 22:28 ` Greg KH
2009-07-24 23:49 ` Éric Piel
2009-07-25 1:50 ` J.H.
2009-07-25 3:30 ` Greg KH
2009-07-25 4:18 ` Bron Gondwana [this message]
[not found] ` <ck4l6511epc17ngfdu7qu8ln46b7op9lj9@4ax.com>
2009-07-25 5:26 ` Greg KH
2009-07-25 10:34 ` Grant Coady
2009-07-25 7:25 ` Thomas Voegtle
2009-07-25 10:00 ` Thomas Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090725041856.GA21123@brong.net \
--to=brong@fastmail.fm \
--cc=eric.piel@tremplin-utc.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=webmaster@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox