From: Daniel Phillips <phillips@istop.com>
To: David Lang <dlang@digitalinsight.com>
Cc: Lars Marowsky-Bree <lmb@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] dlm: overview
Date: Fri, 29 Apr 2005 16:49:52 -0400 [thread overview]
Message-ID: <200504291649.52759.phillips@istop.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0504291011220.7439@qynat.qvtvafvgr.pbz>
On Friday 29 April 2005 13:13, David Lang wrote:
> On Thu, 28 Apr 2005, Daniel Phillips wrote:
> > On Thursday 28 April 2005 20:33, David Lang wrote:
> >> how is this UUID that doesn't need to be touched by an admin, and will
> >> always work in all possible networks (including insane things like
> >> backup servers configured with the same name and IP address as the
> >> primary with NAT between them to allow them to communicate) generated?
> >>
> >> there are a lot of software packages out there that could make use of
> >> this.
> >
> > Please do not argue that the 32 bit node ID ints should be changed to
> > uuids, please find another way to accommodate your uuids.
>
> you misunderstand my question.
>
> 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.
OK, that sound plausible. However, just to be 100% clear, do you agree that
a) simple integer node numbers are better (because simpler) in cman proper
and b) uuids can be layered on top of a simple integer scheme, using a pair
of mappings?
Regards,
Daniel
next prev parent reply other threads:[~2005-04-29 20:52 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 [this message]
2005-05-01 3:57 ` Theodore Ts'o
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=200504291649.52759.phillips@istop.com \
--to=phillips@istop.com \
--cc=dlang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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.