From 12fe473981990f1422e621e942f4acafa3667686 Mon Sep 17 00:00:00 2001 From: jkh Date: Mon, 29 Jul 1996 07:15:57 +0000 Subject: 1. Add some missing mailing lists. [jkh] 2. Make the sup documentation more readable. [jkh] 3. Add new handbook section on terminals. Submitted-By: Sean Kelly --- share/doc/handbook/Makefile | 8 +- share/doc/handbook/eresources.sgml | 5 +- share/doc/handbook/handbook.sgml | 4 +- share/doc/handbook/sections.sgml | 3 +- share/doc/handbook/term.sgml | 539 +++++++++++++++++++++++++++++++++++++ 5 files changed, 551 insertions(+), 8 deletions(-) create mode 100644 share/doc/handbook/term.sgml diff --git a/share/doc/handbook/Makefile b/share/doc/handbook/Makefile index 56cdeac..f62774c 100644 --- a/share/doc/handbook/Makefile +++ b/share/doc/handbook/Makefile @@ -1,4 +1,4 @@ -# $Id: Makefile,v 1.14 1996/06/30 18:01:23 phk Exp $ +# $Id: Makefile,v 1.15 1996/07/02 23:16:14 wosch Exp $ SRCS= authors.sgml basics.sgml bibliography.sgml boothelp.sgml SRCS+= booting.sgml contrib.sgml crypt.sgml ctm.sgml current.sgml @@ -9,8 +9,8 @@ SRCS+= handbook.sgml history.sgml hw.sgml install.sgml isdn.sgml kerberos.sgml SRCS+= kernelconfig.sgml kerneldebug.sgml memoryuse.sgml SRCS+= mirrors.sgml nfs.sgml nutshell.sgml pgpkeys.sgml policies.sgml SRCS+= porting.sgml ports.sgml ppp.sgml printing.sgml quotas.sgml relnotes.sgml -SRCS+= routing.sgml scsi.sgml sections.sgml sio.sgml -SRCS+= skey.sgml slipc.sgml slips.sgml stable.sgml submitters.sgml sup.sgml -SRCS+= synching.sgml troubleshooting.sgml userppp.sgml uart.sgml linuxemu.sgml +SRCS+= routing.sgml scsi.sgml sections.sgml sio.sgml skey.sgml slipc.sgml +SRCS+= slips.sgml stable.sgml submitters.sgml sup.sgml synching.sgml +SRCS+= term.sgml troubleshooting.sgml userppp.sgml uart.sgml linuxemu.sgml .include diff --git a/share/doc/handbook/eresources.sgml b/share/doc/handbook/eresources.sgml index edc7ebf..3893e03 100644 --- a/share/doc/handbook/eresources.sgml +++ b/share/doc/handbook/eresources.sgml @@ -1,4 +1,4 @@ - + @@ -67,11 +67,13 @@ freebsd-emulation Emulation of other systems such as Linux/DOS/Windows freebsd-fs Filesystems freebsd-hackers General technical discussion freebsd-hardware General discussion of hardware for running FreeBSD +freebsd-mobile Discussions about mobile computing freebsd-multimedia Multimedia discussion freebsd-platforms Concerning ports to non-Intel architecture platforms freebsd-ports Discussion of the ports collection freebsd-security Security issues freebsd-scsi The SCSI subsystem +freebsd-smp Design discussions for [A]Symmetric MultiProcessing Limited lists: The following lists require approval to join, @@ -84,6 +86,7 @@ List Purpose freebsd-admin Administrative issues freebsd-arch Architecture and design discussions freebsd-core FreeBSD core team +freebsd-hubs People running mirror sites (infrastructural support) freebsd-install Installation development freebsd-user-groups User group coordination diff --git a/share/doc/handbook/handbook.sgml b/share/doc/handbook/handbook.sgml index 21d8cbd..659706f 100644 --- a/share/doc/handbook/handbook.sgml +++ b/share/doc/handbook/handbook.sgml @@ -1,4 +1,4 @@ - + or one of the numerous Basic Networking * Ethernet basics * Serial basics - * Hardwired Terminals + &term; &dialup; PPP and SLIP diff --git a/share/doc/handbook/sections.sgml b/share/doc/handbook/sections.sgml index e9ce2aa..a289ac1 100644 --- a/share/doc/handbook/sections.sgml +++ b/share/doc/handbook/sections.sgml @@ -1,4 +1,4 @@ - + @@ -23,6 +23,7 @@ + diff --git a/share/doc/handbook/term.sgml b/share/doc/handbook/term.sgml new file mode 100644 index 0000000..4b708c5 --- /dev/null +++ b/share/doc/handbook/term.sgml @@ -0,0 +1,539 @@ + + +Terminals + +

Contributed by &a.kelly;28 July 1996 + + Terminals provide a convenient and low-cost way to access the + power of your FreeBSD system when you are not at the computer's + console or on a connected network. This section describes how + to use terminals with FreeBSD. + + Uses and Types of Terminals + +

