From: Jeff Dike <jdike@addtoit.com>
To: Sven 'Darkman' Michels <sven@darkman.de>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] /dev/random oddity
Date: Mon, 15 Mar 2004 14:41:14 -0500 [thread overview]
Message-ID: <20040315194114.GE23741@ccure.user-mode-linux.org> (raw)
In-Reply-To: <405309FE.6020603@darkman.de>
On Sat, Mar 13, 2004 at 02:17:50PM +0100, Sven 'Darkman' Michels wrote:
> never is wrong, you can 'fill' the pool by doing some work like find /
> ps aux etc, but this is really slow in filling up the pool. Maybe
> other things should be used to fill the pool, too. Jeff? Blaisor?
> anyone? ;)
That doesn't fill the random pool directly. What it does do is cause disk
IO, and the ubd driver will refill the random pool. It's a bit heavy-weight
for generating randomness, and I don't really like it anyway. See my other
reply in this thread.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-03-15 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 1:49 [uml-devel] /dev/random oddity Thomas Schwinge
2004-03-13 13:17 ` Sven 'Darkman' Michels
2004-03-13 15:12 ` Stephen D. Williams
2004-03-14 22:40 ` Matt Zimmerman
2004-03-15 19:37 ` Jeff Dike
[not found] ` <Pine.LNX.4.58.0403151422320.13832@gradall.private.brainfood.com>
2004-03-15 21:16 ` Jeff Dike
2004-03-18 19:06 ` BlaisorBlade
2004-03-15 19:41 ` Jeff Dike [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=20040315194114.GE23741@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=sven@darkman.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.