[uClibc] pty support: /dev/pty/m* /dev/pty/s*

[Maillists]

Hi Erik

the notice that ftpd and telnetd would not work with UNIX98_PTYS 
switched on is not true. It was a mistake of mine. But I still have 
both, /dev/pty/m[0-255] and /dev/ptmx.

telnetd adds a /dev/pty/s0 as soon a telnet connection is opened, and 
opening ptmx's with fd = open( "/dev/ptmx", O_RDWR ) n times adds n 
times /dev/pts/[0-(n-1)].

Unluckily the  openpty( mstrFd, slvFd, ... ) from the uClibc 0.9.19 we 
have does not work on my system. What I get is a ENOTTY - "Not a type 
wirter" in errno.
I found that in ptsname.c revision 5682 a bug fix was made due to a 
misbehaviour when __UNIX_98_PTYS_ONLY__ was not set and both systems are 
activated. In uClibc 0.9.19 the revision of ptsname.c we have is 5747.

I also checked the major and minor number of /dev/pts/0, (major: 
136/minor: 0), /dev/ptmx (major: 5/minor: 2). They seem to be ok.

Any idea what goes wrong?

Roman

Erik Andersen wrote:

>On Thu Aug 18, 2005 at 01:50:45PM +0200, Maillists wrote:
>  
>
>>Hi everyone
>>
>>We run a uClinux 2.4.22 system with uClibc 0.9.19 and I have problems 
>>accessing the pty devices with the functions getpt / ttyname / openpty.
>>The distribution we have sets the pty path to /dev/pty/m* and 
>>/dev/pty/s* and seems to be the "new" naming style.
>>    
>>
>
>Why not mount and use the /dev/pts virtual filesystem?  It works
>wonderfully and is the preferred method of doing things....
>
> -Erik
>
>--
>Erik B. Andersen             http://codepoet-consulting.com/
>--This message was written using 73% post-consumer electrons--
>
>
>  
>