DragonFlyBSD

A ktrace of the old screen binary is needed, at least.

Cheers,
Alex Hornung

2009/9/28 Alex Hornung (via DragonFly issue tracker)
<sinknull@leaf.dragonflybsd.org>:

Alex Hornung <ahornung@gmail.com> added the comment:

A ktrace of the old screen binary is needed, at least.

For me, sudo and many other packages failed with same error message
after upgrade from 2.3.x until got rebuilt/reinstalled.
Could it be you have ssh from pkgsrc or world not in sync with recent
kernel (pty98 works, I guess).

Dennis, I don't understand what you are trying to say.
What does sudo have to do with ptys? What does my ssh to do with not having
something in sync?
Fact is that I'd need a ktrace or even better, an old binary, showing the
symptoms.

Cheers,
Alex Hornung

Seems that the problem is due to having an old libc.so.6 present on the system.
As the old screen binary was linked against libc.so.6, it is using the outdated
implementation of ttyname() which no longer is valid due to the dynamic nature
of the ttys now.
Valid solutions are:
- Recompiling screen and similar programs
- remove old libc.so.6 and make symlink libc.so.6 -> libc.so.7

As for maintaining binary compatibility, this has been discussed before and it
has been ok'ed to not keep binary compatibility for devname and ttyname.

Cheers,
Alex Hornung

Hi Alex,

2009/9/30 Alex Hornung (via DragonFly issue tracker)
<sinknull@leaf.dragonflybsd.org>:

Alex Hornung <ahornung@gmail.com> added the comment:

Dennis, I don't understand what you are trying to say.
What does sudo have to do with ptys? What does my ssh to do with not having
something in sync?

Well, I have only an idea of the problem background. So sorry if I
mistaken the name of tty-related tasks. Looks like you've already
found the solution (libc 6->7).

Sorry, has no old files anymore.