From: k <shikam@yahoo.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM - History
Date: Thu, 22 Feb 2007 00:40:25 -0800 (PST) [thread overview]
Message-ID: <809419.63369.qm@web32913.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070221212318.GA8141@IUPUI.Edu>
Thaks for your help; my goal is to document LVM, from
an architecture, and source code point of views:
-The architecture will probably go back to 70�s or
early 80�s.
-The Source code will start from when LVM, started to
exist as an open source product (1998??) , and the
product that inspired the first release.
Do you know if IBM licensed, LVM to HP, and also
released it to the open source for linux developments?
Did Linux (Sistina) LVM derived from the IBM's LVM? Is
HP's LVM also drived from IBM's LVM?
Regards
Shikam
--- "Mark H. Wood" <mwood@IUPUI.Edu> wrote:
> Maybe you should define the scope of "LVM" for your
> purposes. The
> basic idea goes waaaaay back. Netware 4 had the
> ability to divvy up a
> partition, slice off pieces, and stick them together
> into one or more
> logical volumes. Most mainframe and mini OSes could
> at least paste
> multiple physical disk volumes together to form
> larger logical
> volumes. The ANSI X3.27 tape label standard from
> the 1970s or so (my
> copy is at home now) (last edition is from 1987)
> defines a way to do
> this with *open-reel tapes*.
>
> It's interesting to look at how the idea developed
> over time. Logical
> volume management started out as a way to make a
> single large logical
> volume out of multiple rather dinky physical
> volumes. Nowadays it's
> typically used in the opposite fashion: take a huge
> physical volume
> and carve it into multiple smaller logical volumes.
> You can still
> make logical volumes bigger than the biggest
> available physical
> volume, though, and there are sites which do. (I
> haven't needed that
> much storage in a single block address space since
> the 1990s, but YMMV.)
>
> --
> Mark H. Wood, Lead System Programmer
> mwood@IUPUI.Edu
> Typically when a software vendor says that a product
> is "intuitive" he
> means the exact opposite.
>
> > _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at
http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2007-02-22 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 3:23 [linux-lvm] LVM - History k
2007-02-21 16:53 ` Greg Freemyer
2007-02-21 17:26 ` Georges Giralt
2007-02-21 17:58 ` James Parsons
2007-02-21 21:23 ` Mark H. Wood
2007-02-22 8:40 ` k [this message]
2007-02-25 9:00 ` Luca Berra
2007-02-25 9:17 ` k
2007-02-25 10:14 ` Luca Berra
2007-02-25 22:55 ` k
2007-02-27 15:52 ` Greg Freemyer
2007-02-27 15:42 ` John Stoffel
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 15:13 Philip Wright
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=809419.63369.qm@web32913.mail.mud.yahoo.com \
--to=shikam@yahoo.com \
--cc=linux-lvm@redhat.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.