> I am sorry, I actually meant io_read.
Ok.
> Ok, interesting. This is what the glibc manual said about this:
That's because I was wrong. :-) It's like I said, except that it should be
saved, yes.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://
Roland McGrath <[EMAIL PROTECTED]> writes:
>> Ok, interesting. This is what the glibc manual said about this:
>
> That's because I was wrong. :-) It's like I said, except that it should be
> saved, yes.
So O_NONBLOCK does not belong in OPENONLY_STATE_MODES?
Can this patch be applied?
Thanks,
Roland McGrath <[EMAIL PROTECTED]> writes:
> I'm not sure what you think O_NONBLOCK has to do with io_select.
> io_select's behavior should never be affected by nonblocking mode.
I am sorry, I actually meant io_read.
> The O_NONBLOCK flag bit is strangely overloaded (as specified in POSIX.1).
>
I'm not sure what you think O_NONBLOCK has to do with io_select.
io_select's behavior should never be affected by nonblocking mode.
The O_NONBLOCK flag bit is strangely overloaded (as specified in POSIX.1).
It is a state flag for an open file description (i.e. a peropen in our
implementations' dat
Marco Gerards <[EMAIL PROTECTED]> writes:
> After I couldn't get netfs_S_io_select working by overriding it for
> some translator I am writing I noticed that it is cleared when when
> the peropen structure is created.
This should be:
After I couldn't get netfs_S_io_select working by overriding i
Hi,
After I couldn't get netfs_S_io_select working by overriding it for
some translator I am writing I noticed that it is cleared when when
the peropen structure is created.
I think O_NONBLOCK does not belong in OPENONLY_STATE_MODES. First
because it is used after the node is opened. Another re
