* Tim Kientzle <[EMAIL PROTECTED]> [070617 21:52] wrote:
>
> Note that the second call returns a new file position
> that's exactly 0x2f800 bytes beyond the former file
> position, even though nothing has actually happened.
>
> I think any of the following would be reasonable behaviors:
> * lseek() could return ESPIPE ("illegal seek")
> * lseek() could return an unchanged file offset
> (indicating that the file position was unchanged by
> the attempted seek).
> * lseek() could return ENOTSUP ("unsupported operation")
> As I said though, I just don't know that code well
> enough to propose a fix.
ENOTSUP seems to be the most "correct", although I sort of
see it being the equivelant of dispaching a sign saying
"bump" along the highway without actually fixing said
bump. :(
--
- Alfred Perlstein
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
