From: "Theodore Ts'o" <tytso@mit.edu>
To: David Lang <dlang@digitalinsight.com>
Cc: Daniel Phillips <phillips@istop.com>,
Lars Marowsky-Bree <lmb@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] dlm: overview
Date: Sat, 30 Apr 2005 23:57:47 -0400 [thread overview]
Message-ID: <20050501035746.GA6578@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0504291011220.7439@qynat.qvtvafvgr.pbz>
> the claim was that UUID's are unique and don't have to be assigned by the
> admins.
>
> I'm saying that in my experiance there isn't any standard or reliable way
> to generate such a UUID and I'm asking for the people makeing the
> claim to educate me on what I'm missing becouse a reliable UUID for linux
> on all hardware would be extremely useful for many things.
How to reliably generate universally unique ID's have been well
understood for over twenty years, and is implemented on nearly every
Linux system for over ten. For more information I refer you to
doc/draft-leach-uuid-guids-01.txt in the e2fsprogs sources, and for an
implementation, the uuid library in e2fsprogs, which is used by both
GNOME and KDE. UUID's are also used by Apple's Mac OS X (using
libuuid from e2fsprogs), Microsoft Windows, more historically by the
OSF DCE, and even more historically by the Apollo Domain OS (1980 --
1989, RIP). Much of this usage is due to the efforts of Paul Leach, a
key architect at Apollo, and OSF/DCE, before he left and joined the
Dark Side at Microsoft.
Also, FYI the OSF/DCE, including the specification for generating
UUID's, was submitted by OSF to the X/Open where it was standardized,
who in turn submitted it to the ISO where it was approved as
Publically Available Specification (PAS). So technically, there *is*
an internationally standardized way of generating UUID's, and it is
already implemented and deployed on nearly all Linux systems.
- Ted
next prev parent reply other threads:[~2005-05-01 3:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 15:11 [PATCH 0/7] dlm: overview David Teigland
2005-04-25 20:39 ` Wim Coekaerts
2005-04-25 21:09 ` Lars Marowsky-Bree
2005-04-26 5:30 ` Daniel Phillips
2005-04-27 13:56 ` Lars Marowsky-Bree
2005-04-27 20:00 ` Daniel Phillips
2005-04-27 20:20 ` Lars Marowsky-Bree
2005-04-27 22:38 ` Daniel Phillips
2005-04-28 14:57 ` Lars Marowsky-Bree
2005-04-28 20:53 ` Daniel Phillips
2005-04-29 0:33 ` David Lang
2005-04-29 1:49 ` Bernd Eckenfels
2005-04-29 1:52 ` Daniel Phillips
2005-04-29 17:13 ` David Lang
2005-04-29 20:49 ` Daniel Phillips
2005-05-01 3:57 ` Theodore Ts'o [this message]
2005-05-01 4:14 ` David Lang
2005-05-02 11:21 ` Lars Marowsky-Bree
2005-04-28 16:25 ` David Teigland
2005-04-28 16:42 ` Lars Marowsky-Bree
2005-04-29 4:24 ` Daniel Phillips
2005-04-25 21:19 ` Andrew Morton
2005-04-26 5:46 ` David Teigland
2005-04-26 5:39 ` David Teigland
2005-04-26 18:48 ` Mark Fasheh
2005-04-26 22:34 ` Steven Dake
2005-04-27 3:32 ` David Teigland
2005-04-27 13:23 ` Lars Marowsky-Bree
2005-04-27 18:12 ` Mark Fasheh
2005-04-28 14:36 ` Lars Marowsky-Bree
2005-04-28 17:35 ` Mark Fasheh
2005-04-28 12:50 ` Stephen C. Tweedie
2005-04-25 20:52 ` Daniel Phillips
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=20050501035746.GA6578@thunk.org \
--to=tytso@mit.edu \
--cc=dlang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=phillips@istop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox