On 4/10/14, Bob Beck b...@openbsdfoundation.org wrote:
The Foundation will continue to strive to improve its financial
resources, and hopes to be able to provide further support to the
projects in the future. Please continue to contribute!
Where can I read your financial reports?
On 4/4/14, Philip Guenther guent...@gmail.com wrote:
The original poster has already be pointed to the POSIX spec and had
it explained that OpenBSD won't be changing this behavior as long as
it's in POSIX.
I didn't ask OpenBSD for code. OpenBSD management seems defensive,
perhaps paranoid,
On 4/4/14, Steve Williams st...@williamsitconsulting.com wrote:
The POSIX writers erred by making VTIME an interbyte timer.
What real life problem are you trying to solve?
Theory of operation.
Why do you need to have 250 bytes in the returned buffer?
Same principle as a 16550 UART FIFO
On 4/4/14, John D. Verne john.ve...@gmail.com wrote:
The meaning of VMIN, VTIME change depending on if they are non-zero or not.
VTIME is not always an inter-character timer
I know.
but they way you are using it, it is.
Yes, POSIX case A: MIN0 and TIME0.
Case B, MIN0 and TIME=0, is
On 4/2/14, Mihai Popescu mih...@gmail.com wrote:
Dude, what the hell are you trying to do? Just explain in plain words here.
I am interested in working with rs232
and i wasted my time reading and wainting for your damn problem.
a) Set raw mode.
b) Set VMIN = 250 and VTIME = 1.
c) Set port
On stackoverflow I said:
http://stackoverflow.com/questions/20154157/termios-vmin-vtime-and-blocking-non-blocking-read-operations/22771908#22771908
Any thoughts on fixing the design, in favor or opposed?
On Mon, Mar 31, 2014 at 11:17 PM, Philip Guenther guent...@gmail.com wrote:
You haven't convinced me the design needs fixing, nor have you proved
that the goal that you (sorta) describe can't already be solved with
the existing APIs.
What problem are you trying to solve?
a) set VMIN = 250;
On Mon, Mar 31, 2014 at 11:52 PM, Theo de Raadt dera...@cvs.openbsd.org wrote:
In the future, please submit concise reports rather than a link to
something vague which is part of a long conversation on some site out
there. It will indicate you are serious.
I may do that.
Perhaps VMIN and
On Tue, Apr 1, 2014 at 12:23 AM, Philip Guenther guent...@gmail.com wrote:
I *sounds* like the problem you're trying to solve** is some thing like
I want to efficiently read data from a serial line, returning
whenever at least
250 bytes are available or when more then 0.1s has
On Tue, Apr 1, 2014 at 1:18 AM, Theo de Raadt dera...@cvs.openbsd.org wrote:
Are you saying OpenBSD does it wrong, or that all the operating systems
do it wrong?
I tested Linux and OpenBSD. Both wrong.
The termios man pages from NetBSD and FreeBSD are identical to
OpenBSD. So I expect they're
On Tue, Apr 1, 2014 at 1:39 AM, Theo de Raadt dera...@cvs.openbsd.org wrote:
I suspect they all follow an official specification. Careful test code
compared to the specification would decide.
It might show them all to be right, leaving the obvious conclusion about
who is wrong.
To test it,
On Tue, Apr 1, 2014 at 2:39 AM, Philip Guenther guent...@gmail.com wrote:
Your question is why haven't OS developers done what I think is
right?
The answer to that question is because the POSIX standard says we
shouldn't, and is quite clear about this.
Show me where POSIX says VTIME must be
On Tue, Apr 1, 2014 at 2:12 AM, Theo de Raadt dera...@cvs.openbsd.org wrote:
your cute little nickname should have hinted that you don't have a
mature understanding of the world.
Thanks for the psychoanalysis, doctor. Is your advice free, or do you
charge for it?
On Tue, Apr 1, 2014 at 3:00 AM, Philip Guenther guent...@gmail.com wrote:
Show me where POSIX says VTIME must be an interbyte timer.
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap11.html#tag_11_01_07
I missed that during my search. POSIX says so. OK.
And you *still*
On Tue, Apr 1, 2014 at 3:37 AM, Philip Guenther guent...@gmail.com wrote:
you stated that my description was wrong and not what you were
looking for on at least one point of behavior.
If by that, you mean this:
If no data is received, it should still return after 0.1s.
No, read() should
15 matches
Mail list logo
