OpenWrt Forum Archive

Topic: net2kiss and ptys

The content of this topic has been archived on 18 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I'm trying to use net2kiss to do some ax.25 plumbing. I can't seem to figure out how it wants to name ptys, and don't really understand what White Russian does with the master/slave pairs.

When I look in /dev/pty, I see a zillion files. When I look in /dev/pts, I only see a few, and they're named differently.

I've read about /dev/ptmx. As best I can tell, the net2kiss that is compiled for the WRT doesn't understand this convention/mechanism. Is there some utility I can use to create the ptys I need and pass them around to the programs that need them?

Thanks.

Or ... is there some way to get OpenWRT to use old-style ptys? Does WhiteRussian have "legacy pty" support turned on? Is there a MAKEDEV that will create them?

(Last edited by cak on 18 Jul 2007, 22:53)

Well, it turns out that the ax.25 kernel I was using had legacy pty support turned on, but no devices made.

For posterity:

Google knows everything, if you look hard enough.

I finally found

http://www.lanana.org/docs/device-list/devices.txt

which told me how the legacy pty devices are numbered and named.
With that in hand, I can

# makedevs /dev/ptyp c 2 0 0 8
# makedevs /dev/ttyp c 3 0 0 8
# cat < /dev/ptyp0 &
# echo hi > /dev/ttyp0
hi
# cat: Read error: Input/output error

So that all works. On to the next problems!

The discussion might have continued from here.