From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: permanent kernel upgrading (was: bug and fun with XFS: unable to handle kernel NULL pointer dereference)
Date: Mon, 26 Jul 2010 17:17:26 +1000 [thread overview]
Message-ID: <20100726071726.GG7362@dastard> (raw)
In-Reply-To: <201007260752.59573@zmi.at>
On Mon, Jul 26, 2010 at 07:52:54AM +0200, Michael Monnerie wrote:
> This brings me to another question: openSUSE 11.1 is, despite being old,
> still maintained, so I was under the impression that I'd get updates for
> problems.
Most subsystems are not directly "maintained" by the distro
maintainers. They _hope_ the upstream developers backport all their
bug fixes to "long term stable" kernels like 2.6.27 and just merge
those backports in. The reality is that after one or two releases,
upstream has moved on and the long-term stable kernels don't see
very many fixes from upstream...
> But I already received "upgrade your kernel" the last time for
> my openSUSE 11.2 with it's kernel vmlinuz-2.6.31.12, which by the time
> was the latest release (in the meantime openSUSE 11.3 got released).
Yup, that's the distro maintainer's way of saying "we don't actively
support that subsystem".
> So is this just a generic recommendation of developers who love the
> bleeding-edge stuff and know how many problems they fixed since 2.6.27
> ("yak, that old stuff, how could it ever run?"), or is it known that not
> enough fixes go into "maintained" kernels by distributions?
I think it is more of a reflection on where resources are available.
Most free distros do very little in the way of maintenance except
for security issues because they don't have the knowledge or
resources to triage and fix most subsystems.
However, upstream resources are limited. If we identify a problem as
a fixed bug, then it is up to the distro maintainers to backport it,
not us. Distro maintenance is not our problem or responsisbility
because no upstream developer has the bandwidth to be able to supply
fixes to everyone, nor are they likely to want to beause it's mostly
boring, unrewarding work.
That said, many upstream developers are also distro
maintainers and as a result those distros tend to keep up to date
with all needed fixes for those subsystems.
> I have tons of servers to maintain, and can't compile kernels on my own
> anymore (I did this when I was younger), so I used openSUSE and I am in
> the process of replacing servers to SLES, which should receive much
> better services but still kernel upgrading is not supported on such
> platforms. So what is the best practice that one should choose when
> running "long time services" where you can't upgrade all the time?
Purchase a support contract for an enterprise distro that actively
supports the features you require....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-26 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 22:19 bug and fun with XFS: unable to handle kernel NULL pointer dereference Michael Monnerie
2010-07-26 0:18 ` Dave Chinner
2010-07-26 5:52 ` permanent kernel upgrading (was: bug and fun with XFS: unable to handle kernel NULL pointer dereference) Michael Monnerie
2010-07-26 7:17 ` Dave Chinner [this message]
2010-07-26 8:43 ` Michael Monnerie
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=20100726071726.GG7362@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/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