> But what for open64/read64/write64? None of them give the
> user a hint as to what the file pointer offset is. And we are
> still on a 32-bit system, with a 32-bit VM space, so writing
> 8GB in one go is not possible.
It is not guaranteed that a program which does use `read' will not
later use `lseek'. By returning an error as soon as possible strange
situation really no program is prepared for (read succeeds but one
cannot reset because lseek failed) cannot happen.
-- Uli
---------------. drepper@cygnus.com ,-. Rubensstrasse 5
Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany
Cygnus Solutions `--' drepper@gnu.ai.mit.edu `------------------------