latsetup(8)latsetup(8)NAMElatsetup - Local Area Transport (LAT) setup utility
Specifies that latsetup is run in noncurses and nonmenu-driven mode.
Use this option if the terminal you are using does not support curses.
Note that using the latsetup command with the -nocurses option
provides limited functionality.
The latsetup command provides an interactive, menu-driven facility for
administrating LAT on your system. (For introductory information on
LAT, see the lat_intro(7) reference page.)
To use latsetup, LAT must be built into the running kernel, your system
must be at run level 3 or 4, and you must be logged in as superuser.
For more information, see the Network Administration: Connections man‐
Running multiple latsetup processes concurrently on the same machine
can cause erroneous information to be presented to the latsetup user
and can corrupt the /etc/inittab file.
You can use the latsetup utility to perform the following tasks: Do
initial LAT setup Create LAT device special files Add or delete getty
entries to or from the /etc/inittab file Execute init q Start or stop
the LAT driver Enable or disable LAT automatic startup and shutdown
If LAT is not configured into the running kernel, latsetup only allows
you to remove the LAT entries from the /etc/inittab file.
If you enable LAT automatic startup and shutdown, the /sbin/init.d/lat
script starts LAT upon reaching run level 3 and stops LAT upon leaving
run level 3.
To run latsetup, log in as superuser and enter the following command: #
LAT is not supported over NetRAIN virtual interfaces or the adapters
that compose NetRAIN sets. The latsetup utility does not allow you to
configure LAT over these interfaces, and you should not attempt to do
In the device creation phase, you choose to create SVR4-style or BSD-
style devices. (For an explanation of the types of devices, see the
Network Administration: Connections manual.) You should use SVR4-style
devices; they allow a larger number of devices.
If you create SVR4 devices using latsetup, and an SVR4 device was
mapped as an application port and the device was removed, the port (or
service) information remains associated with the minor number corre‐
sponding to the device that was removed. Therefore, when latsetup cre‐
ates more devices, it may create the device that was mapped as an
application port (if the device name is within the range of SVR4
devices being created). The latsetup utility does not add a getty
entry for the device in the /etc/inittab file. This device is not
counted as a newly created SVR4 device, because it is already being
used as an application port.
If you delete SVR4 devices using latsetup, and an SVR4 device was
mapped as an application port and has an associated getty entry in the
inittab file, if the device name is within the range of SVR4 devices
being removed, latsetup removes the associated getty entry in the
/etc/inittab file. When removing SVR4 devices, latsetup does not remove
the device, because it is mapped as an application port. This device
is not counted as an SVR4 device that has been removed.
The latsetup utility creates device names that directly correspond to
minor numbers (for example, SVR4 device /dev/lat/620 corresponds to
minor number 620).
After you run latsetup, you can customize your system's LAT environment
by modifying the following files: /etc/inittab
Edit the /etc/inittab file to add any LAT entries. For example,
you can add an entry for the LAT/Telnet gateway. For more
information refer to the Network Administration: Connections
manual and inittab(4).
If you delete entries in the /etc/inittab file and then run lat‐
setup to make other changes or deletions, latsetup might not be
able to complete successfully. /etc/latstartup.conf
Create and modify the /etc/latstartup.conf file to include latcp
commands to customize your LAT system. This file is read by the
/sbin/init.d/lat script, which executes the commands included in
the file. For example, you can change the LAT node name or add
additional service names.
If your system is a member of a cluster, you must create this
file as a Context-Dependent Symbolic Link (CDSL). See the System
Administration guide for more information.
For more information refer to the Network Administration: Connections
manual and latcp(8).
Specifies the BSD LAT terminal devices. (Where W is a number from 0 to
9 and X is an alphanumeric character from 0 to 9, a lowercase a to z,
or an uppercase A to Z.) LAT supports up to 620 BSD LAT terminal
devices. Specifies the SVR4 LAT device special files. (Where n is a
number starting at 620 and having no upper limit.) Specifies the LAT
control device. Specifies the LAT startup and shutdown script. Speci‐
fies LAT customization commands. If your system is a member of a clus‐
ter, you must create this file as a Context-Dependent Symbolic Link
(CDSL). See the System Administration guide for more information. Sets
up the system database to automatically push the ldterm STREAMS module
on top of the LAT STREAMS driver each time a LAT tty is opened. Con‐
trols the initialization process. Specifies the system configuration
Commands: llogin(1), init(8), latcp(8), MAKEDEV(8), strsetup(8)
Introduction: lat_intro(7), lat_manual_setup(7)
Network Administration: Connections