Re: workaround for: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On 2007-09-03 03:38:13 -0500, Mumia W.. wrote: > Sarge uses S02mountvirtfs, and Etch uses S04mountdevsubfs.sh. > > Probably there's a bug in one of Sid's startup scripts. My machine is sid and has no problems. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible

Re: workaround for: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On 09/03/2007 12:56 AM, Paul Scott wrote: Takehiko Abe wrote: (snip) Note that I've never had to do it myself. My /etc/fstab on a Sarge system has this entry: none/dev/ptsdevptsgid=5,mode=62000 I will try putting this in my fstab after I send this email. But my lenny

workaround for: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Takehiko Abe wrote: > Paul Scott wrote: > > > $ stat /dev/ptmx > > [...snip...] > > ptmx looks fine to me. > > > mountpoint says /dev/pts is not a mount point > > You need to mount devpts filesystem at /dev/pts. > pts(4) manpage says: > > ;; The Linux support for the above (known as Unix98 pty nami

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Paul Scott wrote: > $ stat /dev/ptmx > [...snip...] ptmx looks fine to me. > mountpoint says /dev/pts is not a mount point You need to mount devpts filesystem at /dev/pts. pts(4) manpage says: ;; The Linux support for the above (known as Unix98 pty naming) is ;; done using the devpts filesyst

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Takehiko Abe wrote: Paul Scott wrote: >> looks different from the previous pty error. Have you fixed that? > > I don't know enough to know why it should have changed with all > stock updates or enough to fix it at this point. You reported that legacy pty support is turned off in the new kernel.

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Paul Scott wrote: >> looks different from the previous pty error. Have you fixed that? > > I don't know enough to know why it should have changed with all > stock updates or enough to fix it at this point. You reported that legacy pty support is turned off in the new kernel. That is one change f

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On Sat, 1 Sep 2007, Paul Scott wrote: Takehiko Abe wrote: Paul Scott wrote: Here's the end of the strace. It doesn't tell me anything we don't already know. Maybe someone else will see more: So what do you already know? For instance, this [...] write(2, "xterm Xt error: Can\'t open disp

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Takehiko Abe wrote: Paul Scott wrote: Here's the end of the strace. It doesn't tell me anything we don't already know. Maybe someone else will see more: So what do you already know? For instance, this [...] write(2, "xterm Xt error: Can\'t open displ"..., [...] looks different from the

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Paul Scott wrote: Here's the end of the strace. It doesn't tell me anything we don't already know. Maybe someone else will see more: So what do you already know? For instance, this [...] write(2, "xterm Xt error: Can\'t open displ"..., [...] looks different from the previous pty error. H

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Vincent Lefevre wrote: > On 2007-08-30 23:46:39 -0700, Paul Scott wrote: > >> Vincent Lefevre wrote: >> >>> I have no problems with this recent change on my x86 machine. >>> Also, if I understand correctly, most programs no longer use >>> "legacy" pty's. And ttyrec, which still uses them, f

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On 2007-08-30 23:46:39 -0700, Paul Scott wrote: > Vincent Lefevre wrote: >> I have no problems with this recent change on my x86 machine. >> Also, if I understand correctly, most programs no longer use >> "legacy" pty's. And ttyrec, which still uses them, fails with >> the new kernel. The fact that

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Vincent Lefevre wrote: On 2007-08-29 20:40:28 -0700, Paul Scott wrote: So have I been missing the main point? Is the recent change in CONFIG_LEGACY_PTYS the problem? I have no problems with this recent change on my x86 machine. Also, if I understand correctly, most programs no longer

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Wayne Topa wrote: OK from your Aug 26 post CONFIG_LEGACY_PTYS=Y CONFIG_LEGACY_PTY_COUNT+256 ^ That should be = Not + That should not have happend, unless you ignored the warning at the top of the file. " # Automatically generated make config: don't edit" These are bot

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Paul Scott([EMAIL PROTECTED]) is reported to have said: > Wayne Topa wrote: >> Paul Scott([EMAIL PROTECTED]) is reported to have said: >> >>> Laptop with AMD K6 running Debian sid >>> >>> xterm works w/ stock 2.6.17-2-486 >>> >>> with stock 2.6.22-1-486 attempting to start xterm gives: >>> >>> x

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On 2007-08-29 20:40:28 -0700, Paul Scott wrote: > So have I been missing the main point? Is the recent change in > CONFIG_LEGACY_PTYS the problem? I have no problems with this recent change on my x86 machine. Also, if I understand correctly, most programs no longer use "legacy" pty's. And ttyrec

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Wayne Topa wrote: Paul Scott([EMAIL PROTECTED]) is reported to have said: Laptop with AMD K6 running Debian sid xterm works w/ stock 2.6.17-2-486 with stock 2.6.22-1-486 attempting to start xterm gives: xterm: Error 32, errno 2: No such file or directory Reason: get_pty: not enough ptys I

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Wayne Topa wrote: Paul Scott([EMAIL PROTECTED]) is reported to have said: Laptop with AMD K6 running Debian sid xterm works w/ stock 2.6.17-2-486 with stock 2.6.22-1-486 attempting to start xterm gives: xterm: Error 32, errno 2: No such file or directory Reason: get_pty: not enough ptys I

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Paul Scott([EMAIL PROTECTED]) is reported to have said: > Laptop with AMD K6 running Debian sid > > xterm works w/ stock 2.6.17-2-486 > > with stock 2.6.22-1-486 attempting to start xterm gives: > > xterm: Error 32, errno 2: No such file or directory > Reason: get_pty: not enough ptys > > I have up

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Paul Scott([EMAIL PROTECTED]) is reported to have said: > Laptop with AMD K6 running Debian sid > > xterm works w/ stock 2.6.17-2-486 > > with stock 2.6.22-1-486 attempting to start xterm gives: > > xterm: Error 32, errno 2: No such file or directory > Reason: get_pty: not enough ptys > > I have up

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On 08/29/2007 06:51 AM, Mumia W.. wrote: Could someone please e-mail me (or post to http://pastebin.mozilla.org ) a copy of /boot/config-2.6.22-1-486 ? I want to see if I have this problem with 2.6.22 also, but I need to use the default config file. I apologize for bothering the list. I ha

Re: xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

On 08/28/2007 11:22 PM, Paul Scott wrote: Laptop with AMD K6 running Debian sid xterm works w/ stock 2.6.17-2-486 with stock 2.6.22-1-486 attempting to start xterm gives: xterm: Error 32, errno 2: No such file or directory Reason: get_pty: not enough ptys I have upgraded almost anything that

xterm won't start on AMD K6 with stock 2.6.22-1-486 kernel

Laptop with AMD K6 running Debian sid xterm works w/ stock 2.6.17-2-486 with stock 2.6.22-1-486 attempting to start xterm gives: xterm: Error 32, errno 2: No such file or directory Reason: get_pty: not enough ptys I have upgraded almost anything that needed it that would have come after the 2