All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Ted Ts'o" <tytso@mit.edu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Konstantin Khlebnikov <khlebnikov@openvz.org>,
	Greg Kroah-Hartman <gregkh@linux-foundation.org>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Subject: Re: RFC: deprecating/removing the legacy mode of devpts
Date: Sat, 07 Apr 2012 15:03:24 -0700	[thread overview]
Message-ID: <4F80B9AC.2010103@zytor.com> (raw)
In-Reply-To: <20120407212705.GD11295@thunk.org>

On 04/07/2012 02:27 PM, Ted Ts'o wrote:
> On Sat, Apr 07, 2012 at 01:02:33PM -0700, H. Peter Anvin wrote:
>> The problem is that the lack of migration at the root causes real
>> problems for the people who need the extra funkiness, and unlike BSD
>> ttys it's not an application-level change at all.
> 
> Could you explain what the issues are?  I haven't been following
> devpts all that carefully.
> 

The issue is that to make the "ptys are private to an instance of the
devpts filesystem", /dev/ptmx has to live inside the /dev/pts
filesystem.  This was traditionally not the case.  To avoid breaking
everything all at once, we have a legacy mode which supports the "all
devpts instances are the same" (effectively bind mounts) and which
support a /dev/ptmx outside /dev/pts.

The problem is that anyone who wants to take advantage of the new
functionality has to make sure *all* instances of devpts work with the
new protocol.  This means modifying your distro to:

1. Add "newinstance" and "ptmxmode" to /etc/fstab [easy]
2. Make /dev/ptmx a symlink to /dev/pts/ptmx.

2 would be easy if it wasn't for udev, which makes it very hard.  It is
not reasonable for udev to support both modes, so the *only* mode that
is reasonable for it to support is the new mode.  However, it is
increasingly obvious that if we don't force it, this will never happen.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-04-07 22:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-07 18:36 RFC: deprecating/removing the legacy mode of devpts H. Peter Anvin
2012-04-07 19:20 ` Alan Cox
2012-04-07 20:02   ` H. Peter Anvin
2012-04-07 21:27     ` Ted Ts'o
2012-04-07 22:03       ` H. Peter Anvin [this message]
2012-04-08  7:30         ` Kay Sievers
2012-04-08 18:00           ` H. Peter Anvin
2012-04-08 19:16             ` Kay Sievers
2012-04-11 23:53               ` Greg Kroah-Hartman
2012-04-11 23:55                 ` H. Peter Anvin
2012-04-12  0:30                   ` Greg Kroah-Hartman
2012-04-12  0:38                     ` Kay Sievers
2012-04-12  1:14                       ` Greg Kroah-Hartman
2012-04-12  1:08               ` Al Viro
2012-04-12  1:56                 ` H. Peter Anvin
2012-04-12  2:26                   ` Al Viro
2012-04-12  2:48                     ` H. Peter Anvin
2012-04-12  3:04                       ` Al Viro
2012-04-12  3:07                         ` H. Peter Anvin
2012-04-12  2:27                 ` Kay Sievers
2012-04-12  2:45                   ` Al Viro
2012-04-12  2:48                     ` Kay Sievers
2012-04-12  2:53                   ` H. Peter Anvin
2012-04-12  3:02                     ` Kay Sievers
2012-04-08 17:20         ` Alan Cox
2012-04-07 20:04   ` H. Peter Anvin
2012-04-08 18:15 ` Konstantin Khlebnikov
2012-04-08 22:18   ` Alan Cox
2012-04-08 22:26     ` H. Peter Anvin
2012-04-08 22:46       ` Alan Cox
2012-04-08 22:45         ` H. Peter Anvin
2012-04-09  3:15           ` Theodore Tso
2012-04-09 12:43             ` Kay Sievers
2012-04-09 13:37               ` Al Viro

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=4F80B9AC.2010103@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@linux-foundation.org \
    --cc=kay.sievers@vrfy.org \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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.