public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Brian Jackson <brian-kernel-list@mdrx.com>,
	linux-kernel@vger.kernel.org, evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: Linux v2.5.42
Date: Sun, 13 Oct 2002 22:55:07 -0600	[thread overview]
Message-ID: <20021014045507.GR3045@clusterfs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210131545510.17395-100000@coffee.psychology.mcmaster.ca>

On Oct 13, 2002  15:58 -0400, Mark Hahn wrote:
> > Yes I do realize that, but I think EVMS offers more in the long run
> > than any of the others.
> 
> for instance, some part of EVMS design is motivated by IBM's political
> desire to permit its bank customers, who have horrible old OS/2 systems,
> to transparently use OS/2 volumes.  it's not as if IBM couldn't provide
> a simple, user-level migration tool.

Well, you try and convert a few TB of data in a few hour outage window
and pray everything goes well (and then have to convert _back_ to the
old format once you find a bug in the new environment).  You have just
never worked in an environment where the time constraints are tight,
and you CANNOT do the migration offline, or in advance, or whatever.

> it's not as if the Linux community is going to rush out and say
> "let's all start use OS/2 volumes everywhere!"

Well, it's not like most of the Linux community is rushing out and saying
"let's all start using Amiga AFFS filesystems" either, but that didn't
prevent it from being included in the kernel.

I actually DO prefer AIX LVM metadata over the Linux LVM metadata,
and it is NO CONTEST when you are comparing it to the "DOS partitions"
that you seem to prefer so much.

> the best part of Linux is its willingness to throw out old designs;

The best part of Linux is that it accepts a lot of people into the fold,
each of whom has their own special needs, and can change it to meet
those needs.

> a big system like EVMS has its own resistance to such redesign.

???  A big system like the VM/VFS/networking/etc has its own resistance to
such redesign too, but that doesn't mean that they haven't been hacked and
diced and re-assembled like Frankenstein several times.  Everything has
to start somewhere, and if you want until everyone reaches "consensus"
on what is the "best" way to implement it, we would all still be running
MS DOS or Minix.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  parent reply	other threads:[~2002-10-14  4:51 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 17:14 Linux v2.5.42 Mark Peloquin
2002-10-12 19:34 ` Alan Cox
2002-10-12 19:37   ` jbradford
2002-10-13 23:55     ` Rob Landley
2002-10-13 12:41 ` [Evms-devel] " Michael Clark
2002-10-13 13:49   ` Christoph Hellwig
2002-10-13 15:16     ` Michael Clark
2002-10-13 15:35       ` Christoph Hellwig
2002-10-13 16:11         ` Brian Jackson
2002-10-13 16:26           ` Arjan van de Ven
2002-10-13 17:06             ` Brian Jackson
2002-10-13 19:58               ` Mark Hahn
2002-10-13 19:57                 ` Rik van Riel
2002-10-13 20:26                   ` Sean Neakums
2002-10-24 11:45                   ` Alexander Kellett
2002-10-13 19:59                 ` Andrew Morton
2002-10-13 20:24                 ` Bernd Eckenfels
2002-10-14 15:11                   ` Christoph Hellwig
2002-10-14 22:27                     ` Bernd Eckenfels
2002-10-14  4:55                 ` Andreas Dilger [this message]
2002-10-13 17:46           ` Robert Love
2002-10-13 18:34             ` Brian Jackson
2002-10-14  4:23             ` [Evms-devel] " Andreas Dilger
2002-10-14 16:08               ` Christoph Hellwig
2002-10-14 14:45           ` Christoph Hellwig
2002-10-13 16:18         ` [Evms-devel] " Michael Clark
2002-10-13 17:10           ` Alexander Viro
2002-10-13 17:41             ` Michael Clark
2002-10-14  4:43               ` Andreas Dilger
2002-10-14 16:16                 ` Christoph Hellwig
2002-10-14 15:21               ` Christoph Hellwig
2002-10-14 14:42             ` Shawn
2002-10-14 15:15           ` Christoph Hellwig
2002-10-14 14:20         ` Shawn
2002-10-14 16:15           ` Rik van Riel
2002-10-14 21:34             ` Shawn
2002-10-14 16:21           ` Christoph Hellwig
2002-10-14 16:38             ` Jeff Garzik
2002-10-14 21:47             ` Shawn
2002-10-15  7:42               ` Heinz J . Mauelshagen
2002-10-14 21:48             ` Oliver Neukum
2002-10-14 21:55               ` Shawn
2002-10-14 22:35                 ` Oliver Neukum
2002-10-14 22:53                   ` Shawn
2002-10-14 23:04                     ` Oliver Neukum
2002-10-14 23:16                       ` Alexander Viro
2002-10-14 23:30                         ` Oliver Neukum
2002-10-15  0:10                         ` Andrew Clausen
2002-10-14 22:57                   ` Alexander Viro
2002-10-13 13:41 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2002-10-14 23:57 [Evms-devel] " Mark Peloquin
2002-10-15 14:51 Steve Pratt
2002-10-15 21:18 ` Andrew Clausen

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=20021014045507.GR3045@clusterfs.com \
    --to=adilger@clusterfs.com \
    --cc=brian-kernel-list@mdrx.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.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