Hi,

When connecting a serial terminal or emulation program to a SCO system, it is
/dev/tty1a for example, or /dev/ttya3 if it's on a terminal adapter.

Moving to Enterprise, with terminals now connecting via telnet, they are
designated /dev/ttyp0, p1 etc depending on the order they login.

Is there a way to "reserve" port designations, and force for example terminal
192.168.0.10 to always connect as /dev/ttyp0, terminal 192.168.0.11 to always
connect as /dev/ttyp1 etc etc.

many thanks


-Rob
robatwork at mail dot com

On Thu, 10 Jun 2004 15:54:49 +0100, Rob S
<robatworkDeleteTheseFourWords@mail.com> wrote:

>Hi,
>
>When connecting a serial terminal or emulation program to a SCO system, it is
>/dev/tty1a for example, or /dev/ttya3 if it's on a terminal adapter.
>
>Moving to Enterprise, with terminals now connecting via telnet, they are
>designated /dev/ttyp0, p1 etc depending on the order they login.
>
>Is there a way to "reserve" port designations, and force for example terminal
>192.168.0.10 to always connect as /dev/ttyp0, terminal 192.168.0.11 to always
>connect as /dev/ttyp1 etc etc.
>
>many thanks
>
>
>-Rob
>robatwork at mail dot com

A couple of possibilities to mull over:
http://aplawrence.com/SCOFAQ/scotec2.html#specifictty
http://tinyurl.com/25mge

Perhaps explaining *why* you want to force specific IPs to specific
ttyps would elicit additional responses/solutions.


Scott McMillan

Rob S <robatworkDeleteTheseFourWords@mail.com> wrote in message news:<40c873e5.111997654@giganews.nildram.co.uk>.. .
> Hi,
>
> When connecting a serial terminal or emulation program to a SCO system, it is
> /dev/tty1a for example, or /dev/ttya3 if it's on a terminal adapter.
>
> Moving to Enterprise, with terminals now connecting via telnet, they are
> designated /dev/ttyp0, p1 etc depending on the order they login.
>
> Is there a way to "reserve" port designations, and force for example terminal
> 192.168.0.10 to always connect as /dev/ttyp0, terminal 192.168.0.11 to always
> connect as /dev/ttyp1 etc etc.
>
> many thanks
>
>
> -Rob
> robatwork at mail dot com

No , is not possible as far as I know.

But you can know the IP of this session typing

who -ux

with older system I had some automatic process based on $TTY , now I
use for the same purpose :

HOST=`who -mx | awk '{print$6}'` ; export HOST

Rob S enscribed:
|
| When connecting a serial terminal or emulation program to a SCO system, it is
| /dev/tty1a for example, or /dev/ttya3 if it's on a terminal adapter.
|
| Moving to Enterprise, with terminals now connecting via telnet, they are
| designated /dev/ttyp0, p1 etc depending on the order they login.
|
| Is there a way to "reserve" port designations, and force for example terminal
| 192.168.0.10 to always connect as /dev/ttyp0, terminal 192.168.0.11 to always
| connect as /dev/ttyp1 etc etc.

I suspect this isn't the real question, so I'll ask why do you want to
do this? And what is the application that appears to insist on this.

--
================================================== ========================
Tom Parsons tom@tegan.com
================================================== ========================

Rob S wrote:
> Hi,
>
> When connecting a serial terminal or emulation program to a SCO system, it is
> /dev/tty1a for example, or /dev/ttya3 if it's on a terminal adapter.
>
> Moving to Enterprise, with terminals now connecting via telnet, they are
> designated /dev/ttyp0, p1 etc depending on the order they login.
>
> Is there a way to "reserve" port designations, and force for example terminal
> 192.168.0.10 to always connect as /dev/ttyp0, terminal 192.168.0.11 to always
> connect as /dev/ttyp1 etc etc.
>
> many thanks
>
>
> -Rob
> robatwork at mail dot com

Many moons ago, someone posted the following:

=== cut here === 8< ===

A few years ago someone suggested using mscreen to solve this
problem of fixed ttys for network logins. You might be able to
locate it via deja.com.

In theory it would work like this:

you log in and the .profile includes the following
tty=`tty`
tty=`basename $tty`
myhost=`who -x|grep $tty|awk '{print $6}'`
HOME=/usr/mscreen/$myhost
cd $HOME
exec mscreen -n 1

you need to create the /usr/mscreen/<ip addresses> directories
with the file .mscreenrc in it. This file contains the pseudo
tty you wish to use. You can also add some checking to see if
$myhost is listed more than once in the result of the who -x
command.

I have not tested this yet so proceed with caution.

=== cut here === 8< ===

Also, under SCO 5.0.6+ you can use the "recon" utility as to run an
application on a specific tty.

Hope this helps !

Best,
Rob (the other one)