I don't know why this is so.
But, notice that ftell(3) didn't report the correct file offset.
> I'm still puzzled why fseek doesn't work with read(2), as they both seem to be rather legacy functions of this kind.
There is some difference, fseek is a stream I/O function of C stdlib and lseek is the system call for seeking into a file. Maybe there are different DS in the kernel for them and perhaps they are not kept in sync? <guess/>
|