From: Niccolo Rigacci <niccolo@texnet.it>
To: linux-raid@vger.kernel.org
Subject: Forcing a more random uuid
Date: Tue, 1 Feb 2005 18:47:39 +0100 [thread overview]
Message-ID: <200502011847.39444.niccolo@texnet.it> (raw)
My previous post was answered very quickly and with an optimal solution,
but unfortunately I have a new question...
I'm writing a script to clone a disk with several md devices.
The raid1 volumes are created on the blank disk within a very quick loop, I
think this is the reason why I get /dev/md5, /dev/md6, /dev/md7
and /dev/md8 all with the same UUID!
Is there a way to force a more random UUID, or do I have to provide an
--uid option on the command line?
--
Niccolo Rigacci
http://www.texnet.it/
next reply other threads:[~2005-02-01 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 17:47 Niccolo Rigacci [this message]
2005-02-02 13:33 ` Forcing a more random uuid (random seed bug) Niccolo Rigacci
2005-02-22 23:55 ` H. Peter Anvin
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=200502011847.39444.niccolo@texnet.it \
--to=niccolo@texnet.it \
--cc=linux-raid@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).