From: Robert Love <rml@tech9.net>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: user-mode port 0.56-2.4.18-15
Date: 08 Apr 2002 16:02:48 -0400 [thread overview]
Message-ID: <1018296173.913.162.camel@phantasy> (raw)
In-Reply-To: <200204082056.PAA03749@ccure.karaya.com>
On Mon, 2002-04-08 at 16:56, Jeff Dike wrote:
> Added SA_SAMPLE_RANDOM to the irq registration flags of some drivers. This
> makes apps which read /dev/random work a lot better. Randomness in UML is
> more problematic than on the host, but I chose a set of drivers whose
> interrupts shouldn't be too predictable.
If these drivers truly are sufficient candidates for feeding
/dev/random, perhaps you could pull these bits and submit them to Linus
and Marcelo?
I for one think this is a good idea.
Robert Love
next prev parent reply other threads:[~2002-04-08 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 20:56 user-mode port 0.56-2.4.18-15 Jeff Dike
2002-04-08 1:25 ` Pavel Machek
2002-04-09 23:16 ` Jeff Dike
2002-04-09 22:17 ` Pavel Machek
2002-04-10 1:44 ` Jeff Dike
2002-04-10 3:53 ` [uml-user] " Andreas Dilger
2002-04-10 21:14 ` David Wagner
2002-04-08 20:02 ` Robert Love [this message]
2002-04-08 23:09 ` 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=1018296173.913.162.camel@phantasy \
--to=rml@tech9.net \
--cc=jdike@karaya.com \
--cc=linux-kernel@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