lat_manual_setup man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

lat_manual_setup(7)					   lat_manual_setup(7)

       lat_manual_setup	 -  Describes  how  to	manually set up the Local Area
       Transport (LAT)

       To run LAT on your system, you must configure LAT in your system's ker‐
       nel (see the Network Administration: Connections manual).

       Optionally, you can customize your LAT setup. The customization section
       of the Network Administration: Connections manual includes  information
       on  general  customization, setting up printers, host-initiated connec‐
       tions, the LAT/Telnet gateway, and creating your own service.

       To set up LAT on your system manually, you must	first  configure  your
       kernel  for  LAT	 (see the Network Administration: Connections manual).
       Then log in as superuser and perform the following  steps:  Create  the
       LAT device special files.

	      LAT  supports  SVR4-style	 and BSD-style devices. You should use
	      SVR4-style devices. See the Network Administration:  Connections
	      manual for more information.


	      You should use the latsetup utility to create SVR4-style devices
	      to ensure that duplicate minor numbers are not used.

	      You can use the mknod command to create character devices with a
	      major  number  of	 5.   If you create SVR4 devices manually, you
	      should observe the following rules: Start the SVR4  device  num‐
	      bers  at	/dev/lat/620.	This  avoids overlapping minor numbers
	      from the BSD tty name space.  Make the minor number of the  SVR4
	      device  the  same as the name.  For example, device /dev/lat/833
	      should have minor number 833.  The following command would  cre‐
	      ate  the	SVR4-style  LAT device /dev/lat/833: # /usr/sbin/mknod
	      /dev/lat/833 c 5 833

	      Once you have created the SVR4-style device, check  the  permis‐
	      sions of the device to make sure they are what you desire.

	      You  can	create	BSD-style  devices by running the /dev/MAKEDEV
	      script with the LAT option. The syntax for the  MAKEDEV  command
	      with the LAT option is as follows: MAKEDEV latN

	      The N variable can be 0 to 38.

	      The /dev/MAKEDEV script creates one BSD-style LAT device special
	      file for each LAT terminal device.  When	you  run  the  MAKEDEV
	      script,  it  creates  16 BSD-style LAT device special files, and
	      creates the LAT control device (/dev/streams/lat), if it has not
	      already been created.  The MAKEDEV script requires 16 contiguous
	      LAT device special files to  be  available.   (Specifying	 lat38
	      requires	only  12  contiguous  LAT  device  special files to be

	      For example, the following commands create a total  of  32  BSD-
	      style  LAT  device  special  files:  #  cd /dev # MAKEDEV lat0 #
	      MAKEDEV lat1

	      Record the device special	 file  information  displayed  by  the
	      MAKEDEV  script.	 The  special file names vary depending on the
	      number of terminal devices already configured.

	      The following is sample output from the MAKEDEV command:

	      MAKEDEV: special file(s) for lat1: tty16 tty17 tty18 tty19 tty1a
	      tty1b  tty1c  tty1d  tty1e  tty1f	 tty1g tty1h tty1i tty1j tty1k
	      tty1l Edit the /etc/inittab file to include entries for the  LAT
	      device special files you created.	 For example:

	      lat620:34:respawn:/usr/sbin/getty	  /dev/lat/620	 console vt100
	      lat621:34:respawn:/usr/sbin/getty	   lat/621    console	 vt100
	      lat630:34:respawn:/usr/sbin/lattelnet lat/630 lattelnet

	      The  second field (34) specifies the run levels at which the LAT
	      devices are spawned; in  this  example,  the  getty  process  is
	      spawned  at  either  run	level  3 or 4. The first entry uses an
	      absolute pathname for the	 device	 (/dev/lat/620).   The	second
	      uses a relative pathname (lat/621).

	      The  previous example shows how to add entries to the /etc/init‐
	      tab file for SVR4	 LAT  devices.	The  following	example	 shows
	      entries for BSD LAT devices:

	      lat16:34:respawn:/usr/sbin/getty	   tty16     console	 vt100
	      lat17:34:respawn:/usr/sbin/getty	   tty17     console	 vt100
	      lat18:34:respawn:/usr/sbin/lattelnet tty18 lattelnet18

	      For  more information, see the inittab(4) and getty(8) reference
	      pages.  The Network Administration: Connections manual  provides
	      additional information on SVR4 and BSD devices.  Use the follow‐
	      ing command to spawn the processes for the  LAT  device  special
	      files  that  you	added to the /etc/inittab file: # /sbin/init q
	      Create the STREAMS special file required by LAT by  issuing  the
	      following	 command: # /usr/sbin/strsetup -i Enable LAT automatic
	      startup  and  shutdown  by  using	 the  following	  command:   #
	      /usr/sbin/rcmgr set LAT_SETUP 1

	      When   LAT  automatic  startup  and  shutdown  is	 enabled,  the
	      /sbin/init.d/lat file automatically starts LAT upon reaching run
	      level  3	and  automatically stops LAT when exiting run level 3.
	      Start LAT by issuing the following command: # /usr/sbin/latcp -s

       Commands: llogin(1),  netstat(1),  getty(8),  init(8),  latcp(8),  lat‐
       setup(8), MAKEDEV(8), mknod(8), rcmgr(8), strsetup(8)

       Files: inittab(4)

       Introduction: lat_intro(7)

       Network Administration: Connections, System Administration


List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net