public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: Stephen Lord <lord@sgi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: XFS in the main kernel
Date: Tue, 23 Apr 2002 17:47:01 +0200	[thread overview]
Message-ID: <3CC581F5.2FBEA0C1@TeraPort.de> (raw)
In-Reply-To: <3CC56355.E5086E46@TeraPort.de> <3CC56FE9.1080303@sgi.com>

Stephen Lord wrote:
> 
> Martin Knoblauch wrote:
> 
> >
> > definitely. Unless XFS is in the mainline kernel (marked as
> >experimantal if necessary) it will not get good exposure.
> >
> > The most important (only) reason I do not use it (and recommend our
> >customers against using it) is that at the moment it is impossible to
> >track both the kernel and XFS at the same time. This is a shame, because
> >I think that for some application XFS is superior to the other
> >alternatives (can be said about the other alternatives to :-).
> >
> 
> You would be surprised about the level of exposure XFS is getting, a lot
> more
> than you might realize. It is in everything from settop boxes and fiber
> channel
> switches to NAS boxes, those folks in general do not want to advertise.
> Here are
> a few larger scale installations out there:
> 
> http://oss.sgi.com/projects/xfs/xfs_users.html
> 
> Steve
Steve,

 no question that those are seriour users that give you serious
feedback. And if you call that
exposure, I am not going to argue. It is your project, it is your
marketing. (And *I* am not going to argue about SGI marketing :-(

 From a mainline point of view XFS on Linux will only be successfull if
it is "in the kernel". Fully maintained and "Linus approved". I am not
sure when SGI started the port (could even go back to the time when I
worked for them, late 1997). Definitely quite some time. By now it
should be in the kernel. Maybe marked "experimental". As I see it now
EXT3, ReiserFS and maybe JFS are just eating the XFS lunch away.

 In any case, the Vanderbilt comment is right on.

Martin
-- 
------------------------------------------------------------------
Martin Knoblauch         |    email:  Martin.Knoblauch@TeraPort.de
TeraPort GmbH            |    Phone:  +49-89-510857-309
C+ITS                    |    Fax:    +49-89-510857-111
http://www.teraport.de   |    Mobile: +49-170-4904759

  reply	other threads:[~2002-04-23 15:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 13:36 XFS in the main kernel Martin Knoblauch
2002-04-23 14:30 ` Stephen Lord
2002-04-23 15:47   ` Martin Knoblauch [this message]
2002-04-23 21:37     ` J.A. Magallon
2002-04-23  9:23       ` Daniel Phillips
2002-04-24  9:32         ` Luigi Genoni
2002-04-23 15:47 ` Peter Wächtler
2002-04-23 15:55   ` Martin Knoblauch
2002-04-23 21:43 ` Luigi Genoni
2002-04-23  9:32   ` Daniel Phillips
2002-04-24  7:13   ` Martin Knoblauch
2002-04-24  9:02     ` Luigi Genoni
     [not found] <20020422234419.GQ2470@dstl.gov.uk>
2002-04-23  8:31 ` Tony Gale
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 15:10 Dan Yocum
2002-04-21 15:29 ` Daniel Phillips
2002-04-22 16:55 ` Wichert Akkerman
2002-04-22 22:19   ` Matthias Andree
2002-04-22 22:47     ` Chris Mason
2002-04-22 23:29   ` Keith Owens
2002-04-22 23:44     ` Wichert Akkerman
2002-04-23  0:43     ` Luigi Genoni

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=3CC581F5.2FBEA0C1@TeraPort.de \
    --to=martin.knoblauch@teraport.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.com \
    --cc=m.knoblauch@TeraPort.de \
    /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