From: "Ralf S. Engelschall" <rse@engelschall.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM UUIDs are not UUIDs!?
Date: Thu, 23 Sep 2004 19:53:22 +0200 [thread overview]
Message-ID: <20040923175322.GA6110@engelschall.com> (raw)
In-Reply-To: <1095959414.26438.27.camel@tesuji.nac.uci.edu>
On Thu, Sep 23, 2004, Dan Stromberg wrote:
> Same in concept, different implementation, easier to use?
>
> The Lustre does the same thing: It has what it calls UUID's, that are
> actually more descriptive strings than what the standard calls for.
> [...]
Well, it's 100% ok if one implements own ids with more descriptive
strings which are not conforming to the UUID or any other id standard.
My only concern is that then the result should be better not named UUID
because that's already (since many years) the official name of the
ids from DCE 1.1 and ISO/IEC 11578:1996. It is like using an object
addressing scheme producing strings like "foo!bar!quux" but calling
them "URLs"... ;-)
Ralf S. Engelschall
rse@engelschall.com
www.engelschall.com
next prev parent reply other threads:[~2004-09-23 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 8:47 [linux-lvm] LVM UUIDs are not UUIDs!? Ralf S. Engelschall
2004-09-23 17:10 ` Dan Stromberg
2004-09-23 17:53 ` Ralf S. Engelschall [this message]
2004-09-25 16:41 ` Alasdair G Kergon
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=20040923175322.GA6110@engelschall.com \
--to=rse@engelschall.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.