Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Y test failures (zpty)
- X-seq: zsh-workers 16808
- From: Clint Adams <clint@xxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Y test failures (zpty)
- Date: Mon, 11 Mar 2002 14:02:31 -0500
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <1020311182942.ZM27214@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020311053241.GA9027@xxxxxxxx> <1020311182942.ZM27214@xxxxxxxxxxxxxxxxxxxxxxx>
> It would appear that the get_pty() function is failing. Why that's
> happening, I couldn't say. There are two different versions of that
> function in zpty.c -- is the wrong one getting used for some reason?
The one defined is one with /dev/ptyxx.
I'm not entirely certain that this is the wrong one; I have
Unix98 ptys in /dev/pts (this is what nearly everything uses),
and I have /dev/pty?? as compatibility symlinks to /dev/pty/m[0-9]+.
The nodes in /dev/pty are char devices (major 2), which are the
traditional BSD-style pty's.
> Has the naming convention for pty devices changed?
Unix98 ptys showed up as an option quite some time ago, but
you used to be able to still get BSD-style pty's if you asked
for one.
I imagine that something could be broken with the kernel or devfsd.
Irrespective of that, I'd think that zsh should do the /dev/ptmx
decision at runtime. Would this hurt anything?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author