From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: utils: use better wrappered random generator
Date: Wed, 25 May 2016 19:19:11 +0000 (UTC) [thread overview]
Message-ID: <pan$bb742$78566cd9$5fc9402d$3fb62a5@cox.net> (raw)
In-Reply-To: 5d14ab66-9894-82da-91ca-5cbfd0a7d760@gmail.com
Austin S. Hemmelgarn posted on Wed, 25 May 2016 08:39:08 -0400 as
excerpted:
> I would tend to agree with Hugo on this one, we should be using
> /dev/urandom, not /dev/random.
Add me to the list. I was wondering where urandom was in the discussion
all along, but figured there must be some reason it was excluded that I
as a non-dev simply didn't grok.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-05-25 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 3:10 [PATCH] btrfs-progs: utils: use better wrappered random generator Qu Wenruo
2016-05-23 12:01 ` David Sterba
2016-05-24 0:31 ` Qu Wenruo
2016-05-24 9:51 ` David Sterba
2016-05-25 0:33 ` Qu Wenruo
2016-05-25 11:11 ` David Sterba
2016-05-25 11:20 ` Hugo Mills
2016-05-25 12:39 ` Austin S. Hemmelgarn
2016-05-25 19:19 ` Duncan [this message]
2016-05-26 0:27 ` Qu Wenruo
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='pan$bb742$78566cd9$5fc9402d$3fb62a5@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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