From: Ed Schouten <ed@FreeBSD.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Inconsistency between PTY read() return values
Date: Wed, 8 Apr 2009 19:56:03 +0200 [thread overview]
Message-ID: <20090408175603.GI32098@hoeg.nl> (raw)
In-Reply-To: <20090408174716.6474af70@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
Hi Alan,
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> I would argue that TTYs do behave this way. We treat the disconnect as a
> hang up event. BSD sees it as EOF, Linux as hangup.
Would you mind explaining me the difference? I thought a modem
disconnect implies an end-of-file condition? If you take the code I
mentioned and modify it to close the master device and perform a read on
the TTY, it will return 0.
--
Ed Schouten <ed@FreeBSD.org>
[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2009-04-08 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 14:36 Inconsistency between PTY read() return values Ed Schouten
2009-04-08 16:47 ` Alan Cox
2009-04-08 17:56 ` Ed Schouten [this message]
2009-04-08 18:09 ` Alan Cox
2009-04-08 18:22 ` Ed Schouten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090408175603.GI32098@hoeg.nl \
--to=ed@freebsd.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox