From: Greg Kroah-Hartman <gregkh@linux-foundation.org>
To: Kay Sievers <kay@vrfy.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, "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>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Subject: Re: RFC: deprecating/removing the legacy mode of devpts
Date: Wed, 11 Apr 2012 18:14:02 -0700 [thread overview]
Message-ID: <20120412011402.GA23803@kroah.com> (raw)
In-Reply-To: <CAPXgP12iMFrsk2pq54sBuQL4jk_vGJS2AxW0HjkU5wjhv1Wskw@mail.gmail.com>
On Thu, Apr 12, 2012 at 02:38:29AM +0200, Kay Sievers wrote:
> On Thu, Apr 12, 2012 at 02:30, Greg Kroah-Hartman
> <gregkh@linux-foundation.org> wrote:
> > On Wed, Apr 11, 2012 at 04:55:41PM -0700, H. Peter Anvin wrote:
> >> On 04/11/2012 04:53 PM, Greg Kroah-Hartman wrote:
> >> >
> >> > That all seems pretty simple.
> >> >
> >> >> - get rid of the (rather broken) idea of 'legacy' vs 'non-legacy mode'
> >> >> mount options in the default setup; I don't think userspace should
> >> >> ever be required to fiddle with such stuff
> >> >
> >> > Hm, but if we get rid of them, what about tools that expect them to be
> >> > there? Just silently ignore them?
> >> >
> >>
> >> Drop the newinstance mount option on the floor; keep recognizing the
> >> ptmxmode mount option but change the default.
> >
> > Wait, change the default to what?
>
> Of the devpts fs mount option. The 'newinstance' one, which should not
> have existed in the first place.
>
> > I think this is going to require a lot of testing :)
>
> In the example patch I posted and which I ran here, I just removed the
> entire option. This was just to show that userspace does not want to
> be taught dirty tricks that need updating of early-boot tools. All
> such pretty self-contained stuff should be in the kernel itself.
> Userspace wants to be dumb here, and that worked fine so far with that
> patch. :)
I missed your patch, sorry, am catching up on the email thread now...
greg k-h
next prev parent reply other threads:[~2012-04-12 1:14 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 [this message]
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=20120412011402.GA23803@kroah.com \
--to=gregkh@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--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