I'm not sure how to test the UNIX98 ptys, but it does show
pty: 256 Unix98 ptys configured
At bootup, has a line in /etc/fstab :
none /dev/pts devpts mode=0622 0 0
And is running on a totally glibc 2.1 built system (including the kernel)
[root@netwinder lsh-snapshot-1999-02-28]# cat /proc/version
Linux version 2.2.2 (root@netwinder) (gcc version egcs-2.91.60.1
19990115/Linux (egcs-1.1.1 release)) #1 Fri Mar 5 00:21:08 EST 1999
So everything seems fine as far as the UNIX98 ptys go.
I did some work with the CVS stuff from yesterday, and it didn't seem to
help. I saw there were changes today, but they seemed related to adding a
new encryption scheme and not to pty stuff. Have there been changes since
the 28th snapshot that might affect pty stuff?
I will certainly add the Netwinder to the port list if I can get it all
working right...
I would be happy to give you an account on the machine if you want to mess
around with the UNIX98 stuff. I spent a long time getting everything built
and would be glad to see others benefit.
Jason.
----------
>From: "J.H.M. Dassen" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Can't connect to lsh... (pty problem?)
>Date: Fri, Mar 5, 1999, 1:20 PM
>
> On Fri, Mar 05, 1999 at 12:53:19 -0500, Jason Titus wrote:
>> Client requesting a tty...
>> granted.
>> tty_setctty: unlockpt() failed,
>> (errno = 44): Bad address
>> lshd: Can't set controlling tty for child!
>
> Does using the latest version (from Niels' cvsweb) make a difference?
>
>> I am on a Linux 2.2.2 kernel, using UNIX98 ptys
>
> Are you sure your UNIX98 pty support is supposed to work? (I.e. are you
> using a late glibc pre-2.1 or glibc 2.1?, do you have a devpts entry in
> /etc/fstab?)
>
> The parts of UNIX98 support I wrote were written "blindly" (i.e. from the
> glibc documentation); I have no glibc2.1 system to test them on yet.
>
>> on a Corel Netwinder (StrongARM 110).
>
> Cool. Please submit an entry for the PORTS file.
>
> Ray
> --
> Obsig: developing a new sig
>
