From: Simon Derr <simon.derr@bull.net>
To: Yura Pakhuchiy <pakhuchiy@iptel.by>
Cc: Patrice Martinez <patrice.martinez@ext.bull.net>,
linux-kernel@vger.kernel.org
Subject: Re: /dev/random problem on 2.6.12-rc1
Date: Thu, 7 Apr 2005 17:36:59 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0504071727080.5654@localhost.localdomain> (raw)
In-Reply-To: <1112879666.2035.10.camel@chaos.void>
On Thu, 7 Apr 2005, Yura Pakhuchiy wrote:
> On Thu, 2005-04-07 at 14:40 +0200, Patrice Martinez wrote:
> > When using a machine with a 2612-rc 1kernel, I encounter problems
> > reading /dev/random:
> > it simply nevers returns anything, and the process is blocked in the
> > read...
> > The easiest way to see it is to type:
> > od < /dev/random
> >
> > Any idea?
>
> Because, /dev/random use user input, mouse movements and other things to
> generate next random number. Use /dev/urandom if you want version that
> will never block your machine.
>
> Read "man 4 random" for details.
>
Something changed since previous versions of the kernel, I guess.
Running `find /usr | wc' on a ssh session generates both network and disk
activity, and you should not expect any other kind of input on a networked
server.
Anyway, still zero bytes coming from /dev/random, for the few minutes I
waited.
This on Linux-2.6.12-rc-bk1, on IA64.
next prev parent reply other threads:[~2005-04-07 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 12:40 /dev/random problem on 2.6.12-rc1 Patrice Martinez
2005-04-07 13:08 ` Yura Pakhuchiy
2005-04-07 13:14 ` Yura Pakhuchiy
2005-04-07 15:36 ` Simon Derr [this message]
2005-04-07 21:12 ` Matt Mackall
2005-04-08 6:56 ` Simon Derr
2005-04-08 7:55 ` Matt Mackall
2005-04-08 12:12 ` buggy ia64_fls() ? (was Re: /dev/random problem on 2.6.12-rc1) Simon Derr
2005-04-08 16:27 ` Matt Mackall
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=Pine.LNX.4.58.0504071727080.5654@localhost.localdomain \
--to=simon.derr@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pakhuchiy@iptel.by \
--cc=patrice.martinez@ext.bull.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