From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Christoph Hellwig <hch@infradead.org>,
Andrew Lunn <andrew@lunn.ch>,
linux-kernel@vger.kernel.org, andrew.lunn@ascom.ch
Subject: Re: 2.6-test4 Traditional pty and devfs
Date: Tue, 2 Sep 2003 20:08:03 +0200 [thread overview]
Message-ID: <20030902180803.GA6652@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <20030902150808.A7388@infradead.org>
> Well, that's why we have UNIX98 ptys. My preferred fix for this
> issue would be to just axe traditional ptys, although this would probably
> make it us incompatible with libc5.
>
> Why aren't you using the new-style ptys?
Ripperx, the program that is failing, is not mine. I have no control
over what sort of pty it uses. Im sure there are other programs with
use traditional pty's as well.
Andrew
-
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/
> Well, that's why we have UNIX98 ptys. My preferred fix for this
> issue would be to just axe traditional ptys, although this would probably
> make it us incompatible with libc5.
>
> Why aren't you using the new-style ptys?
Ripperx, the program that is failing, is not mine. I have no control
over what sort of pty it uses. Im sure there are other programs with
use traditional pty's as well.
Andrew
next prev parent reply other threads:[~2003-09-02 18:13 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
2003-09-02 18:35 ` Andrew Lunn
2003-09-02 18:08 ` Andrew Lunn [this message]
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=20030902180803.GA6652@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=andrew@lunn.ch \
--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®