> > But as we all know, it is harder to remove a feature from Linux, than
> > to get the camel book through the eye of a needle (or something).
>
> It's possible that I'm too tired to have grasped this, but if I have,
> you're all wet. In all cases, read needs to return the number of bytes
> successfully moved. If you ask for N and 1/2 of the way through N you
> are going to get a fault, and you return SEGFAULT, now how can I ever
> find out that N/2 bytes actually made it out to me? I want to know that.
> If you are arguing that return N/2 is wrong, you are incorrect.
Imagine "I reallyu want to know how much memory memcpy() copied!". It is
as unreasonable as that.
Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/