Re: Forcing a more random uuid (random seed bug)

2005-02-22 Thread H. Peter Anvin
Followup to: [EMAIL PROTECTED] By author:Niccolo Rigacci [EMAIL PROTECTED] In newsgroup: linux.dev.raid I get /dev/md5, /dev/md6, /dev/md7 and /dev/md8 all with the same UUID! It seems that there is a bug in mdadm: when generating the UUID for a volume, the random() function is

Re: Forcing a more random uuid (random seed bug)

2005-02-22 Thread H. Peter Anvin
Followup to: [EMAIL PROTECTED] By author:[EMAIL PROTECTED] In newsgroup: linux.dev.raid +if ((my_fd = open(/dev/random, O_RDONLY)) != -1) { Please use /dev/urandom for such applications. /dev/random is the highest-quality generator, but will block if entropy isn't available.

Re: Forcing a more random uuid (random seed bug)

2005-02-02 Thread Niccolo Rigacci
I get /dev/md5, /dev/md6, /dev/md7 and /dev/md8 all with the same UUID! It seems that there is a bug in mdadm: when generating the UUID for a volume, the random() function is called, but the random sequence is never initialized. The result is that every volume created with mdadm has an uuid