From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] /dev/random oddity
Date: Sun, 14 Mar 2004 14:40:08 -0800 [thread overview]
Message-ID: <20040314224008.GY28592@alcor.net> (raw)
In-Reply-To: <405324DB.3030404@lig.net>
On Sat, Mar 13, 2004 at 10:12:27AM -0500, Stephen D. Williams wrote:
> This is a bit beyond our scope here, but one ideal source for randomness
> is LavaRnd: http://www.lavarnd.org/
LavaRnd is software, and like any other software cannot be a source of
entropy. From reading the web page, it seems to rely on hardware to import
entropy from an external source, which is less than ideal for use with UML.
If the host has a steady supply of randomness from any source, then UML
should be able to simply read from /dev/random on the host.
--
- mdz
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-14 22:40 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 [this message]
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
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=20040314224008.GY28592@alcor.net \
--to=mdz@debian.org \
--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.