summaryrefslogtreecommitdiff
path: root/man/sd_id128_randomize.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2021-06-15 17:55:17 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-06-15 20:58:56 +0200
commit39d02a175f08c8cc9e4507e1abce26912d00fac3 (patch)
treeccdc51852d56613ef11bdc2c3a999656e35189b4 /man/sd_id128_randomize.xml
parent9b682672e4b21e6325b48da3dcca4b4a479378a6 (diff)
downloadsystemd-39d02a175f08c8cc9e4507e1abce26912d00fac3.tar.gz
sd-id128: document everywhere that we treat all UUIDs as Variant 1
So in theory UUID Variant 2 (i.e. microsoft GUIDs) are supposed to be displayed in native endian. That is of course a bad idea, and Linux userspace generally didn't implement that, i.e. uuidd and similar. Hence, let's not bother either, but let's document that we treat everything the same as Variant 1, even if it declares something else.
Diffstat (limited to 'man/sd_id128_randomize.xml')
-rw-r--r--man/sd_id128_randomize.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/man/sd_id128_randomize.xml b/man/sd_id128_randomize.xml
index 0bc1d0abd8..52fa089ec3 100644
--- a/man/sd_id128_randomize.xml
+++ b/man/sd_id128_randomize.xml
@@ -42,9 +42,9 @@
<filename>/dev/urandom</filename> kernel random number
generator.</para>
- <para>Note that <function>sd_id128_randomize()</function> always returns a UUID v4-compatible ID. It is
- hence guaranteed that this function will never return the ID consisting of all zero or all one bits
- (<constant>SD_ID128_NULL</constant>, <constant>SD_ID128_ALLF</constant>).</para>
+ <para>Note that <function>sd_id128_randomize()</function> always returns a UUID Variant 1 Version 4
+ compatible ID. It is hence guaranteed that this function will never return the ID consisting of all zero
+ or all one bits (<constant>SD_ID128_NULL</constant>, <constant>SD_ID128_ALLF</constant>).</para>
<para>For more information about the <literal>sd_id128_t</literal>
type, see