On Tuesday 22 February 2005 11:59 pm, Michal wrote:
> This might well fix the bug that started this thread, but if so, mine
> was different. The UUID generator bug I am describing has been
> happening for the last couple of years, well before the UTF stuff.
> The scenario was always that all 4 bytes read from /dev/urandom
> appeared as nil, which caused a walkback. (As I said, cat/more/etc. on
> /dev/urandom unblocked it).
>
> The issue is moot however: since I the server has migrated, I haven't
> seen it happen (but I haven't had a rush of UUID creation either).

Yes, on thinking about it I realized that the symptom was wrong. Now, we could 
just test for nils (and keep trying?) but it seems like if we're allowed to 
open the device we should be allowed to read from it.

-- 
Ned Konz
http://bike-nomad.com/squeak/