From: "Theodore Ts'o" <tytso@mit.edu>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] sysctl: introduce uuid_le and uuid_be
Date: Tue, 24 May 2016 18:56:59 -0400 [thread overview]
Message-ID: <20160524225659.GA387@thunk.org> (raw)
In-Reply-To: <1464121530.31269.86.camel@linux.intel.com>
I'm also curious what !@#!? idiot came up with the concept of Little
Endian UUID's. UUID's, and how to transform them from a printed
representation to a binary presentation, were well defined in a very
specific way in RFC-4122, which came from HP's Apollo/Domain OS, and
was adopted by the OSF/DCE, as well as later by Microsoft. In all
cases, there was never any such thing as little endian versus big
endian UUID's. Might as well talk about big-endian and little endian
IP addresses. This way lies madness.
It's also the case that if all you need is a random UUID's, that
*technically* the endianness matters, but in actual practice, it
really won't matter.
- Ted
P.S. Let me guess, it was some clueless Intel engineer when they were
drafting the EFI spec? Sigh....
prev parent reply other threads:[~2016-05-26 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 17:27 [PATCH v1 1/1] sysctl: introduce uuid_le and uuid_be Andy Shevchenko
2016-05-24 20:15 ` Andrew Morton
2016-05-24 20:25 ` Andy Shevchenko
2016-05-24 22:56 ` Theodore Ts'o [this message]
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=20160524225659.GA387@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
/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