Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Apr 2007 15:38:15 -0500
From:      "Ben Kaduk" <minimarmot@gmail.com>
To:        "Pawel Jakub Dawidek" <pjd@freebsd.org>
Cc:        freebsd-arch@freebsd.org
Subject:   Re: Host ID.
Message-ID:  <47d0403c0704091338p4c6476fey5d90e0dfb3a50cbf@mail.gmail.com>
In-Reply-To: <20070409190743.GL76673@garage.freebsd.pl>
References:  <20070407120656.GD63916@garage.freebsd.pl> <m264873tm7.wl%gnn@neville-neil.com> <20070408151358.GX63916@garage.freebsd.pl> <200704091335.42092.jkim@FreeBSD.org> <20070409190743.GL76673@garage.freebsd.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/9/07, Pawel Jakub Dawidek <pjd@freebsd.org> wrote:
> On Mon, Apr 09, 2007 at 01:35:39PM -0400, Jung-uk Kim wrote:
> > On Sunday 08 April 2007 11:13 am, Pawel Jakub Dawidek wrote:
[snip]
> > > I'd really like to make it simple and consistent on all archs, so
> > > one knows exactly what to expect.
> >
> > Agreed.  But I also agree with imp, i.e., we have to utilize hardware
> > UUID if it is available and valid for the platform.
>
> I don't agree. As Robert pointed out there are situation you would like
> to share the same UUID between many hosts.
>

This may be a bit pedantic, but I thought the case Robert described
was for a way to have an identical setup on many machines but still
allow for having a different UUID on each one.  That's not to say that
there aren't cases where you would want the same UUID on multiple
hosts, say, on redundant live spares, but I think that Robert's
example (as I am interpreting it) is a relatively common case.

-Ben Kaduk

> I'm committing as it is, we may change it in the future.
>
> --
> Pawel Jakub Dawidek                       http://www.wheel.pl
> pjd@FreeBSD.org                           http://www.FreeBSD.org
> FreeBSD committer                         Am I Evil? Yes, I Am!
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47d0403c0704091338p4c6476fey5d90e0dfb3a50cbf>