After that it's just down to using /dev/urandom[1] or the getrandom syscall (which is the same as using /dev/urandom). Also the getrandom syscall actually has the behavior you're talking about.
[1] http://sockpuppet.org/blog/2014/02/25/safely-generate-random...
mv /dev/random /dev/badrandom
ln -s /dev/random /dev/urandom # is this the right syntax?
Or something like that?1. http://superuser.com/questions/309840/how-can-i-point-dev-ra...
Edit: on boot, first prevent access to /dev/urandom, then symlink it to /dev/random. Then as soon as /dev/random stops blocking, reverse the direction of the symlink. Same improved security, much simpler to use.
1 - try to read from /dev/random.
2 - While 1 has not succeeded, wait and try again
3 - Once it has succeeded, read from /dev/urandom on next reads
There's no stealing with entropy. And once random returns a read the RNG is seeded, period.