Date: Thu, 7 Apr 2005 17:36:59 +0200 (CEST)
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
In-Reply-To: <1112879666.2035.10.camel@chaos.void>
Message-ID: <Pine.LNX.4.58.0504071727080.5654@localhost.localdomain>
References: <42552A33.6070704@ext.bull.net> <1112879666.2035.10.camel@chaos.void>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1183
Lines: 37


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.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/