Problems emerge for a unified /dev/*random

> A more insidious problem, perhaps, is that a seed written to the RNG before it initializes will not actually be used until after the pool is initialized properly; "you might write in a perfectly good seed to /dev/urandom, but what you read out for the subsequent seed may be complete deterministic crap"

This has been noticed on StackExchange it seems https://security.stackexchange.com/questions/183506/rando...