If program uses POSIX API, then there should be POSIX behaviour.
Meh, I was unclear. What I meant was that the translator can do whatever it wants to the file offset. Aslong as read/write/whatever work as expected.
One way to circumvent this is by declaring that this is socket, not file, so io_seek/lseek returns ESPIPE.
But then you loose some useful functionality, it should act as a normal file as much as possible.
POSIX read/write can't work as expected when filesystem changes file pointer at fs's own will.
Perhaps it's not explicitly stated in POSIX, but it's expected that noone except file descriptor's owner can change file pointer.
Regards, ogi
_______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-hurd
