From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: hch@infradead.org, akpm@osdl.org
Subject: Re: 2.6-test4 Traditional pty and devfs
Date: 02 Sep 2003 22:52:47 -0400 [thread overview]
Message-ID: <1062557567.846.2090.camel@cube> (raw)
Christoph Hellwig writes:
> On Tue, Sep 02, 2003 at 10:43:40AM -0700, Andrew Morton wrote:
>>> That's the magic use uid/gid of the process calling
>>> devfs_Register flag I killed. With a big HEADSUP
>>> and explanation on lkml..
>>
>> So what is the impact here? That libc5 will break if
>> the user is using devfs and old-style pty's?
>
> If he removed the pt_chown logic that is present with a
> stock libc5, yes. I wouldn't know why someone would do
> that, though.
The problem may be more serious. There are lots of
apps that use the old-style PTYs w/o any libc help.
a. because that's the historic BSD way
b. so the user can choose a specific pty
For example, there's a "remserial" program
that abuses a PTY for giving access to a
serial port over the network. Apps trying to
use the port work pretty well, without any need
for source code changes or new kernel drivers.
next reply other threads:[~2003-09-03 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 2:52 Albert Cahalan [this message]
2003-09-03 6:35 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-09-02 10:42 Andrew Lunn
2003-09-02 14:08 ` Christoph Hellwig
2003-09-02 17:21 ` Andrew Morton
2003-09-02 17:42 ` Christoph Hellwig
2003-09-02 17:43 ` Andrew Morton
2003-09-02 18:02 ` Christoph Hellwig
2003-09-02 18:16 ` Andrew Lunn
2003-09-02 18:29 ` Christoph Hellwig
2003-09-02 18:35 ` Andrew Lunn
2003-09-02 18:08 ` Andrew Lunn
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=1062557567.846.2090.camel@cube \
--to=albert@users.sf.net \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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®