From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: Sami Kerola <kerolasa@iki.fi>
Subject: [PATCH 2/2] man: use long options in text and add example to uuidgen
Date: Sun, 26 Nov 2017 17:27:21 +0000 [thread overview]
Message-ID: <20171126172721.9504-2-kerolasa@iki.fi> (raw)
In-Reply-To: <20171126172721.9504-1-kerolasa@iki.fi>
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
---
misc-utils/uuidgen.1 | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/misc-utils/uuidgen.1 b/misc-utils/uuidgen.1
index 4b0fcb60c..d5e1a5675 100644
--- a/misc-utils/uuidgen.1
+++ b/misc-utils/uuidgen.1
@@ -27,19 +27,19 @@ will generate a random-based UUID if a high-quality random number
generator is present. Otherwise, it will choose a time-based UUID.
It is possible to force the generation of one of these first two
UUID types by using the
-.B \-r
+.B \-\-random
or
-.B \-t
+.B \-\-time
options.
.PP
The third type of UUID is generated with the
-.B \-m
+.B \-\-md5
or
-.B \-s
-options (MD5 or SHA1, respectively), followed by
-.BR "\-n " \fInamespace
+.B \-\-sha1
+options, followed by
+\fB\-\-namespace\fR \fInamespace\fR
and
-.BR "\-N " \fIname\fR.
+\fB\-\-name\fR \fIname\fR.
The \fInamespace\fR may either be a well-known UUID, or else
an alias to one of the well-known UUIDs defined in RFC 4122, that is
.BR @dns ,
@@ -89,6 +89,8 @@ Generate the hash of the \fIname\fR.
Interpret name \fIname\fR as a hexidecimal string.
.SH "CONFORMING TO"
OSF DCE 1.1
+.SH EXAMPLES
+uuidgen \-\-sha1 \-\-namespace @dns \-\-name "www.example.com"
.SH AUTHOR
.B uuidgen
was written by Andreas Dilger for libuuid.
--
2.15.0
prev parent reply other threads:[~2017-11-26 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 17:27 [PATCH 1/2] misc: fix typos Sami Kerola
2017-11-26 17:27 ` Sami Kerola [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=20171126172721.9504-2-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).