mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: linux-kernel@vger.kernel.org
Cc: andrew.lunn@ascom.ch
Subject: 2.6-test4 Traditional pty and devfs
Date: Tue, 2 Sep 2003 12:42:12 +0200	[thread overview]
Message-ID: <20030902104212.GA23978@londo.lunn.ch> (raw)

Hi Folks

http://bugme.osdl.org/show_bug.cgi?id=1045

I found that devfs and traditional pty's don't work properly with
2.6-test4 and a lot of previous versions. Note im talking about
traditional pty's not UNIX98 which need devpts mounted.

The pty slave devices do not appear in devfs. They should be
/dev/pts/s* and symbolic links from /dev/pty* into /dev/pts/s*. But
these are all missing. So programs like ripperx which use a pty to
control cdparanoia don't work.

I've attached two possible patches to the bugzilla bug. The first one
causes the slave devices to be created in devfs at start up. The
second one makes it work more like 2.4 when the slave device is only
created when the master device is opened.

Both patches suffer from a problem. The slave is always only RW
root. 2.4 sets the owner of the slave to that of the process opening
the master. I cannot see a way to make this happen with 2.6-test. 

Im open for suggestions as to the correct way to fix this.

   Thanks
        Andrew

             reply	other threads:[~2003-09-02 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 10:42 Andrew Lunn [this message]
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
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=20030902104212.GA23978@londo.lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andrew.lunn@ascom.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®