>Another thing that strikes me as odd happens during the startup of
>X clients.  Shortly after looking at .Xauthority, they all seem to 
>issue a read() call on the descriptor they're using for network
>connectivity, and that call fails with EAGAIN (Resource temporarily
>unavailable).  This yields the following message:
>
>XIO:  fatal IO error 35 (No message of desired type) on X server ":0.0"
>      after 7 requests (6 known processed) with 0 events remaining.
>
>Is this the message NetBSD users are seeing when they start X clients?

No, I've always just gotten a simple "unable to connect to server" message.



<<<John>>>

"One World, One Web, One Program" - Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler