Installation guide

pty1 pseudoterminals have corresponding device special
files named /dev/ttyq0 through /dev/ttyqf.
If you add pseudoterminals to your system, the pty # variable must be
higher than pty1 because the installation software sets pty0 and
pty1. For example, to create device special files for a third set of
pseudoterminals, enter:
# ./MAKEDEV pty2
The MAKEDEV command lists the device special files it has created. For
example:
MAKEDEV: special file(s) for pty2:
ptyr0 ttyr0 ptyr1 ttyr1 ptyr2 ttyr2 ptyr3 ttyr3 ptyr4 ttyr4
ptyr5 ttyr5 ptyr6 ttyr6 ptyr7 ttyr7 ptyr8 ttyr8 ptyr9 ttyr9
ptyra ttyra ptyrb ttyrb ptyrc ttyrc ptyrd ttyrd ptyre ttyre
ptyrf ttyrf
6. If you want to allow root logins on all pseudoterminals, make sure an
entry for ptys is present in the /etc/securettys file. If you do not
want to allow root logins on pseudoterminals, delete the entry for ptys
from the /etc/securettys file. For example (using the sample
output shown in step 5), to add the entries for the new tty lines and to
allow root login on all pseudoterminals, enter the following lines in the
/etc/securettys file:
/dev/tty08 # direct tty
/dev/tty09 # direct tty
/dev/tty10 # direct tty
/dev/tty11 # direct tty
ptys
Refer to the securettys(4) reference page for more information.
The pty name space in SVR4 systems is defined as follows:
/dev/pts/
N
The variable N is a number from 0-9999.
This name space allows for more scalability than the BSD pty name space
(tty[a-zA-Z][0-9a-zA-Z]). The base system commands and utilities have been
modified to support both SVR4 and BSD pty name spaces. For binary
compatibility reasons, the default is the BSD name space. You can alter
this behavior by using the SYSV_PTY
(8) command. The invocation of the
SVS_PTY command results in using the SVR4 name space as the default.
To revert back to the original default behavior (BSD pty name space),
create the BSD ptys as discussed in Section 6.4.1.
6–6 Administering Devices with Dynamic Device Recognition