> Hmm, the same happens for a pipe_read. In linux-2.0.x that one
> also returned immediatly (due to the check on 0 in sys_read).
> But an read of a pipe (0 bytes as count) still blocks...
>
> I'm nt sure what the proper semantics for the read call are.
> Shouldn't it at least be the same for all read's? pipe,
> tty, fs, network, unix?
OK, I'll take a look at the pipe code as well. I would think the read()
behavior should be consistent across all devices, but perhaps someone
else will explain otherwise.
Regards,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu