All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Dwyer <larryd.kbd@gmail.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>, austin-group-l@opengroup.org
Cc: Carlos O'Donell <carlos@redhat.com>,
	Zack Weinberg <zackw@panix.com>,
	Florian Weimer <fweimer@redhat.com>,
	Paul Eggert <eggert@cs.ucla.edu>,
	Andrew Josey <ajosey@opengroup.org>,
	Joseph Myers <joseph@codesourcery.com>,
	linux-man <linux-man@vger.kernel.org>,
	Geoff Clare <gwc@opengroup.org>, Elliot Hughes <enh@google.com>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Pseudoterminal terminology in POSIX
Date: Sat, 8 Aug 2020 16:18:10 -0700	[thread overview]
Message-ID: <6425d636-7f48-3a73-ef0e-7bb5b991360c@gmail.com> (raw)
In-Reply-To: <CALxWeYrisuzEPVEHOQSFJ8G_=8-VTAOTNBquyszOZMid7YfT=Q@mail.gmail.com>

How about the "control" side and the "terminal" side (of the paired 
device files)?

Cheers,
Larry

On 8/5/2020 4:21 AM, Michael Kerrisk via austin-group-l at The Open 
Group wrote:
> Elliot Hughes and I both noticed a point from "Minutes of the 3rd August 2020
> Teleconference":
> 
> [[
> On Tue, Aug 4, 2020 at 5:52 PM Andrew Josey <ajosey@opengroup.org> wrote:
>>
>> All
>> Enclosed are the minutes of yesterdays teleconference
>> regards
>> Andrew
> 
> [...]
> 
>> * General news
>>
>> We discussed terminology usage, in particuler terms such as
>> master/slave, blacklist/whitelist.  It was agreed some terminology
>> for pseudo-terminals could be better described using more functionally
>> descriptive terms, but the details of this are left to a future bug
>> report.  Andrew and Geoff took an action to investigate further
>> and come back with an analysis.
> ]]
> 
> I see that Elliot already replied to the Minutes with some thoughts
> about this. I had already been working on thismail on the topic, which
> reiterates some details that Elliot gave, but also adds some
> information, and brings a lot of relevant people into CC. (I've
> already notified those people that only subscribers can post to the
> Austin list, and presumably those not already subscribed will
> subscribe if they want to add to the discussion.)
> 
> The master-slave terminology with respect to pseudoterminals has
> recently been under active discussion in the GNU C library and Linux
> man-pages mailing lists (see [1]). Currently, we are considering at
> least one possible proposal for a language change, but there may yet
> be others. In any case, I and others thought it would be a wise idea
> to involve TOG in this discussion, so that, ideally, we could come up
> with a shared standard for replacement terminology.
> 
> The proposal that has seen some discussion, and met with some positive
> feedback, is [2]. The concept was proposed by Elliot, inspired by a
> similar change that was made in relevant golang libraries; I've
> written an implementation of the idea (i.e., a proposed patch) for the
> Linux manual pages (again, see [2]).
> 
> The essence of the idea is simple. Let's not invent completely new
> terms, but rather rework existing (familiar) terminology a little, as
> follows:
> 
>      pseudoterminal (device) ==> "pseudoterminal device pair"
> 
>     slave ==> "terminal device"
>             (or "terminal end of the pseudoterminal device pair")
> 
>      master ==> "pseudoterminal device"
>             (or "pseudoterminal end of the pseudoterminal device pair")
> 
> The resulting language (as it appears in the proposed changes for the
> Linux manual pages) is reasonably clear, albeit a little clunky in
> places (wordings like "the (pseudo)terminal end of the pseudoterminal
> device pair" are clear, but a little verbose).
> 
> Aside from the obvious points (raising a bug on the Austin bug
> tracker, and proposing line edits to the standard), is there anything
> else that we can do to help along the process of changing the
> terminology in POSIX? Also, any feedback on the proposal in [2] would be
> welcome.
> 
> With best regards,
> 
> Michael Kerrisk
> 
> [1] https://sourceware.org/pipermail/libc-alpha/2020-July/115792.html
> 
> [2] https://lore.kernel.org/linux-man/b3b4cf95-5eaa-0b4e-34cc-1a855e7148b6@gmail.com/
> 
> 

  parent reply	other threads:[~2020-08-08 23:18 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 [this message]
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
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=6425d636-7f48-3a73-ef0e-7bb5b991360c@gmail.com \
    --to=larryd.kbd@gmail.com \
    --cc=ajosey@opengroup.org \
    --cc=austin-group-l@opengroup.org \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=enh@google.com \
    --cc=fweimer@redhat.com \
    --cc=gwc@opengroup.org \
    --cc=joseph@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.