Processing commands for [EMAIL PROTECTED]:
reassign 256468 kernel
Bug#256468: xterm: utmp handling is broken for high pts
Bug reassigned from package `xterm' to `kernel'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
reassign 256468 kernel
thanks
On Thu, Jul 08, 2004 at 07:40:39PM -0400, Thomas Dickey wrote:
On Thu, Jul 08, 2004 at 06:16:29PM -0500, Branden Robinson wrote:
Is it your opinion that this is a bug in the Linux kernel, then?
neither - I did read that this behavior is changed in the next
On Sun, Jun 27, 2004 at 10:47:21AM -0400, Thomas Dickey wrote:
On Sun, Jun 27, 2004 at 12:00:11PM +0200, Jim Paris wrote:
Package: xterm
Version: 4.3.0.dfsg.1-5
Severity: normal
Later Linux 2.6 kernels do not recycle pseudo TTYs, so ptys like
/dev/pts/1234 are not uncommon.
I
On Thu, Jul 08, 2004 at 06:16:29PM -0500, Branden Robinson wrote:
Is it your opinion that this is a bug in the Linux kernel, then?
neither - I did read that this behavior is changed in the next version
of the kernel, but it's something that xterm should (in principle) handle.
But if it's really
Package: xterm
Version: 4.3.0.dfsg.1-5
Severity: normal
Later Linux 2.6 kernels do not recycle pseudo TTYs, so ptys like
/dev/pts/1234 are not uncommon.
xterm does not seem to handle this well at all. In particular, it
relies on the 4-digit ut_id field in utmp, which would look like
p123 in
On Sun, Jun 27, 2004 at 12:00:11PM +0200, Jim Paris wrote:
Package: xterm
Version: 4.3.0.dfsg.1-5
Severity: normal
Later Linux 2.6 kernels do not recycle pseudo TTYs, so ptys like
/dev/pts/1234 are not uncommon.
I suppose it was to move complexity out of the kernel into the applications.
6 matches
Mail list logo
