From: "H. Peter Anvin" <hpa@zytor.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Kay Sievers <kay@vrfy.org>, "Ted Ts'o" <tytso@mit.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
Greg Kroah-Hartman <gregkh@linux-foundation.org>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Subject: Re: RFC: deprecating/removing the legacy mode of devpts
Date: Wed, 11 Apr 2012 20:07:08 -0700 [thread overview]
Message-ID: <4F8646DC.9020800@zytor.com> (raw)
In-Reply-To: <20120412030425.GL6589@ZenIV.linux.org.uk>
On 04/11/2012 08:04 PM, Al Viro wrote:
> On Wed, Apr 11, 2012 at 07:48:44PM -0700, H. Peter Anvin wrote:
>> The symlink support is at least 3 years old, probably more.
>
> DEVPTS_MULTIPLE_INSTANCES wasn't anywhere near mandatory all that time...
> Kernel upgrade procedure that starts with "build the old kernel with
> that option enabled, boot it, replace /dev/ptmx with a symlink, then
> never try to boot earlier kernel images. Now you can safely upgrade
> to current kernel" is the recipe for massive self-LARTs (and resulting
> pitchfork crowds).
Sounds like the first thing we need to do is to remove the
CONFIG_DEVPTS_MULTIPLE_INSTANCES=n code.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-04-12 3:07 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
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 [this message]
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=4F8646DC.9020800@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linux-foundation.org \
--cc=kay@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox