1 .\" $NetBSD: uuidgen.2,v 1.4 2005/01/30 18:13:04 jwise Exp $
2 .\" $FreeBSD: src/lib/libc/sys/uuidgen.2,v 1.7 2003/06/27 13:41:29 yar Exp $
3 .\" Copyright (c) 2002 Marcel Moolenaar
4 .\" All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
16 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
17 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
18 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
19 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
20 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
21 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
22 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
23 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
24 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
25 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
27 .\" $FreeBSD: src/lib/libc/sys/uuidgen.2,v 1.7 2003/06/27 13:41:29 yar Exp $
34 .Nd generate universally unique identifiers
41 .Fn uuidgen "struct uuid *store" "int count"
47 universally unique identifiers (UUIDs) and writes them to the buffer
50 The identifiers are generated according to the syntax and semantics of the
51 DCE version 1 variant of universally unique identifiers.
52 See below for a more in-depth description of the identifiers.
54 address is available for the node field, a random multi-cast address is
55 generated for each invocation of the system call.
56 According to the algorithm of generating time-based UUIDs, this will also
57 force a new random clock sequence, thereby increasing the likelihood for
58 the identifier to be unique.
60 When multiple identifiers are to be generated, the
62 system call will generate a set of identifiers that is dense in such a way
63 that there is no identifier that is larger than the smallest identifier in the
64 set and smaller than the largest identifier in the set and that is not already
67 Universally unique identifiers, also known as globally unique identifiers
68 (GUIDs), have a binary representation of 128-bits.
69 The grouping and meaning of these bits is described by the following
70 structure and its description of the fields that follow it:
75 uint16_t time_hi_and_version;
76 uint8_t clock_seq_hi_and_reserved;
77 uint8_t clock_seq_low;
78 uint8_t node[_UUID_NODE_LEN];
81 .Bl -tag -width ".Va clock_seq_hi_and_reserved"
83 The least significant 32 bits of a 60-bit timestamp.
84 This field is stored in the native byte-order.
86 The least significant 16 bits of the most significant 28 bits of the 60-bit
88 This field is stored in the native byte-order.
89 .It Va time_hi_and_version
90 The most significant 12 bits of the 60-bit timestamp multiplexed with a 4-bit
92 The version number is stored in the most significant 4 bits of the 16-bit
94 This field is stored in the native byte-order.
95 .It Va clock_seq_hi_and_reserved
96 The most significant 6 bits of a 14-bit sequence number multiplexed with a
98 Note that the width of the variant value is determined by the variant itself.
99 Identifiers generated by the
101 system call have variant value 10b.
102 the variant value is stored in the most significant bits of the field.
104 The least significant 8 bits of a 14-bit sequence number.
106 The 6-byte IEEE 802 (MAC) address of one of the interfaces of the node.
107 If no such interface exists, a random multi-cast address is used instead.
110 The binary representation is sensitive to byte ordering.
111 Any multi-byte field is to be stored in the local or native byte-order and
112 identifiers must be converted when transmitted to hosts that do not agree
114 The specification does not however document what this means in concrete
115 terms and is otherwise beyond the scope of this system call.
121 system call can fail with:
124 The buffer pointed to by
126 could not be written to for any or all identifiers.
130 argument is less than 1 or larger than the hard upper limit of 2048.
136 The identifiers are represented and generated in conformance with the DCE 1.1
140 system call is itself not part of the specification.
144 system call first appeared in
146 and was subsequently added to