All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Kemp <dale@inet.net.nz>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] Re: IBM to release LVM Technology to the Linux
Date: Sat, 01 Jul 2000 09:30:01 +1200	[thread overview]
Message-ID: <395D1159.634DF7EB@inet.net.nz> (raw)
In-Reply-To: 8525690E.006AEE2B.00@d54mta02.raleigh.ibm.com

Ben,

I'm beginning to wonder why IBM is even on this list every suggestion is for
a pure LVMS solution. You say you care about LMS but everything shows that
IBM only wants there LVMS solution. I understand that LVMS has extra
functionality, I suspect it has many more years of development put into it
than LMS. I also think its a great idea for IBM to port, since its good for
your
existing users and maybe new ones too. The point I'm trying to make is why
not have some common standard here, even my proposal you answered,
"The LVMS already does what you are talking about ... integration occurs in
the LVMS instead of in the user interface, ...". Again that's not the point,
this
is a one eyed view once again. lvms, lvms, lvms... You suggest solutions and
they are "LVMS does this, LVMS does that".
Maybe IBM still doesn't get the working with the community idea here,
people on this list have been very open minded regards LVMS and generally
understand what you are trying to do, and are happy about LVMS coming to
Linux. But most of the list wants you to help expand Linux and understand
that they want you to help with it overall. Maybe some of that LVMS interface
could be used in LMS, or atleast give Linux a standard concept of a volume
.vs. a partition, even if all the insides of each piece are completely
different.
See if you can answer without saying LVMS does this... And we can tell users
in the future "integration occurs in the LVMS instead of the user interface".

-- Dale.

  reply	other threads:[~2000-06-30 21:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-30 19:27 [linux-lvm] Re: IBM to release LVM Technology to the Linux benr
2000-06-30 21:30 ` Dale Kemp [this message]
2000-06-30 23:05   ` Jens Benecke
  -- strict thread matches above, loose matches on Subject: below --
2000-06-30 20:50 benr
2000-06-30 20:28 benr
2000-06-30 20:53 ` Ragnar Kjørstad
2000-06-29 23:39 benr
2000-06-30  4:09 ` Dale Kemp
2000-06-30  9:34 ` Jan Niehusmann
2000-06-30 15:28 ` Ragnar Kjørstad
2000-06-29  5:32 Jean-Eric Cuendet
2000-06-29 10:49 ` Andi Kleen
2000-06-29  1:23 benr
2000-06-29 14:37 ` Ragnar Kjørstad
2000-06-26 21:44 benr
2000-06-27  3:53 ` Paul Jakma
2000-06-26 20:59 benr
2000-06-26 14:27 Wilson, Eric
2000-06-26 23:18 ` Dale Kemp
2000-06-27  2:02   ` Andi Kleen
2000-06-27  2:22     ` Dale Kemp
2000-06-27  2:13   ` Andreas Dilger
2000-06-23 21:04 benr
2000-06-23 23:49 ` Paul Jakma
2000-06-24  6:37   ` Dale Kemp
2000-06-24 18:07     ` S. Ryan Quick
2000-06-25  1:25       ` Dale Kemp
2000-06-26  6:31     ` Martin K. Petersen
2000-06-23 12:52 hpuxadm
2000-06-23 15:20 ` Jens Benecke
2000-06-22 19:37 benr
2000-06-23  1:23 ` Dale Kemp
2000-06-23 20:55 ` Martin K. Petersen
2000-06-21 22:27 benr
     [not found] <85256900.007B81E0.00@d54mta02.raleigh.ibm.com>
2000-06-18 22:51 ` Andreas Dilger
2000-06-21 17:28   ` Martin K. Petersen

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=395D1159.634DF7EB@inet.net.nz \
    --to=dale@inet.net.nz \
    --cc=linux-lvm@msede.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.