History log of /freebsd-10.0-release/bin/uuidgen/
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
259065 07-Dec-2013 gjb

- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation


235842 23-May-2012 wblock

Mention the upper hard limit for -n option. Patch slightly modified
from PR version.

PR: 168255
Submitted by: Andy Kosela
Approved by: gjb
MFC after: 3 days


198148 15-Oct-2009 ru

Removed redundant WARNS setting.

Submitted by: Ulrich Spörlein


177151 13-Mar-2008 obrien

uuidgen has been repo-copied from usr.bin/ to bin/ to match its "new"
(2007/04/09) installation location.


168544 09-Apr-2007 pjd

Move uuidgen(1) from /usr/bin/ to /bin/. It will be used in rc.d/hostid
script, which will be executed before /usr/ mount.

Reviewed by: mlaier, rink, brooks, rwatson


149845 07-Sep-2005 rse

Mention that uuidgen(1) generates DCE version 1 UUIDs only


140368 17-Jan-2005 ru

Added the EXIT STATUS section where appropriate.


123258 07-Dec-2003 mux

The uuidgen(1) program is WARNS=6 clean, so flag it as such.

Tested on: i386, sparc64


115226 22-May-2003 ru

Erase whitspace at EOL.

Approved by: re (blanket)


112252 15-Mar-2003 marcel

Add an -o filename option to have the output written to a file.
This option is present on most uuidgen(1) implementations even
though normal file redirection can be used to achieve the same.

Submitted by: Hiten Pandya <hiten@unixdaemons.com>


106283 01-Nov-2002 marcel

o Remove $Id$ from copyright; there's $FreeBSD$,
o Remove static function uuid_print(); use uuid_to_string(3) in
combination with printf(3) to achieve the same,
o Remove unneeded includes,
o Add a reference to uuid(3) to the manpage.


97604 30-May-2002 ru

mdoc(7) police: kill hard sentence breaks.


97372 28-May-2002 marcel

Add uuidgen(2) and uuidgen(1).

The uuidgen command, by means of the uuidgen syscall, generates one
or more Universally Unique Identifiers compatible with OSF/DCE 1.1
version 1 UUIDs.

From the Perforce logs (change 11995):

Round of cleanups:
o Give uuidgen() the correct prototype in syscalls.master
o Define struct uuid according to DCE 1.1 in sys/uuid.h
o Use struct uuid instead of uuid_t. The latter is defined
in sys/uuid.h but should not be used in kernel land.
o Add snprintf_uuid(), printf_uuid() and sbuf_printf_uuid()
to kern_uuid.c for use in the kernel (currently geom_gpt.c).
o Rename the non-standard struct uuid in kern/kern_uuid.c
to struct uuid_private and give it a slightly better definition
for better byte-order handling. See below.
o In sys/gpt.h, fix the broken uuid definitions to match the now
compliant struct uuid definition. See below.
o In usr.bin/uuidgen/uuidgen.c catch up with struct uuid change.

A note about byte-order:
The standard failed to provide a non-conflicting and
unambiguous definition for the binary representation. My initial
implementation always wrote the timestamp as a 64-bit little-endian
(2s-complement) integral. The clock sequence was always written
as a 16-bit big-endian (2s-complement) integral. After a good
nights sleep and couple of Pan Galactic Gargle Blasters (not
necessarily in that order :-) I reread the spec and came to the
conclusion that the time fields are always written in the native
by order, provided the the low, mid and hi chopping still occurs.
The spec mentions that you "might need to swap bytes if you talk
to a machine that has a different byte-order". The clock sequence
is always written in big-endian order (as is the IEEE 802 address)
because its division is resulting in bytes, making the ordering
unambiguous.