public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Igmar Palsenberg <maillist@chello.nl>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: xterm: no available ptys
Date: Tue, 07 Nov 2000 18:24:27 -0800	[thread overview]
Message-ID: <3A08B95B.3D473A5F@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011080131200.32613-100000@server.serve.me.nl>

Igmar Palsenberg wrote:
> 
> > > I'm missing ptmx. You NEED a writable /dev/pts dir.
> > >
> >
> > Actually, what you need is the devpts filesystem mounted onto
> > /dev/pts.
> 
> Agree. I had a shitload of probs when 2.2.0 came out and I switched.. Was
> due that /dev was readonly here. Bit strange if I think of it.
> 

If you don't have devpts mounted, glibc tries to use a setuid program to
hack around /dev for you.  I'd rather wish it didn't, actually.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-08  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-06 20:37 xterm: no available ptys Paul Powell
2000-11-06 20:53 ` Ben Ford
2000-11-06 20:57 ` Michael Meissner
2000-11-06 22:04   ` H. Peter Anvin
2000-11-07  0:57 ` Igmar Palsenberg
2000-11-07  0:28   ` H. Peter Anvin
2000-11-08  0:32     ` Igmar Palsenberg
2000-11-08  2:24       ` H. Peter Anvin [this message]

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=3A08B95B.3D473A5F@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@chello.nl \
    /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