From: Jamie Lokier <jamie@shareable.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>,
linux-kernel@vger.kernel.org
Subject: Re: PTS alocation problem with 2.6.4/2.6.5
Date: Tue, 6 Apr 2004 18:55:01 +0100 [thread overview]
Message-ID: <20040406175501.GA27672@mail.shareable.org> (raw)
In-Reply-To: <20040405165957.5f8ab8dc.akpm@osdl.org>
Andrew Morton wrote:
> You need a glibc upgrade - we broke things for really old glibc's. We're
> (slowly) working on fixing it up.
Looking at patch-2.6.4, there are plenty of minor changes to the pty
code but nothing that looks like it would break userspace except for
_very_ old glibcs that don't know about /dev/pts at all and just used
the legacy ones.
I have some _non-glibc_ pty code that I wish to keep working. Can you
briefly explain how it breaks with moderately old glibcs such as the
glibc-2.3.3 that's said to be inadequate, and therefore what interface
change is needed in non-glibc code?
Thanks,
-- Jamie
next prev parent reply other threads:[~2004-04-06 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 22:53 Andrzej Krzysztofowicz
2004-04-05 23:59 ` Andrew Morton
2004-04-06 5:11 ` Andrzej Krzysztofowicz
2004-04-06 17:55 ` Jamie Lokier [this message]
2004-04-06 18:16 ` Andrew Morton
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=20040406175501.GA27672@mail.shareable.org \
--to=jamie@shareable.org \
--cc=akpm@osdl.org \
--cc=ankry@green.mif.pg.gda.pl \
--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®