From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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@suse.de>,
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, 7 Apr 2012 20:20:56 +0100 [thread overview]
Message-ID: <20120407202056.472d8ad9@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <4F80892A.7050104@zytor.com>
On Sat, 07 Apr 2012 11:36:26 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:
> Currently, devpts supports a legacy mode where only one instance exists.
> For backwards compatibility, this is also the default mode, but the
> right thing should be to migrate everyone over to the "newinstance" scheme.
>
> However, it is increasingly clear that that is not happening; neither
> the distros nor udev support this by default at this point.
Well maybe thats because the legacy mode works perfectly well for most
purposes and does what they want. The "non-legacy" mode is really not
"non-legacy" its "special case extra funkiness".
With my tty hat on I'd prefer to keep it indefinitely if need be. It's
hardly a maintainability issue or a hot problem. We've got much bigger
turds to juggle than that.
I don't see why we need an agendum to force the users into making changes
that really don't matter. I mean we still support BSD ptys 8)
Alan
next prev parent reply other threads:[~2012-04-07 19:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 18:36 H. Peter Anvin
2012-04-07 19:20 ` Alan Cox [this message]
2012-04-07 20:02 ` H. Peter Anvin
2012-04-07 21:27 ` Ted Ts'o
2012-04-07 22:03 ` H. Peter Anvin
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=20120407202056.472d8ad9@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=kay.sievers@vrfy.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®