mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: linux-kernel@vger.kernel.org, lkcd-devel@lists.sourceforge.net,
	lkcd-general@lists.sourceforge.net,
	lkcd-general-admin@lists.sourceforge.net
Subject: Re: [lkcd-general] Re: What's left over.
Date: Mon, 4 Nov 2002 13:27:59 +0100	[thread overview]
Message-ID: <20021104122759.GG19368@marowsky-bree.de> (raw)
In-Reply-To: <OFE5D1360D.AD5C65BE-ON80256C67.004027FF@portsmouth.uk.ibm.com>

On 2002-11-04T11:59:23,
   Richard J Moore <richardj_moore@uk.ibm.com> said:

> So, for those of use who passionately care whether Linux has a system
> dumping mechanism, we need to regroup, we need to decide the correct
> strategy for gaining LKCD's inclusion into the kernel.  Many of the
> arguments relate to timeliness and ultimately have a commercial benefit. I
> suggest we actively campaign among the various distros who are interested
> in selling Linus businesses and provide support. We also need to
> concentrate on consolidating the various requirements of a system crash
> dump - it's going to be much easier for everyone if there is a consensus on
> system dumping technology.

I think you are somewhat missing the point.

Both RH and UnitedLinux seem to care enough for system dump facilities that
they ship patched kernels (netdump / LKCD, respectively). Anyone who cares can
simply apply the patch themselves, if they want to compile from vanilla
sources. Just buy RH AS or any enterprise product powered by United Linux, and
off you go. I assume that your "enterprise customers" will want to do that
anyway because they need all those very useful certifications...

And since l-k (rightly!) mostly refuses to deal with crash/oops reports from
vendor patched kernels anyway, the distributors have to deal with the
diagnosis themselves already and do so as part of the support contracts.
Anyone who runs their own patched kernels probably also is able to do so.

While I can see the issue that having the patch included in the mainstream
kernel offers the usual advantages, it is by no means the absolute requirement
you make it out to be.

It appears that the facilities are all there now; so 2.6 should be a the
perfect time to test the various approaches in the field. (And face it, field
experience is rather limitted still, but I am very sure it will grow soon
because it is such a useful feature)

Then it can be included. This is how Linux has always worked. reiserfs has
gone through this, as has ext3, XFS, quite a few of the VM patches etc. So no
worries, nobody is being exceptionally harsh in any fashion.

But arguing about "I have so many fortune 100 companies just lined up ready to
say that they support this campaign!" is marketing speak. Go away with that
from Linux kernel, will you.

Come back when it is "I have so many fortune 100 companies actively using this
feature and have solved many problems with it!".


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Principal Squirrel 
SuSE Labs - Research & Development, SuSE Linux AG
  
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
  -- Capt. Edward A. Murphy            -- Louis Pasteur

  reply	other threads:[~2002-11-04 12:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 11:59 Richard J Moore
2002-11-04 12:27 ` Lars Marowsky-Bree [this message]
2002-11-04 12:30 ` [lkcd-devel] " P.A.M. van Dam 
2002-11-04 16:16 ` John Alvord
2002-11-04 16:22 ` Linus Torvalds
2002-11-04 16:57   ` Alan Cox
2002-11-05  9:05     ` Suparna Bhattacharya
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05 20:37 Dr. Greg Wettstein
     [not found] <Pine.LNX.4.44.0211040727330.771-100000@home.transmeta.com.suse.lists.linux.kernel>
     [not found] ` <1036429035.1718.99.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2002-11-04 16:53   ` Andi Kleen
2002-11-04 12:34 Richard J Moore
     [not found] <551170412@toto.iv>
2002-11-04  3:03 ` Peter Chubb
2002-11-04 13:08   ` Alan Cox
2002-11-03 17:08 linux
2002-11-03 19:14 ` jw schultz
2002-11-03 13:48 Bill Davidsen
2002-11-04  2:44 ` [lkcd-general] " Jennie Haywood
2002-11-04 14:45   ` Henning P. Schmiedehausen
2002-11-04 15:29     ` Alan Cox
2002-11-04 15:27       ` Henning P. Schmiedehausen
2002-11-04 15:38         ` Patrick Finnegan
2002-11-04 16:51           ` Henning P. Schmiedehausen
2002-11-05  4:57     ` Werner Almesberger
2002-11-02 15:29 Alan Cox
2002-11-03  1:24 ` [lkcd-general] " Matt D. Robinson
2002-11-03  1:49   ` Alan Cox
2002-11-03 14:33     ` Bill Davidsen
2002-11-03 15:34       ` Bernd Eckenfels
2002-11-03 16:32       ` Alan Cox
2002-11-05 18:07         ` Bill Davidsen
2002-11-03  3:10   ` Christoph Hellwig
2002-10-31 22:47 Perez-Gonzalez, Inaky
2002-11-01 13:06 ` [lkcd-general] " Jan Iven
2002-10-31 22:20 Shawn
2002-10-31 23:14 ` [lkcd-general] " Bernhard Kaindl
2002-10-31 21:58 Richard J Moore
2002-10-31 15:46 Linus Torvalds
2002-10-31 17:55 ` [lkcd-general] " Dave Craft
2002-10-31 18:45   ` Patrick Mochel
2002-10-31 19:16     ` Stephen Hemminger
2002-10-31 19:57       ` george anzinger
2002-10-31 20:48         ` Stephen Hemminger

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=20021104122759.GG19368@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcd-devel@lists.sourceforge.net \
    --cc=lkcd-general-admin@lists.sourceforge.net \
    --cc=lkcd-general@lists.sourceforge.net \
    --cc=richardj_moore@uk.ibm.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

Powered by JetHome