public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
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>,
	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: Thu, 12 Apr 2012 02:08:04 +0100	[thread overview]
Message-ID: <20120412010804.GI6589@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAPXgP10-_kS7VtdWonBhOxKJD2KatB9SznZ_xUUaxBz7-boT2A@mail.gmail.com>

On Sun, Apr 08, 2012 at 09:16:22PM +0200, Kay Sievers wrote:

> I guess the following:
>   - remove the 'ptmx' cdev from drivers/tty/pty.c
>   - add a new devtmpfs_create_link() to drivers/base/devtmpfs.c
>   - call devtmpfs_create_link() from _init in fs/devpts/inode.c
>   - change the default of ptxmode=0 to a sane default = 0666
>   - 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

You do realize that there are people with _static_ /dev out there, don't
you?  As well as those of us who are not using your latest and greatest
udev and not enabling devtmpfs at all.  Not all world is Fedora...

  parent reply	other threads:[~2012-04-12  1:08 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 [this message]
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=20120412010804.GI6589@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@linux-foundation.org \
    --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 \
    /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