[Solved] Problem during trunk installation

[zpin]

Sure, but that wasn't the point. The urandom number is as good as impossible to predict it in practice and during the installation it's - afaik - only used for the pma blowfish secret. I'm not sure but I think urandom also uses the kernel entropy, but if it runs out it falls back to another mechanism.
So anyway, this is a frequent issue and something needs to be done about it.
My suggestions:
a) Use urandom (or perl rand) in "make install" and state the remotely existant security issue with pma cookies
b) Print a clearly visible notice before the last step in "make install" that informs the user about the possible delay and how to circumvent it.
c) Add a timeout to the /dev/random read and try to generate entropy if reached.