>> That's quite bizarre.  Something _somewhere_ along the line is
>> returning EIO.
> You are sure that this message is only generated for EIO?

AFAIK, yes.

> I only added printf statements were I found "return EIO;" or
> something like that.

Well, jtk said something about having found and fixed a probable
culprit, so it's likely moot...but it could also be wherever it passes
back an error generated by some other call, as in
	error = some_call(one_thing,another_thing,etc...);
	if (error) return(error);

>> Define "broken", then.  [...] (Just as obviously not completely
>> working, either.)
> "Not completely working" means "broken" for me (no offence intended).

In that case, you will probably be quite unhappy with NetBSD...and
indeed equally so with (almost?) every other OS.  There isn't very much
that I, at least, feel sure is completely working; the really simple
things, like "yes" and "true", are the places I would look if I were
looking for code I could hold up as a bug-free part of NetBSD.  Even
basic utilities like ls probably still harbor at least one bug.

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu