Have a Question?

00220: How to setup the CONFIG.BBX file for pseudo tty’s


How to setup the CONFIG.BBX file for pseudo tty’s


Here is a way to get around the tty dependency when using pseudo ttys: 

1) Use an alias line similar to: 
        alias T0 /dev/tty term 
2) Set your TERM environment variable to reflect your terminal type. Example: 
        TERM=ansicoe;export TERM 
3) Set your TERMCAP environment variable to point to the termcap file. Example: 
        TERMCAP=/usr/bbx/termcap;export TERMCAP 
4) Set your BBTERM environment variable to point to the desired alias line. Example: 
        BBTERM=T0; export BBTERM 
        An alternate method would be to force BBx to pick a specific alias line. Example: 
        bbx4 -tT5 
5) Run bbx 

This way, BBx will grab the alias line pointed to by the BBTERM environment variable. It will then see the generic ‘/dev/tty’ component, and use *whatever* tty you are currently on. (You can do a ./pro5 -r to find out what tty BBx thinks you are on–this is similar to the Unix ‘tty’ command). Then, it will see the generic ‘term’ component, and use the TERM and TERMCAP information to find out your terminal type and how to talk to it. 

1) This allows you the option of having only a few alias lines in the config.bbx file, one for each user. This is preferred over an alias line for every valid tty device defined on your system, which can be over 600! 

2) Some software requires users to have a unique FID(0), or terminal alias, in order to create unique temporary files. Therefore, if your software has this requirement, ensure that each user has their own terminal alias line. 

3) To test the setup enter: grep $TERM $TERMCAP. This will search the termcap entry and will show the entry for the term variable. 

Last Modified: 12/22/1997 Product: PRO/5 Operating System: Unix

BASIS structures five components of their technology into the BBx Generations.

Table of Contents
Scroll to Top