From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Zack Weinberg <zackw@panix.com>,
Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>,
Florian Weimer <fweimer@redhat.com>,
linux-man <linux-man@vger.kernel.org>,
GNU C Library <libc-alpha@sourceware.org>,
larryd.kbd@gmail.com, gwc@opengroup.org,
austin-group-l@opengroup.org, ajosey@opengroup.org,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
enh@google.com, Joseph Myers <joseph@codesourcery.com>
Subject: Re: Pseudoterminal terminology in POSIX
Date: Mon, 10 Aug 2020 20:21:21 +0200 [thread overview]
Message-ID: <20200810182121.msb7mngurj653cau@function> (raw)
In-Reply-To: <20200810181753.pkoqpkd3k54b6rfj@function>
Samuel Thibault, le lun. 10 août 2020 20:17:53 +0200, a ecrit:
> Zack Weinberg, le lun. 10 août 2020 14:10:42 -0400, a ecrit:
> > "control(ler) side" still gives the wrong impression IMNSHO. The
> > pty[p-r][0-9a-f] | ptmx devices don't exert any actual control over
> > anything.
>
> ? They do to some extent: writing ^C on that side will send a SIGINT to
> the foreground process there (even if owned by another user!).
Unless they opened it with O_NOCTTY to avoid letting it be their
"controlling terminal". There really is some "control" terminology here,
which is initiated by the pty side.
Samuel
next prev parent reply other threads:[~2020-08-10 18:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 11:21 Pseudoterminal terminology in POSIX Michael Kerrisk
2020-08-05 13:51 ` Steffen Nurpmeso
[not found] ` <20200805142049.GA17848@localhost>
2020-08-05 20:34 ` Michael Kerrisk (man-pages)
[not found] ` <CAP1RCkjrqKGJmh6f637D=yGuhev7ae5QJkMjv5a8iHo4X33NFw@mail.gmail.com>
[not found] ` <1d8c5e6e96fbdd47ce143a566b57db2c803d4898.camel@gnu.org>
2020-08-05 20:34 ` Michael Kerrisk (man-pages)
[not found] ` <21048.1596645536@jinx.noi.kre.to>
[not found] ` <CAH7i3LrNvBo3indixGyJgS2_4F9r3cd3kOiDgPK8m-ZXj1a0zg@mail.gmail.com>
[not found] ` <874bfe40-5f05-151d-42b3-482baacbf0b2@gmail.com>
[not found] ` <CAH7i3LpXZxwaLQTY=XK8zM4jWYHSiy1feA6ZLE-mT-ZiJNak5A@mail.gmail.com>
2020-08-11 8:31 ` Michael Kerrisk (man-pages)
2020-08-08 23:18 ` Larry Dwyer
2020-08-10 13:20 ` Joerg Schilling
2020-08-10 18:10 ` Zack Weinberg
2020-08-10 18:17 ` Samuel Thibault
2020-08-10 18:21 ` Samuel Thibault [this message]
2020-08-11 8:32 ` Michael Kerrisk (man-pages)
2020-08-10 13:58 ` Thor Lancelot Simon
2020-08-11 8:31 ` Michael Kerrisk (man-pages)
2020-08-11 11:51 ` Thor Lancelot Simon
2020-08-11 14:20 ` Michael Kerrisk
2020-08-12 14:37 ` Thor Lancelot Simon
2020-08-11 8:32 ` Michael Kerrisk (man-pages)
2020-08-11 17:29 ` Joshua M. Clulow
2020-08-12 13:19 ` Steffen Nurpmeso
2020-08-18 16:10 ` Dave Martin
2020-08-11 11:17 ` Dirk Fieldhouse
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=20200810182121.msb7mngurj653cau@function \
--to=samuel.thibault@ens-lyon.org \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=ajosey@opengroup.org \
--cc=austin-group-l@opengroup.org \
--cc=enh@google.com \
--cc=fweimer@redhat.com \
--cc=gwc@opengroup.org \
--cc=joseph@codesourcery.com \
--cc=larryd.kbd@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=zackw@panix.com \
/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;
as well as URLs for NNTP newsgroup(s).