The original Unix systems did not have consoles. Instead, + people logged in and ran programs through terminals that were + connected to the computer's serial ports. It is quite similar + to using a modem and some terminal software to dial into a + remote system to do text-only work. + + Today's PCs have consoles capable of high quality graphics, + but the ability to establish a login session on a serial port + still exists in nearly every Unix-style operating system + today; FreeBSD is no exception. By using a terminal attached + to a unused serial port, you can log in and run any text + program that you would normally run on the console or in an + + + + + + + The remaining subsections describe each kind. + + Dumb Terminals + +

Dumb terminals are specialized pieces of hardware that let + you connect to computers over serial lines. They are called + ``dumb'' because they have only enough computational power + to display, send, and receive text. You cannot run any + programs on them. It is the computer to which you connect + them that has all the power to run text editors, compilers, + email, games, and so forth. + + There are hundreds of kinds of dumb terminals made by + many manufacturers, including Digital Equipment + Corporation's VT-100 and Wyse's WY-75. Just about any kind + will work with FreeBSD. Some high-end terminals can even + display graphics, but only certain software packages can + take advantage of these advanced features. + + Dumb terminals are popular in work environments where + workers do not need access to graphic applications such as + those provided by the X window system. + + PCs Acting As Terminals + +

If a has just + enough ability to display, send, and receive text, then + certainly any spare personal computer can be a dumb + terminal. All you need is the proper cable and some + X Terminals + +

X terminals are the most sophisticated kind of terminal + available. Instead of connecting to a serial port, they + usually connect to a network like Ethernet. Instead of + being relegated to text-only applications, they can display + any X application. + + We introduce X terminals just for the sake of completeness. + However, this chapter does Cables and Ports + +

To connect a terminal to your FreeBSD system, you need the + right kind of cable and a serial port to which to connect it. + This section tells you what to do. If you are already + familiar with your terminal and the cable it requires, skip to + . + + Cables + +

Because terminals use serial ports, you need to use + serial---also known as RS-232C---cables to connect the + terminal to the FreeBSD system. + + There are a couple of kinds of serial cables. Which one + you'll use depends on the terminal you want to connect: + + + If you are connecting a personal computer to act as + a terminal, use a + cable. A null-modem cable connects two computers or + terminals together. + + If you have an actual terminal, your best source of + information on what cable to use is the documentation + that accompanied the terminal. If you do not have the + documentation, then try a cable. If that does not work, then try + a cable. + + + Also, the serial port on Null-modem cables + +

A null-modem cable passes some signals straight through, + like ``signal ground,'' but switches other signals. For + example, the ``send data'' pin on one end goes to the + ``receive data'' pin on the other end. + + If you like making your own cables, here is a table + showing a recommended way to construct a null-modem cable + for use with terminals. This table shows the RS-232C + signal names and the pin numbers on a DB-25 connector. + + Signal Pin# Pin# Signal + TxD 2 ----------------------- 3 RxD + RxD 3 ----------------------- 2 TxD + DTR 20 ----------------------- 6 DSR + DSR 6 ----------------------- 20 DTR + SG 7 ----------------------- 7 SG + DCD 8 ----------------------+ 4 RTS* + *RTS 4 + + 5 CTS* + *CTS 5 +---------------------- 8 DCD + +* Connect pins 4 to 5 internally in the connector hood, and then to + pin 8 in the remote hood. + + + Standard RS-232C Cables + +

A standard serial cable passes all the RS-232C signals + straight-through. That is, the ``send data'' pin on one + end of the cable goes to the ``send data'' pin on the + other end. This is the type of cable to connect a modem + to your FreeBSD system, and the type of cable needed for + some terminals. + + Ports + +

Serial ports are the devices through which data is + transferred between the FreeBSD host computer and the + terminal. This section describes the kinds of ports that + exist and how they are addressed in FreeBSD. + + Kinds of Ports + +

Several kinds of serial ports exist. Before you purchase + or construct a cable, you need to make sure it will fit + the ports on your terminal and on the FreeBSD system. + + Most terminals will have DB25 ports. Personal computers, + including PCs running FreeBSD, will have DB25 or DB9 + ports. If you have a multiport serial card for your PC, + you may have RJ-12 or RJ-45 ports. + + See the documentation that accompanied the hardware for + specifications on the kind of port in use. A visual + inspection of the port often works, too. + + Port Names + +

In FreeBSD, you access each serial port through an entry + in the /dev directory. There are two different + kinds of entries: + + Callin ports are named /dev/ttyd + where Callout ports are named /dev/cuaa. + You usually do not use the callout port for terminals, + just for modems. You may use the callout port if the + serial cable or the terminal does not support the + carrier detect signal. + + + See the sio(4) manual page for more information. + + If you have connected a terminal to the first serial port + (COM1 in DOS parlance), then you want to use + /dev/ttyd0 to refer to the terminal. If it is on + the second serial port (also known as COM2), it is + /dev/ttyd1, and so forth. + + Note that you may have to configure your kernel to support + each serial port, especially if you have a mutliport + serial card. See for more information. + + Configuration + +

