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
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.
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
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
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
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
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
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
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
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
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
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
On 2007-08-29 15:39:42 -0700, Paul Scott wrote:
> No terminal I have tried will start.
> rxvt fails. The error message is:
>
> urxvt: can't initialize pseudo-tty, aborting.
>
> Text mode Emacs 21 also fails.
So, the problem seems to come from your kernel (since the old one works).
Another sugg
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
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
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
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
Vincent Lefevre wrote:
> On 2007-08-27 23:06:53 -0700, Paul Scott wrote:
>
>> I should have made it clear that I am using a (the latest package)
>> stock 2.6.22 (486) kernel. It would seem that I must have made some
>> kind of install mistake to lead to:
>>
>> xterm: Error 32, errno 2: No such f
On 2007-08-27 23:06:53 -0700, Paul Scott wrote:
> I should have made it clear that I am using a (the latest package)
> stock 2.6.22 (486) kernel. It would seem that I must have made some
> kind of install mistake to lead to:
>
> xterm: Error 32, errno 2: No such file or directory
> Reason: get_pty:
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
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
Sent from unsubscribed address again.
Vincent Lefevre wrote:
On 2007-08-27 10:28:48 -, Thomas Dickey wrote:
Vincent Lefevre <[EMAIL PROTECTED]> wrote:
I've had a pty-related error with xterm on PowerPC in the past. I had
to use the following workaround in my app-defaults file for X
Vincent Lefevre wrote:
On 2007-08-27 10:28:48 -, Thomas Dickey wrote:
Vincent Lefevre <[EMAIL PROTECTED]> wrote:
I've had a pty-related error with xterm on PowerPC in the past. I had
to use the following workaround in my app-defaults file for XTerm:
I don't think it is relat
On 2007-08-27 10:28:48 -, Thomas Dickey wrote:
> Vincent Lefevre <[EMAIL PROTECTED]> wrote:
> > I've had a pty-related error with xterm on PowerPC in the past. I had
> > to use the following workaround in my app-defaults file for XTerm:
>
> I don't think it is related (it's a different error c
Vincent Lefevre <[EMAIL PROTECTED]> wrote:
> I've had a pty-related error with xterm on PowerPC in the past. I had
> to use the following workaround in my app-defaults file for XTerm:
I don't think it is related (it's a different error code).
> ! On ay (PPC), ones needs to set eightBitInput to t
On 2007-08-26 19:46:29 -0700, Paul Scott wrote:
> Installed 2.6.22 kernel and built module for USB wireless card.
> Starting xterm gives:
>
> xterm: Error 32, errno 2: No such file or directory
> Reason: get_pty: not enough ptys
I've had a pty-related error with xterm on PowerPC in the past. I had
26 matches
Mail list logo
