From: Jeff Dike <jdike@addtoit.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] /dev/random oddity
Date: Mon, 15 Mar 2004 14:37:08 -0500 [thread overview]
Message-ID: <20040315193708.GD23741@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20040314224008.GY28592@alcor.net>
On Sun, Mar 14, 2004 at 02:40:08PM -0800, Matt Zimmerman wrote:
> 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.
That could be done. it would require replacing the generic /dev/random with
a UML one, and I don't know whether the kernel build makes that easy.
Another alternative is to add an mconsole interface to dump randomness into
a UML when it starts running out.
The current UML practice of feeding /dev/random from the drivers is a bit
suspect. The randomness obtained there is related to the host randomness,
but the host random pool isn't depleted accordingly.
I think the right solution is to feed UML /dev/random from the host /dev/random
somehow.
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
next prev parent reply other threads:[~2004-03-15 19:03 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 [this message]
[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=20040315193708.GD23741@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox