Lennert Buytenhek wrote: > The problem is not that xdm doesn't check /dev/urandom first, the > problem is that it reads from /dev/mem _at all_. > > It is possible that checking /dev/urandom first masks the problem > in most configurations, but it doesn't solve it (if you don't have > /dev/random and /dev/urandom in your filesystem for whatever reason, > you still oops.) >
Right, but still, having a workaround when /dev/urandom exists is much better than having xdm broken on all arm. So, do you know if /dev/urandom is more often (always?) available on arm than /dev/random? What about the machine where you had the original bug? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]