On Sat, Jul 24, 2010 at 09:20:09AM -0300, Henrique de Moraes Holschuh wrote: > On Sat, 24 Jul 2010, Mario 'BitKoenig' Holbe wrote: > > the rng-tools init-script should depend on the start of the sysfsutils > > init-script: > No. sysfsutils starts too late for my tastes. The right way to deal with > this would actually to hook to udev and select the preferred rng as soon as > it becomes available.
Hmmm, nice idea, but I have no idea how to do it. I tried to search
through the udev database (udevadm info --export-db) to find a way to
hook the loading of via-rng but found no entry for it (quite expected:
it has no own device or sysfs entry). The only thing I found was the
record for hwrng, but this, of course, appears as soon as the first RNG
loads.
> OTOH, I have nothing against adding support for this feature to rng-tools
> itself, which looks like a simple way to solve both problems.
This would also be fine for me :)
> This is just a kernel interface shortcoming. We really should have a way
> for the RNG core to select the highest preference HWRNG (which would be the
> VIA Padlock one, as it is *FAST*, can generate very high quality random
Well, I started a thread on the LKML:
From: "Mario 'BitKoenig' Holbe" <[email protected]>
Subject: b43 wireless driver inhibits access to /dev/hwrng
Message-ID: <[email protected]>
Currently, it's a two-man-show between John (wlan guy) and me. If you
like - comment it, probably change the subject, because "changing rng
core" is more or less the way it currently walks :)
regards
Mario
--
Whenever you design a better fool-proof software,
the genetic pool will always design a better fool.
signature.asc
Description: Digital signature
