From: Christoph Hellwig <hch@infradead.org>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Andrew Morton <akpm@osdl.org>,
andrew@lunn.ch, linux-kernel@vger.kernel.org
Subject: Re: 2.6-test4 Traditional pty and devfs
Date: Tue, 2 Sep 2003 19:29:29 +0100 [thread overview]
Message-ID: <20030902192928.A17371@infradead.org> (raw)
In-Reply-To: <20030902181654.GB6652@biferten.ma.tech.ascom.ch>; from andrew.lunn@ascom.ch on Tue, Sep 02, 2003 at 08:16:54PM +0200
On Tue, Sep 02, 2003 at 08:16:54PM +0200, Andrew Lunn wrote:
> > That's why I'm really keen on knowing how the system of the bugreporter
> > looks - this shouldn't happen without a very strange setup.
>
> I've attached to the bugzilla bug my .config (its actually for -test2)
> and an ls -la /dev/pt*
>
> Is there anything else you want to know?
That doesn't really help - if an application opens old-style pty's
directly the permissions can't work. IF you care for them fill a
bugreport to ripperx that it should use openpty() from libc which
will fix the problem automatically.
Until then we should apply your patch to create the slaves on init
so the behaviour is consistant with 2.4 and 2.6 without devfs.
I was just wondering whether you were using an acient / stripped
down libc with the pt_chown helper removed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Sep 02, 2003 at 08:16:54PM +0200, Andrew Lunn wrote:
> > That's why I'm really keen on knowing how the system of the bugreporter
> > looks - this shouldn't happen without a very strange setup.
>
> I've attached to the bugzilla bug my .config (its actually for -test2)
> and an ls -la /dev/pt*
>
> Is there anything else you want to know?
That doesn't really help - if an application opens old-style pty's
directly the permissions can't work. IF you care for them fill a
bugreport to ripperx that it should use openpty() from libc which
will fix the problem automatically.
Until then we should apply your patch to create the slaves on init
so the behaviour is consistant with 2.4 and 2.6 without devfs.
I was just wondering whether you were using an acient / stripped
down libc with the pt_chown helper removed.
next prev parent reply other threads:[~2003-09-02 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-09-02 18:35 ` Andrew Lunn
2003-09-02 18:08 ` Andrew Lunn
2003-09-03 2:52 Albert Cahalan
2003-09-03 6:35 ` Christoph Hellwig
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=20030902192928.A17371@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=andrew.lunn@ascom.ch \
--cc=andrew@lunn.ch \
--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®