Hello, I'm hoping someone has some experience with this and can offer some advice. I have several environments in which I am using Thin Clients as terminal emulators to Red Hat servers. I have been deploying Thin Clients for the past few years to replace old WYSE dumb terminals. One problem I am having is that the dumb terminals were serial so they were on a specific tty port. The Thin Clients however connect on the first available pts port, I really don't have control over the port each Thin Client connects on, other then possibly making sure they are always started in a certain order, which isn't a feasible option. What I am wondering is if anyone knows a way to control which pts port a thin client connects on; I'm guessing it would have to be by hostname or IP, I just can't figure out how. Any advice is appreciated.

Thanks,

Probably the best way to define your pts ports is to use the modprobe.conf file and allocate a hostname to each pts port similar to how alsa defines sound cards. This is what I had to do when I had multiple ethernet ports and I wanted eth0 assigned to the ISP. Another suggestion is using udev rules, its probably cleaner.