This section describes what you need to configure on your + FreeBSD system to enable a login session on a terminal. It + assumes you have already configured your kernel to support the + serial port to which the terminal is connected---and that you + have connected it. + + In a nutshell, you need tell the /etc/ttys file. + First, use the /etc/ttys: + + Add an line to /etc/ttys for the entry in the + /dev directory for the serial port if it is not + already there. + + Specify that /usr/libexec/getty be run on the + port, and specify the appropriate /etc/gettytab file. + + Specify the default terminal type. + + Set the port to ``on.'' + + Specify whether the port should be ``secure.'' + + Force /etc/ttys file. + + + As an optional step, you may wish to create a custom + /etc/gettytab. This document does not explain how to + do so; you are encouraged to see the gettytab(5) and the + getty(8) manual pages for more information. + + The remaining sections detail how to do these steps. We will + use a running example throughout these sections to illustrate + what we need to do. In our example, we will connect two + terminals to the system: a Wyse-50 and a old 286 IBM PC + running Procomm terminal software emulating a VT-100 terminal. + We connect the Wyse to the second serial port and the 286 to + the sixth serial port (a port on a multiport serial card). + + For more information on the /etc/ttys file, see the + ttys(5) manual page. + + Adding an Entry to /etc/ttys +

First, you need to add an entry to the /etc/ttys + file, unless one is already there. + + The /etc/ttys file lists all of the ports on your + FreeBSD system where you want to allow logins. For example, + the first virtual console ttyv0 has an entry in + this file. You can log in on the console using this entry. + This file contains entries for the other virtual consoles, + serial ports, and pseudo-ttys. For a hardwired terminal, + just list the serial port's /dev entry without the + /dev part. + + When you installed your FreeBSD system, the + /etc/ttys file included entries for the first four + serial ports: /etc/ttys file + after we add the new entry: + +ttyd1 "/usr/libexec/getty std.9600" unknown off secure +ttyd5 + + + Specifying the +

Next, we need to specify what program will be run to handle + the logins on a terminal. For FreeBSD, the standard program + to do that is /usr/libexec/getty. It is what + provides the login: prompt. + + The program /etc/gettytab. + + The file /etc/gettytab contains lots of entries for + terminal lines both old and new. In almost all cases, the + entries that start with the text /etc/ttys + file, make sure that the communications settings on the + terminal match. + + For our example, the Wyse-50 uses no parity and connects at + 38400 bps. The 286 PC uses no parity and connects at 19200 + bps. Here is the /etc/ttys file so far (showing + just the two terminals in which we are interested): + +ttyd1 "/usr/libexec/getty std.38400" unknown off secure +ttyd5 "/usr/libexec/getty std.19200" + + Note that the second field---where we specify what program + to run---appears in quotes. This is important, otherwise + the type argument to Specifying the Default Terminal Type + +

The third field in the /etc/ttys file lists the + default terminal type for the port. For dialup ports, you + typically put /etc/ttys file, users can forego such + prompting. + + To find out what terminal types FreeBSD supports, see the + file /usr/share/misc/termcap. It lists about 600 + terminal types. You can add more if you wish. See the + termcap(5) manual page for information. + + In our example, the Wyse-50 is a Wyse-50 type of terminal + (although it can emulate others, we will leave it in Wyse-50 + mode). The 286 PC is running Procomm which will be set to + emulate a VT-100. Here are the pertinent yet unfinished + entries from the /etc/ttys file: + +ttyd1 "/usr/libexec/getty std.38400" wy50 off secure +ttyd5 "/usr/libexec/getty std.19200" vt100 + + + Enabling the Port +

The next field in /etc/ttys, the fourth field, + tells whether to enable the port. Putting /etc/ttys file. We have turned each + port +ttyd1 "/usr/libexec/getty std.38400" wy50 on secure +ttyd5 "/usr/libexec/getty std.19200" vt100 on + + + + Specifying Secure Ports +

We have arrived at the last field (well, almost: there is + an optional /etc/ttys file, with comments added to describe + where the terminals are: + +ttyd1 "/usr/libexec/getty std.38400" wy50 on insecure # Kitchen +ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom + + + Force /etc/ttys +

When you boot FreeBSD, the first process, /etc/ttys file and start the programs + listed for each enabled port to prompt for logins. + + After you edit /etc/ttys, you do not want to have + to reboot your system to get /etc/ttys if it receives + a SIGHUP (hangup) signal. + + So, after you have saved your changes to /etc/ttys, + send SIGHUP to +kill -HUP 1 + + (The Debugging your connection +

Even with the most meticulous attention to detail, something + could still go wrong while setting up a terminal. Here is a + list of symptoms and some suggested fixes. + + + +ps -axww|grep getty + + to get a list of running +22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1 + + shows that a /etc/gettytab. + + If no /etc/ttys. Make sure you + have run /etc/ttys and run + + + -- cgit v1.1