From owner-svn-doc-head@FreeBSD.ORG Mon Jan 28 15:15:46 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E9129E6E; Mon, 28 Jan 2013 15:15:46 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DB52425E; Mon, 28 Jan 2013 15:15:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0SFFkNJ014073; Mon, 28 Jan 2013 15:15:46 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0SFFkvV014072; Mon, 28 Jan 2013 15:15:46 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301281515.r0SFFkvV014072@svn.freebsd.org> From: Dru Lavigne Date: Mon, 28 Jan 2013 15:15:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40783 - head/en_US.ISO8859-1/books/handbook/serialcomms X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:15:47 -0000 Author: dru Date: Mon Jan 28 15:15:46 2013 New Revision: 40783 URL: http://svnweb.freebsd.org/changeset/doc/40783 Log: White space fix only. Translators can ignore. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Mon Jan 28 15:14:36 2013 (r40782) +++ head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Mon Jan 28 15:15:46 2013 (r40783) @@ -13,12 +13,13 @@ serial communications - &unix; has always had support for serial communications. In fact, - the very first &unix; machines relied on serial lines for user input - and output. Things have changed a lot from the days when the average - terminal consisted of a 10-character-per-second serial - printer and a keyboard. This chapter will cover some of the ways in - which FreeBSD uses serial communications. + &unix; has always had support for serial communications. In + fact, the very first &unix; machines relied on serial lines for + user input and output. Things have changed a lot from the days + when the average terminal consisted of a + 10-character-per-second serial printer and a keyboard. This + chapter will cover some of the ways in which FreeBSD uses serial + communications. After reading this chapter, you will know: @@ -52,9 +53,9 @@ linkend="basics"/>). - Have access to the technical manual for the serial hardware - (modem or multi-port card) that you would like to use with - FreeBSD. + Have access to the technical manual for the serial + hardware (modem or multi-port card) that you would like to + use with FreeBSD. @@ -103,7 +104,8 @@ DCE - Data Communications Equipment — your modem + Data Communications Equipment — your + modem @@ -113,7 +115,8 @@ RS-232C cables - EIA standard for hardware serial communications + EIA standard for hardware serial + communications @@ -122,18 +125,18 @@ does not use the term baud. Baud refers to the number of electrical state transitions that may be made in a period of time, while bps (bits per second) is - the correct term to use (at least it does not - seem to bother the curmudgeons quite as much). + the correct term to use (at least it does + not seem to bother the curmudgeons quite as much). Cables and Ports To connect a modem or terminal to your FreeBSD system, you - will need a serial port on your computer and the proper cable to - connect to your serial device. If you are already familiar with your - hardware and the cable it requires, you can safely skip this - section. + will need a serial port on your computer and the proper cable + to connect to your serial device. If you are already familiar + with your hardware and the cable it requires, you can safely + skip this section. Cables @@ -141,8 +144,8 @@ There are several different kinds of serial cables. The two most common types for our purposes are null-modem cables and standard (straight) RS-232 cables. The - documentation for your hardware should describe the type of cable - required. + documentation for your hardware should describe the type of + cable required. Null-modem Cables @@ -152,20 +155,21 @@ A null-modem cable passes some signals, such as - Signal Ground, straight through, but switches other - signals. For example, the Transmitted Data pin on - one end goes to the Received Data pin on the other - end. - - You can also construct your own null-modem cable for use with - terminals (e.g., for quality purposes). This table shows the - RS-232C signals - and the pin numbers on a DB-25 connector. Note that the standard - also calls for a straight-through pin 1 to pin 1 - Protective Ground line, but it is often - omitted. Some terminals work OK using only pins 2, 3 and 7, - while others require different configurations than the examples - shown below. + Signal Ground, straight through, but + switches other signals. For example, the + Transmitted Data pin on one end goes to the + Received Data pin on the other end. + + You can also construct your own null-modem cable for + use with terminals (e.g., for quality purposes). This + table shows the RS-232C signals + and the pin numbers on a DB-25 connector. Note that the + standard also calls for a straight-through pin 1 to pin 1 + Protective Ground line, but it is + often omitted. Some terminals work OK using only pins 2, + 3 and 7, while others require different configurations + than the examples shown below. DB-25 to DB-25 Null-Modem Cable @@ -257,7 +261,8 @@
- Here are two other schemes more common nowadays. + Here are two other schemes more common + nowadays. DB-9 to DB-9 Null-Modem Cable @@ -441,87 +446,92 @@ When one pin at one end connects to a pair of pins - at the other end, it is usually implemented with one short - wire between the pair of pins in their connector and a - long wire to the other single pin. + at the other end, it is usually implemented with one + short wire between the pair of pins in their connector + and a long wire to the other single pin. - The above designs seems to be the most popular. In another - variation (explained in the book RS-232 Made - Easy) SG connects to SG, TD connects to RD, RTS and - CTS connect to DCD, DTR connects to DSR, and vice-versa. + The above designs seems to be the most popular. In + another variation (explained in the book RS-232 + Made Easy) SG connects to SG, TD connects to + RD, RTS and CTS connect to DCD, DTR connects to DSR, and + vice-versa. Standard RS-232C Cables + RS-232C cables - A standard serial cable passes all of the RS-232C signals - straight through. That is, the Transmitted Data - pin on one end of the cable goes to the - Transmitted Data pin on the other end. This is - the type of cable to use to connect a modem to your FreeBSD - system, and is also appropriate for some terminals. + A standard serial cable passes all of the RS-232C + signals straight through. That is, the Transmitted + Data pin on one end of the cable goes to the + Transmitted Data pin on the other end. + This is the type of cable to use to connect a modem to + your FreeBSD system, and is also appropriate 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. + 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 DB-25 ports. Personal computers, - including PCs running FreeBSD, will have DB-25 or DB-9 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. + 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 DB-25 ports. Personal + computers, including PCs running FreeBSD, will have DB-25 + or DB-9 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: + In FreeBSD, you access each serial port through an + entry in the /dev directory. There + are two different kinds of entries: Call-in ports are named /dev/ttyuN where N is the port number, - starting from zero. Generally, you use the call-in port for - terminals. Call-in ports require that the serial line assert - the data carrier detect (DCD) signal to work correctly. + starting from zero. Generally, you use the call-in + port for terminals. Call-in ports require that the + serial line assert the data carrier detect (DCD) + signal to work correctly. Call-out ports are named /dev/cuauN. - You usually do not use the call-out port for terminals, just - for modems. You may use the call-out port if the serial cable - or the terminal does not support the carrier detect - signal. + You usually do not use the call-out port for + terminals, just for modems. You may use the call-out + port if the serial cable or the terminal does not + support the carrier detect signal. - If you have connected a terminal to the first serial port - (COM1 in &ms-dos;), then you will - use /dev/ttyu0 to refer to the terminal. If - the terminal is on the second serial port (also known as - COM2), use + If you have connected a terminal to the first serial + port(COM1 in &ms-dos;), then you + will use /dev/ttyu0 to refer to the + terminal. If the terminal is on the second serial port + (also known as COM2), use /dev/ttyu1, and so forth. @@ -540,27 +550,28 @@ dumb multiport serial interface cards, such as the BocaBoard 1008 and 2016, as well as more intelligent multi-port cards such as those made by Digiboard - and Stallion Technologies. However, the default kernel only looks - for the standard COM ports. + and Stallion Technologies. However, the default kernel only + looks for the standard COM ports. - To see if your kernel recognizes any of your serial ports, watch - for messages while the kernel is booting, or use the - /sbin/dmesg command to replay the kernel's boot - messages. In particular, look for messages that start with the - characters uart if you use &os; 8.0 or - higher, or sio for &os; 7.4 or older. + To see if your kernel recognizes any of your serial ports, + watch for messages while the kernel is booting, or use the + /sbin/dmesg command to replay the kernel's + boot messages. In particular, look for messages that start + with the characters uart if you use + &os; 8.0 or higher, or sio for + &os; 7.4 or older. To view just the messages that have the word - uart or sio depending on the - installed version of &os;, use the commands: + uart or sio depending + on the installed version of &os;, use the commands: &prompt.root; /sbin/dmesg | grep 'uart' &prompt.root; /sbin/dmesg | grep 'sio' For example, on a &os; 7.X - system with four serial ports, these are the serial-port specific - kernel boot messages: + system with four serial ports, these are the serial-port + specific kernel boot messages: sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -574,28 +585,28 @@ sio3: type 16550A If your kernel does not recognize all of your serial ports, you will probably need to configure your kernel in the /boot/device.hints file. You can - also comment-out or completely remove lines for devices you do not - have. + also comment-out or completely remove lines for devices you + do not have. Please refer to the &man.sio.4; manual page for - more information on serial ports and multiport boards configuration. - Be careful if you are using a configuration + more information on serial ports and multiport boards + configuration. Be careful if you are using a configuration file that was previously used for a different version of - FreeBSD because the device flags and the syntax have changed between - versions. + FreeBSD because the device flags and the syntax have changed + between versions. port IO_COM1 is a substitution for port 0x3f8, IO_COM2 is 0x2f8, IO_COM3 is 0x3e8, and IO_COM4 is - 0x2e8, which are fairly common port addresses for - their respective serial ports; interrupts 4, 3, 5, and 9 are fairly - common interrupt request lines. Also note that regular serial ports - cannot share interrupts on ISA-bus PCs - (multiport boards have on-board electronics that allow all the - 16550A's on the board to share one or two interrupt request - lines). + 0x2e8, which are fairly common port + addresses for their respective serial ports; interrupts 4, + 3, 5, and 9 are fairly common interrupt request lines. Also + note that regular serial ports cannot + share interrupts on ISA-bus PCs (multiport boards have + on-board electronics that allow all the 16550A's on the + board to share one or two interrupt request lines). @@ -603,27 +614,29 @@ sio3: type 16550A Device Special Files - Most devices in the kernel are accessed through device - special files, which are located in the - /dev directory. The sio - devices are accessed through the - /dev/ttyuN (dial-in) - and /dev/cuauN - (call-out) devices. FreeBSD also provides initialization devices - (/dev/ttyuN.init and + Most devices in the kernel are accessed through + device special files, which are located in the + /dev directory. The + sio devices are accessed through the + /dev/ttyuN + (dial-in) and + /dev/cuauN + (call-out) devices. FreeBSD also provides initialization + devices + (/dev/ttyuN.init + and /dev/cuauN.init) + and locking devices + (/dev/ttyuN.lock and - locking devices - (/dev/ttyuN.lock and /dev/cuauN.lock). - The - initialization devices are used to initialize communications port - parameters each time a port is opened, such as - crtscts for modems which use - RTS/CTS signaling for flow control. The locking - devices are used to lock flags on ports to prevent users or programs - changing certain parameters; see the manual pages &man.termios.4;, - &man.sio.4;, and &man.stty.1; for + The initialization devices are used to initialize + communications port parameters each time a port is opened, + such as crtscts for modems which use + RTS/CTS signaling for flow control. The + locking devices are used to lock flags on ports to prevent + users or programs changing certain parameters; see the manual + pages &man.termios.4;, &man.sio.4;, and &man.stty.1; for information on the terminal settings, locking and initializing devices, and setting terminal options, respectively. @@ -632,49 +645,53 @@ sio3: type 16550A Serial Port Configuration - ttyu - cuau + ttyu + cuau - The ttyuN (or - cuauN) device is the - regular device you will want to open for your applications. When a - process opens the device, it will have a default set of terminal I/O - settings. You can see these settings with the command - - &prompt.root; stty -a -f /dev/ttyu1 - - When you change the settings to this device, the settings are in - effect until the device is closed. When it is reopened, it goes back to - the default set. To make changes to the default set, you can open and - adjust the settings of the initial state device. For - example, to turn on mode, 8 bit communication, - and flow control by default for - ttyu5, type: + The + ttyuN (or + cuauN) + device is the regular device you will want to open for your + applications. When a process opens the device, it will have a + default set of terminal I/O settings. You can see these + settings with the command + + &prompt.root; stty -a -f /dev/ttyu1 + + When you change the settings to this device, the settings + are in effect until the device is closed. When it is + reopened, it goes back to the default set. To make changes to + the default set, you can open and adjust the settings of the + initial state device. For example, to turn on + mode, 8 bit communication, and + flow control by default for + ttyu5, type: &prompt.root; stty -f /dev/ttyu5.init clocal cs8 ixon ixoff - - rc files - rc.serial - - - System-wide initialization of the serial devices is - controlled in /etc/rc.d/serial. This file - affects the default settings of serial devices. - - To prevent certain settings from being changed by an - application, make adjustments to the lock state - device. For example, to lock the speed of - ttyu5 to 57600 bps, type: + + rc files + rc.serial + + + System-wide initialization of the serial devices is + controlled in /etc/rc.d/serial. This + file affects the default settings of serial devices. + + To prevent certain settings from being changed by an + application, make adjustments to the lock state + device. For example, to lock the speed of + ttyu5 to 57600 bps, type: &prompt.root; stty -f /dev/ttyu5.lock 57600 - Now, an application that opens - ttyu5 and tries to change the speed of - the port will be stuck with 57600 bps. - - Naturally, you should make the initial state and lock state devices - writable only by the root account. + Now, an application that opens + ttyu5 and tries to change the speed + of the port will be stuck with 57600 bps. + + Naturally, you should make the initial state and lock + state devices writable only by the root + account. @@ -706,33 +723,35 @@ sio3: type 16550A terminals Terminals provide a convenient and low-cost way to access - 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. + 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 - 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 an unused serial port, you - can log in and run any text program that you would normally run on the - console or in an xterm window in the X Window - System. - - For the business user, you can attach many terminals to a FreeBSD - system and place them on your employees' desktops. For a home user, a - spare computer such as an older IBM PC or a &macintosh; can be a - terminal wired into a more powerful computer running FreeBSD. You can - turn what might otherwise be a single-user computer into a powerful - multiple user system. + 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 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 an unused serial port, you can log in and + run any text program that you would normally run on the + console or in an xterm window in the X + Window System. + + For the business user, you can attach many terminals to a + FreeBSD system and place them on your employees' desktops. + For a home user, a spare computer such as an older IBM PC or a + &macintosh; can be a terminal wired into a more powerful + computer running FreeBSD. You can turn what might otherwise be + a single-user computer into a powerful multiple user + system. For FreeBSD, there are three kinds of terminals: @@ -742,7 +761,8 @@ sio3: type 16550A - PCs acting as terminals + PCs acting as + terminals @@ -755,39 +775,41 @@ sio3: type 16550A 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 graphical applications such as those provided by - the X Window System. + 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 graphical applications such as + those provided by the X Window System. PCs Acting as Terminals - If a dumb terminal 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 terminal emulation - software to run on the computer. - - Such a configuration is popular in homes. For example, if your - spouse is busy working on your FreeBSD system's console, you can do - some text-only work at the same time from a less powerful personal - computer hooked up as a terminal to the FreeBSD system. + If a dumb terminal 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 + terminal emulation software to run on + the computer. + + Such a configuration is popular in homes. For example, + if your spouse is busy working on your FreeBSD system's + console, you can do some text-only work at the same time + from a less powerful personal computer hooked up as a + terminal to the FreeBSD system. There are at least two utilities in the base-system of &os; that can be used to work through a serial connection: @@ -807,19 +829,19 @@ sio3: type 16550A port number. - Note that device numbers in &os; start from zero and not - one (like they do, for instance in &ms-dos;-derived systems). - This means that what &ms-dos;-based systems call - COM1 is usually + Note that device numbers in &os; start from zero and + not one (like they do, for instance in &ms-dos;-derived + systems). This means that what &ms-dos;-based systems + call COM1 is usually /dev/cuau0 in &os;. Some people prefer to use other programs, available - through the Ports Collection. The Ports include quite a few - utilities which can work in ways similar to &man.cu.1; and - &man.tip.1;, - i.e., comms/minicom. + through the Ports Collection. The Ports include quite a + few utilities which can work in ways similar to &man.cu.1; + and &man.tip.1;, i.e., comms/minicom. @@ -827,23 +849,26 @@ sio3: type 16550A 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 not cover setup, - configuration, or use of X terminals. + 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 + not cover setup, configuration, or use + of X terminals. 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. + 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. Recall from that the init process is responsible for all process @@ -856,18 +881,19 @@ sio3: type 16550A program. Thus, to configure terminals for your FreeBSD system the - following steps should be taken as root: + following steps should be taken as + root: - Add a line to /etc/ttys for the entry in - the /dev directory for the serial port if it - is not already there. + Add a 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 + Specify that /usr/libexec/getty + be run on the port, and specify the appropriate getty type from the /etc/gettytab file. @@ -892,31 +918,34 @@ sio3: type 16550A As an optional step, you may wish to create a custom - getty type for use in step 2 by making an - entry in /etc/gettytab. This chapter does - not explain how to do so; you are encouraged to see the - &man.gettytab.5; and the &man.getty.8; manual pages for more - information. + getty type for use in step 2 by + making an entry in /etc/gettytab. This + chapter does not explain how to do so; you are encouraged to + see the &man.gettytab.5; and the &man.getty.8; manual pages + for more information. - Adding an Entry to <filename>/etc/ttys</filename> + Adding an Entry to + <filename>/etc/ttys</filename> - 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 also 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 (for example, + 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 also 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 (for example, /dev/ttyv0 would be listed as ttyv0). A default FreeBSD install includes an - /etc/ttys file with support for the first - four serial ports: ttyu0 through - ttyu3. If you are attaching a terminal - to one of those ports, you do not need to add another entry. + /etc/ttys file with support for the + first four serial ports: ttyu0 + through ttyu3. If you are + attaching a terminal to one of those ports, you do not need + to add another entry. Adding Terminal Entries to @@ -937,14 +966,13 @@ sio3: type 16550A</screen> id="co-ttys-line1col3"/> on<co id="co-ttys-line1col4"/> insecure<co id="co-ttys-line1col5"/> -ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure - </programlisting> +ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure</programlisting> <calloutlist> <callout arearefs="co-ttys-line1col1"> <para>The first field normally specifies the name of - the terminal special file as it is found in - <filename>/dev</filename>.</para> + the terminal special file as it is found in + <filename>/dev</filename>.</para> </callout> <callout arearefs="co-ttys-line1col2"> @@ -959,18 +987,18 @@ ttyu5 "/usr/libexec/getty std.19200" <replaceable>getty</replaceable> type. A <replaceable>getty</replaceable> type configures characteristics on the terminal line, like bps rate - and parity. The <command>getty</command> program reads - these characteristics from the file + and parity. The <command>getty</command> program + reads these characteristics from the file <filename>/etc/gettytab</filename>.</para> <para>The file <filename>/etc/gettytab</filename> contains lots of entries for terminal lines both old and new. In almost all cases, the entries that start with the text <literal>std</literal> will work for - hardwired terminals. These entries ignore parity. + hardwired terminals. These entries ignore parity. There is a <literal>std</literal> entry for each bps rate from 110 to 115200. Of course, you can add your - own entries to this file. The &man.gettytab.5; manual + own entries to this file. The &man.gettytab.5; manual page provides more information.</para> <para>When setting the <replaceable>getty</replaceable> @@ -979,8 +1007,8 @@ ttyu5 "/usr/libexec/getty std.19200" match.</para> <para>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.</para> + connects at 38400 bps. The 286 PC uses no + parity and connects at 19200 bps.</para> </callout> <callout arearefs="co-ttys-line1col3"> @@ -1038,13 +1066,15 @@ ttyu5 "/usr/libexec/getty std.19200" <para>After making the necessary changes to the <filename>/etc/ttys</filename> file you should send a SIGHUP (hangup) signal to the <command>init</command> process to - force it to re-read its configuration file. For example:</para> + force it to re-read its configuration file. For + example:</para> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> <note> - <para><command>init</command> is always the first process run - on a system, therefore it will always have PID 1.</para> + <para><command>init</command> is always the first process + run on a system, therefore it will always have PID + 1.</para> </note> <para>If everything is set up correctly, all cables are in @@ -1058,31 +1088,31 @@ ttyu5 "/usr/libexec/getty std.19200" <sect2 id="term-debug"> <title>Troubleshooting 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. + 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. No Login Prompt Appears - Make sure the terminal is plugged in and powered up. If it - is a personal computer acting as a terminal, make sure it is - running terminal emulation software on the correct serial + Make sure the terminal is plugged in and powered up. If + it is a personal computer acting as a terminal, make sure it + is running terminal emulation software on the correct serial port. - Make sure the cable is connected firmly to both the terminal - and the FreeBSD computer. Make sure it is the right kind of - cable. - - Make sure the terminal and FreeBSD agree on the bps rate and - parity settings. If you have a video display terminal, make - sure the contrast and brightness controls are turned up. If it - is a printing terminal, make sure paper and ink are in good - supply. - - Make sure that a getty process is running - and serving the terminal. For example, to get a list of - running getty processes with + Make sure the cable is connected firmly to both the + terminal and the FreeBSD computer. Make sure it is the + right kind of cable. + + Make sure the terminal and FreeBSD agree on the bps rate + and parity settings. If you have a video display terminal, + make sure the contrast and brightness controls are turned + up. If it is a printing terminal, make sure paper and ink + are in good supply. + + Make sure that a getty process is + running and serving the terminal. For example, to get a + list of running getty processes with ps, type: &prompt.root; ps -axww|grep getty @@ -1096,24 +1126,25 @@ ttyu5 "/usr/libexec/getty std.19200" 22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyu1 - If no getty process is running, make sure - you have enabled the port in /etc/ttys. - Also remember to run kill -HUP 1 - after modifying the ttys file. + If no getty process is running, make + sure you have enabled the port in + /etc/ttys. Also remember to run + kill -HUP 1 after modifying the + ttys file. If the getty process is running but the terminal still does not display a login prompt, or if it displays a prompt but will not allow you to type, your terminal or cable may not support hardware - handshaking. Try changing the entry in + handshaking. Try changing the entry in /etc/ttys from std.38400 to 3wire.38400 (remember to run kill -HUP 1 after modifying - /etc/ttys). The + /etc/ttys). The 3wire entry is similar to std, but ignores hardware - handshaking. You may need to reduce the baud rate or + handshaking. You may need to reduce the baud rate or enable software flow control when using 3wire to prevent buffer overflows. @@ -1123,12 +1154,12 @@ ttyu5 "/usr/libexec/getty std.19200" If Garbage Appears Instead of a Login Prompt - Make sure the terminal and FreeBSD agree on the bps rate and - parity settings. Check the getty processes - to make sure the - correct getty type is in use. If - not, edit /etc/ttys and run kill - -HUP 1. + Make sure the terminal and FreeBSD agree on the bps rate + and parity settings. Check the getty + processes to make sure the correct + getty type is in use. If not, + edit /etc/ttys and run kill + -HUP 1. @@ -1137,8 +1168,8 @@ ttyu5 "/usr/libexec/getty std.19200" Typed Switch the terminal (or the terminal emulation software) - from half duplex or local echo to - full duplex. + from half duplex or local echo + to full duplex. @@ -1181,24 +1212,26 @@ ttyu5 "/usr/libexec/getty std.19200" similar to connecting terminals except that you are dealing with modems instead of terminals. - - External Versus Internal Modems + + External Versus Internal Modems - External modems seem to be more convenient for dial-up, because - external modems often can be semi-permanently configured via - parameters stored in non-volatile RAM and they usually provide - lighted indicators that display the state of important RS-232 - signals. Blinking lights impress visitors, but lights are also very - useful to see whether a modem is operating properly. - - Internal modems usually lack non-volatile RAM, so their - configuration may be limited only to setting DIP switches. If your - internal modem has any signal indicator lights, it is probably - difficult to view the lights when the system's cover is in - place. + External modems seem to be more convenient for dial-up, + because external modems often can be semi-permanently + configured via parameters stored in non-volatile RAM and they + usually provide lighted indicators that display the state of + important RS-232 signals. Blinking lights impress visitors, + but lights are also very useful to see whether a modem is + operating properly. + + Internal modems usually lack non-volatile RAM, so their + configuration may be limited only to setting DIP switches. + If your internal modem has any signal indicator lights, it is + probably difficult to view the lights when the system's cover + is in place. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***