From owner-svn-doc-head@FreeBSD.ORG Thu Oct 17 17:08:29 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 908AC4EA; Thu, 17 Oct 2013 17:08:29 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7CBE121F6; Thu, 17 Oct 2013 17:08:29 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r9HH8TBM015224; Thu, 17 Oct 2013 17:08:29 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r9HH8TWk015223; Thu, 17 Oct 2013 17:08:29 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310171708.r9HH8TWk015223@svn.freebsd.org> From: Dru Lavigne Date: Thu, 17 Oct 2013 17:08:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42985 - 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: Thu, 17 Oct 2013 17:08:29 -0000 Author: dru Date: Thu Oct 17 17:08:29 2013 New Revision: 42985 URL: http://svnweb.freebsd.org/changeset/doc/42985 Log: White space fix only. Translators can ignore. To be followed by a quick typo fix. 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 Thu Oct 17 15:42:25 2013 (r42984) +++ head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Thu Oct 17 17:08:29 2013 (r42985) @@ -59,30 +59,36 @@ Serial Terminology and Hardware - The following terms are often used in serial commnications: - - - bps + The following terms are often used in serial + commnications: + + + bps - Bits per Secondbits-per-second (bps) is the rate - at which data is transmitted. + Bits per + Secondbits-per-second + (bps) is the rate at which data is + transmitted. DTE - Data Terminal EquipmentDTE - (DTE) is one of two endpoints in a - serial communication. An example would be a computer. + Data Terminal + EquipmentDTE + (DTE) is one of two endpoints in a + serial communication. An example would be a + computer. DCE - Data Communications EquipmentDCE - (DTE) is the other endpoint in a + Data Communications + EquipmentDCE + (DTE) is the other endpoint in a serial communication. Typically, it is a modem. @@ -92,8 +98,9 @@ The original standard which defined hardware serial - communications. It has since been renamed to - TIA-232RS-232C cables. + communications. It has since been renamed to + TIA-232RS-232C + cables. @@ -104,7 +111,6 @@ period of time, while bps is the correct term to use. - To connect a modem or serial terminal to a &os; system, a serial port on the computer and the proper cable to connect to the serial device are needed. Users who are already familiar @@ -119,372 +125,372 @@ RS-232 cables. The documentation for the hardware should describe the type of cable required. - - null-modem cable - - - 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. - - A null-modem cable can be constructed for use with - terminals. The following table shows the RS-232C signal names - and the pin numbers on a DB-25 connector. While the - standard calls for a straight-through pin 1 to pin 1 - Protective Ground line, it is often - omitted. Some terminals work using only pins 2, 3, and - 7, while others require different configurations than - the examples shown below. + + null-modem cable + - - DB-25 to DB-25 Null-Modem Cable + 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. + + A null-modem cable can be constructed for use with + terminals. The following table shows the RS-232C signal names + and the pin numbers on a DB-25 connector. While the + standard calls for a straight-through pin 1 to pin 1 + Protective Ground line, it is often + omitted. Some terminals work using only pins 2, 3, and + 7, while others require different configurations than + the examples shown below. - - - - Signal - Pin # - - Pin # - Signal - - +
+ DB-25 to DB-25 Null-Modem Cable - - - SG - 7 - connects to - 7 - SG - + + + + Signal + Pin # + + Pin # + Signal + + - - TD - 2 - connects to - 3 - RD - + + + SG + 7 + connects to + 7 + SG + - - RD - 3 - connects to - 2 - TD - + + TD + 2 + connects to + 3 + RD + - - RTS - 4 - connects to - 5 - CTS - + + RD + 3 + connects to + 2 + TD + - - CTS - 5 - connects to - 4 - RTS - + + RTS + 4 + connects to + 5 + CTS + - - DTR - 20 - connects to - 6 - DSR - + + CTS + 5 + connects to + 4 + RTS + - - DTR - 20 - connects to - 8 - DCD - + + DTR + 20 + connects to + 6 + DSR + - - DSR - 6 - connects to - 20 - DTR - + + DTR + 20 + connects to + 8 + DCD + - - DCD - 8 - connects to - 20 - DTR - - - -
+ + DSR + 6 + connects to + 20 + DTR + - The next two tables show two other common - schemes. + + DCD + 8 + connects to + 20 + DTR + + + + - - DB-9 to DB-9 Null-Modem Cable + The next two tables show two other common + schemes. - - - - Signal - Pin # - - Pin # - Signal - - +
+ DB-9 to DB-9 Null-Modem Cable - - - RD - 2 - connects to - 3 - TD - + + + + Signal + Pin # + + Pin # + Signal + + - - TD - 3 - connects to - 2 - RD - + + + RD + 2 + connects to + 3 + TD + - - DTR - 4 - connects to - 6 - DSR - + + TD + 3 + connects to + 2 + RD + - - DTR - 4 - connects to - 1 - DCD - + + DTR + 4 + connects to + 6 + DSR + - - SG - 5 - connects to - 5 - SG - + + DTR + 4 + connects to + 1 + DCD + - - DSR - 6 - connects to - 4 - DTR - + + SG + 5 + connects to + 5 + SG + - - DCD - 1 - connects to - 4 - DTR - + + DSR + 6 + connects to + 4 + DTR + - - RTS - 7 - connects to - 8 - CTS - + + DCD + 1 + connects to + 4 + DTR + - - CTS - 8 - connects to - 7 - RTS - - - -
+ + RTS + 7 + connects to + 8 + CTS + - - DB-9 to DB-25 Null-Modem Cable + + CTS + 8 + connects to + 7 + RTS + + + +
- - - - Signal - Pin # - - Pin # - Signal - - + + DB-9 to DB-25 Null-Modem Cable - - - RD - 2 - connects to - 2 - TD - + + + + Signal + Pin # + + Pin # + Signal + + - - TD - 3 - connects to - 3 - RD - + + + RD + 2 + connects to + 2 + TD + - - DTR - 4 - connects to - 6 - DSR - + + TD + 3 + connects to + 3 + RD + - - DTR - 4 - connects to - 8 - DCD - + + DTR + 4 + connects to + 6 + DSR + - - SG - 5 - connects to - 7 - SG - + + DTR + 4 + connects to + 8 + DCD + - - DSR - 6 - connects to - 20 - DTR - + + SG + 5 + connects to + 7 + SG + - - DCD - 1 - connects to - 20 - DTR - + + DSR + 6 + connects to + 20 + DTR + - - RTS - 7 - connects to - 5 - CTS - + + DCD + 1 + connects to + 20 + DTR + - - CTS - 8 - connects to - 4 - RTS - - - -
+ + RTS + 7 + connects to + 5 + CTS + - - 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. - + + CTS + 8 + connects to + 4 + RTS + + + + + + + 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. + - The above designs seem to be the most popular. In - another variation, SG connects to SG, TD connects to RD, - RTS and CTS connect to DCD, DTR connects to DSR, and - vice-versa. - - RS-232C cables - - A standard serial cable passes all of the RS-232C - signals straight through. 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 used to connect a modem to - the &os; system, and is also appropriate for some - terminals. + The above designs seem to be the most popular. In + another variation, SG connects to SG, TD connects to RD, + RTS and CTS connect to DCD, DTR connects to DSR, and + vice-versa. + + RS-232C cables + + A standard serial cable passes all of the RS-232C + signals straight through. 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 used to connect a modem to + the &os; system, and is also appropriate for some + terminals. Serial ports are the devices through which data is transferred between the &os; host computer and the terminal. This section describes the kinds of ports that exist and how they are addressed in &os;. - Several kinds of serial ports exist. Before - purchasing or constructing a cable, make sure it will - fit the ports on the terminal and on the &os; - system. - - Most terminals have DB-25 ports. Personal computers - may have DB-25 or DB-9 ports. A multiport serial card may - have RJ-12 or RJ-45 ports. - - See the documentation that accompanied the hardware - for specifications on the kind of port or visually verify - the type of port. - - In &os;, each serial port is accessed through an - entry in /dev. - There are two different kinds of entries: - - - - Call-in ports are named - /dev/ttyuN - where N is the port number, - starting from zero. Generally, the call-in port is - used 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. - Call-out ports are usually not used for terminals, but - are used for modems. The call-out port can be used if - the serial cable or the terminal does not support the - carrier detect signal. - - - - If a terminal is connected to the first serial - port(COM1), use - /dev/ttyu0 to refer to the - terminal. If the terminal is on the second serial port - (COM2), use - /dev/ttyu1, and so forth. - + Several kinds of serial ports exist. Before + purchasing or constructing a cable, make sure it will + fit the ports on the terminal and on the &os; + system. + + Most terminals have DB-25 ports. Personal computers + may have DB-25 or DB-9 ports. A multiport serial card may + have RJ-12 or RJ-45 ports. + + See the documentation that accompanied the hardware + for specifications on the kind of port or visually verify + the type of port. + + In &os;, each serial port is accessed through an + entry in /dev. + There are two different kinds of entries: + + + + Call-in ports are named + /dev/ttyuN + where N is the port number, + starting from zero. Generally, the call-in port is + used 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. + Call-out ports are usually not used for terminals, but + are used for modems. The call-out port can be used if + the serial cable or the terminal does not support the + carrier detect signal. + + + + If a terminal is connected to the first serial + port(COM1), use + /dev/ttyu0 to refer to the + terminal. If the terminal is on the second serial port + (COM2), use + /dev/ttyu1, and so forth. + Kernel Configuration @@ -635,109 +641,110 @@ connected network. This section describes how to use terminals with &os;. - The original &unix; systems did not have consoles. - Instead, users logged in and ran programs through terminals - that were connected to the computer's serial ports. - - The ability to establish a login session on a serial port - still exists in nearly every &unix;-like operating system - today, including &os;. By using a terminal attached to an - unused serial port, a user can log in and run any text program - that can normally be run on the console or in an - xterm window. - - Many terminals can be attached to a &os; system. An older - spare computer can be used as a terminal wired into a more - powerful computer running &os;. This can turn what might - otherwise be a single-user computer into a powerful multiple - user system. - - &os; supports three types of terminals: + The original &unix; systems did not have consoles. + Instead, users logged in and ran programs through terminals + that were connected to the computer's serial ports. + + The ability to establish a login session on a serial port + still exists in nearly every &unix;-like operating system + today, including &os;. By using a terminal attached to an + unused serial port, a user can log in and run any text program + that can normally be run on the console or in an + xterm window. + + Many terminals can be attached to a &os; system. An older + spare computer can be used as a terminal wired into a more + powerful computer running &os;. This can turn what might + otherwise be a single-user computer into a powerful multiple + user system. + + &os; supports three types of terminals: + Dumb terminals + Computers Acting as Terminals - - - Dumb terminals - - Dumb terminals are specialized hardware that connect to - computers over serial lines. They are called - dumb because they have only enough - computational power to display, send, and receive text. No - programs can be run on these devices. Dumb terminals - connect to a computer 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, and just about any kind will work with - &os;. 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. - - + + + + Dumb terminals are specialized hardware that connect + to computers over serial lines. They are called + dumb because they have only enough + computational power to display, send, and receive text. + No programs can be run on these devices. Dumb terminals + connect to a computer 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, and just about any kind will work + with &os;. 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. + + - Computers Acting as Terminals - If a dumb terminal has - just enough ability to display, send, and receive text, - any spare computer can be a dumb terminal. All that is - needed is the proper cable and some terminal + If a dumb terminal has just enough ability to + display, send, and receive text, any spare computer can + be a dumb terminal. All that is needed is the proper + cable and some terminal emulation software to run on the - computer. + computer. - This configuration can be useful. For example, if one - user is busy working at the &os; system's console, another - user can do some text-only work at the same time from a - less powerful personal computer hooked up as a terminal to - the &os; system. - - There are at least two utilities in the base-system of - &os; that can be used to work through a serial connection: - &man.cu.1; and &man.tip.1;. - - To connect from a client system that runs &os; to the - serial connection of another system, use: - - &prompt.root; cu -l serial-port-device - - Where serial-port-device is the name of a - special device file denoting a serial port on the system. - These device files are called - /dev/cuauN. + This configuration can be useful. For example, if one + user is busy working at the &os; system's console, another + user can do some text-only work at the same time from a + less powerful personal computer hooked up as a terminal to + the &os; system. + + There are at least two utilities in the base-system of + &os; that can be used to work through a serial connection: + &man.cu.1; and &man.tip.1;. + + To connect from a client system that runs &os; to the + serial connection of another system, use: + + &prompt.root; cu -l serial-port-device + + Where serial-port-device is the name of + a special device file denoting a serial port on the + system. These device files are called + /dev/cuauN. - The N-part of a device name is the serial - port number. + The N-part of a device name is the + serial port number. - - Note that device numbers in &os; start from zero and - not one. This means that COM1 is - /dev/cuau0 in &os;. - + + Note that device numbers in &os; start from zero and + not one. This means that COM1 + is /dev/cuau0 in &os;. + - - Some people prefer to use other programs available - through the Ports Collection, such as comms/minicom. - - - + + Some people prefer to use other programs available + through the Ports Collection, such as comms/minicom. + + + 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. - - This chapter does not cover the - setup, configuration, or use of 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. + + This chapter does not cover the + setup, configuration, or use of X terminals. + + + Configuration @@ -968,69 +975,70 @@ ttyu5 "/usr/libexec/getty std.19200" Here is a list of common symptoms and some suggested fixes. - If 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 - port. - - Make sure the cable is connected firmly to both the - terminal and the &os; computer. Make sure it is the - right kind of cable. - - Make sure the terminal and &os; agree on the - bps rate and parity settings. For 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 - - There should be an entry for the terminal. For example, - the following display shows that a - getty is running on the second serial - port, ttyu1, and is using the - std.38400 entry in - /etc/gettytab: *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***