Date: Tue, 10 Sep 2002 20:30:12 -0400 From: Mike Barcroft <mike@FreeBSD.org> To: Bakul Shah <bakul@bitblocks.com> Cc: Archie Cobbs <archie@dellroad.org>, freebsd-arch@FreeBSD.ORG Subject: Re: /dev/stdout behavior Message-ID: <20020910203012.E40217@espresso.q9media.com> In-Reply-To: <200209102200.SAA07377@thunderer.cnchost.com>; from bakul@bitblocks.com on Tue, Sep 10, 2002 at 03:00:04PM -0700 References: <200209102135.g8ALZXm34757@arch20m.dellroad.org> <200209102200.SAA07377@thunderer.cnchost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bakul Shah <bakul@bitblocks.com> writes: > > > You need to fix your test program similarly and run it under > > > Linux to see if the two OSes behave differently. > > > > They do behave differently, even after adjusting '0' to '1': > > > > $ uname -a > > Linux foobar.packetdesign.com 2.4.9 #19 SMP Mon Oct 29 11:55:31 PST 2001 > > i686 unknown > > $ ./flags > > O_NONBLOCK is not set > > Hmmm... are /dev/stdin etc. part of Posix? If not, linux can > do what it wants. POSIX specifies three special files: /dev/null, /dev/tty, and /dev/console. So the answer is no. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020910203012.E40217>