public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: pts bug? and keyboard on kvm
Date: Fri, 12 Mar 2004 08:02:36 +0000 (UTC)	[thread overview]
Message-ID: <c2rqqs$pnc$1@terminus.zytor.com> (raw)
In-Reply-To: Pine.LNX.4.58.0403111109290.21406@pina-colada.ucf.ics.uci.edu

Followup to:  <Pine.LNX.4.58.0403111109290.21406@pina-colada.ucf.ics.uci.edu>
By author:    Edmund Lau <edlau@ucf.ics.uci.edu>
In newsgroup: linux.dev.kernel
> 
> I just upgraded to 2.6.4.  Is it normal for /dev/pts numbers to keep
> increasing now?  With 2.6.3, I could log in or create an xterm and a pts
> would be assigned.  Then when it was released, another process could reuse
> that number.  Now, it seems it just keeps incrementing.  Has this changed?
> 

Yes.  We may make a slight change to this, due to the incredibly
braindamaged way glibc and xterm handles utmp, however.

	-hpa

      reply	other threads:[~2004-03-12  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 19:25 pts bug? and keyboard on kvm Edmund Lau
2004-03-12  8:02 ` 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='c2rqqs$pnc$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --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