diff options
Diffstat (limited to 'documentation/content/en/books/handbook/serialcomms/_index.po')
| -rw-r--r-- | documentation/content/en/books/handbook/serialcomms/_index.po | 2486 |
1 files changed, 2486 insertions, 0 deletions
diff --git a/documentation/content/en/books/handbook/serialcomms/_index.po b/documentation/content/en/books/handbook/serialcomms/_index.po new file mode 100644 index 0000000000..ee4926cc2f --- /dev/null +++ b/documentation/content/en/books/handbook/serialcomms/_index.po @@ -0,0 +1,2486 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR The FreeBSD Project +# This file is distributed under the same license as the FreeBSD Documentation package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: FreeBSD Documentation VERSION\n" +"POT-Creation-Date: 2024-01-17 20:35-0300\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"Language: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. type: YAML Front Matter: description +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1 +#, no-wrap +msgid "This chapter covers some of the ways serial communications can be used on FreeBSD" +msgstr "" + +#. type: YAML Front Matter: part +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1 +#, no-wrap +msgid "Part IV. Network Communication" +msgstr "" + +#. type: YAML Front Matter: title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1 +#, no-wrap +msgid "Chapter 29. Serial Communications" +msgstr "" + +#. type: Title = +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:14 +#, no-wrap +msgid "Serial Communications" +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:52 +#, no-wrap +msgid "Synopsis" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:57 +msgid "" +"UNIX(R) has always had support for serial communications as the very first " +"UNIX(R) 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 covers " +"some of the ways serial communications can be used on FreeBSD." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:59 +msgid "After reading this chapter, you will know:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:61 +msgid "How to connect terminals to a FreeBSD system." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:62 +msgid "How to use a modem to dial out to remote hosts." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:63 +msgid "How to allow remote users to login to a FreeBSD system with a modem." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:64 +msgid "How to boot a FreeBSD system from a serial console." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:66 +msgid "Before reading this chapter, you should:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:68 +msgid "" +"Know how to crossref:kernelconfig[kernelconfig, configure and install a " +"custom kernel]." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:69 +msgid "Understand crossref:basics[basics, FreeBSD permissions and processes]." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:70 +msgid "" +"Have access to the technical manual for the serial hardware to be used with " +"FreeBSD." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:72 +#, no-wrap +msgid "Serial Terminology and Hardware" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:75 +msgid "The following terms are often used in serial communications:" +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:76 +#, no-wrap +msgid "bps" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:78 +msgid "Bits per Second (bps) is the rate at which data is transmitted." +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:79 +#, no-wrap +msgid "DTE" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:82 +msgid "" +"Data Terminal Equipment (DTE) is one of two endpoints in a serial " +"communication. An example would be a computer." +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:83 +#, no-wrap +msgid "DCE" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:86 +msgid "" +"Data Communications Equipment (DCE) is the other endpoint in a serial " +"communication. Typically, it is a modem or serial terminal." +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:87 +#, no-wrap +msgid "RS-232" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:90 +msgid "" +"The original standard which defined hardware serial communications. It has " +"since been renamed to TIA-232." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:93 +msgid "" +"When referring to communication data rates, this section does not use the " +"term _baud_. Baud refers to the number of electrical state transitions made " +"in a period of time, while bps is the correct term to use." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:96 +msgid "" +"To connect a serial terminal to a FreeBSD system, a serial port on the " +"computer and the proper cable to connect to the serial device are needed. " +"Users who are already familiar with serial hardware and cabling can safely " +"skip this section." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:98 +#, no-wrap +msgid "Serial Cables and Ports" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:103 +msgid "" +"There are several different kinds of serial cables. The two most common " +"types are null-modem cables and standard RS-232 cables. The documentation " +"for the hardware should describe the type of cable required." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:109 +msgid "" +"These two types of cables differ in how the wires are connected to the " +"connector. Each wire represents a signal, with the defined signals " +"summarized in <<serialcomms-signal-names>>. A standard serial cable passes " +"all of the RS-232C signals straight through. For example, 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 " +"FreeBSD system, and is also appropriate for some terminals." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:112 +msgid "" +"A null-modem cable switches the \"Transmitted Data\" pin of the connector on " +"one end with the \"Received Data\" pin on the other end. The connector can " +"be either a DB-25 or a DB-9." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:117 +msgid "" +"A null-modem cable can be constructed using the pin connections summarized " +"in <<nullmodem-db25>>, <<nullmodem-db9>>, and <<nullmodem-db9-25>>. 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. When in doubt, " +"refer to the documentation for the hardware." +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:119 +#, no-wrap +msgid "RS-232C Signal Names" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:123 +#, no-wrap +msgid "Acronyms" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:125 +#, no-wrap +msgid "Names" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:126 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:172 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:173 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:226 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:237 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:291 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:302 +#, no-wrap +msgid "RD" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:128 +#, no-wrap +msgid "Received Data" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:129 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:167 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:178 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:231 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:232 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:296 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:297 +#, no-wrap +msgid "TD" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:131 +#, no-wrap +msgid "Transmitted Data" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:132 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:191 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:197 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:208 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:213 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:238 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:244 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:261 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:267 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:303 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:309 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:326 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:332 +#, no-wrap +msgid "DTR" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:134 +#, no-wrap +msgid "Data Terminal Ready" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:135 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:196 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:203 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:243 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:256 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:308 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:321 +#, no-wrap +msgid "DSR" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:137 +#, no-wrap +msgid "Data Set Ready" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:138 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:202 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:209 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:249 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:262 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:314 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:327 +#, no-wrap +msgid "DCD" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:140 +#, no-wrap +msgid "Data Carrier Detect" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:141 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:161 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:166 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:250 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:255 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:315 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:320 +#, no-wrap +msgid "SG" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:143 +#, no-wrap +msgid "Signal Ground" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:144 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:179 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:190 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:268 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:278 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:333 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:343 +#, no-wrap +msgid "RTS" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:146 +#, no-wrap +msgid "Request to Send" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:147 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:184 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:185 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:273 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:274 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:338 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:339 +#, no-wrap +msgid "CTS" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:148 +#, no-wrap +msgid "Clear to Send" +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:151 +#, no-wrap +msgid "DB-25 to DB-25 Null-Modem Cable" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:155 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:160 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:220 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:225 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:285 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:290 +#, no-wrap +msgid "Signal" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:156 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:158 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:221 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:223 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:286 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:288 +#, no-wrap +msgid "Pin #" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:162 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:164 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:269 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:277 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:318 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:334 +#, no-wrap +msgid "7" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:163 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:169 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:175 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:181 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:187 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:193 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:199 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:205 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:211 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:228 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:234 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:240 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:246 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:252 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:258 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:264 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:270 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:276 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:293 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:299 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:305 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:311 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:317 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:323 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:329 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:335 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:341 +#, no-wrap +msgid "connects to" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:168 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:176 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:227 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:235 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:292 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:294 +#, no-wrap +msgid "2" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:170 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:174 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:229 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:233 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:298 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:300 +#, no-wrap +msgid "3" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:180 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:188 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:239 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:245 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:259 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:265 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:304 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:310 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:342 +#, no-wrap +msgid "4" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:182 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:186 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:251 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:253 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:316 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:336 +#, no-wrap +msgid "5" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:192 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:198 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:206 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:212 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:324 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:330 +#, no-wrap +msgid "20" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:194 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:204 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:241 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:257 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:306 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:322 +#, no-wrap +msgid "6" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:200 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:210 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:271 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:275 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:312 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:340 +#, no-wrap +msgid "8" +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:216 +#, no-wrap +msgid "DB-9 to DB-9 Null-Modem Cable" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:247 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:263 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:328 +#, no-wrap +msgid "1" +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:281 +#, no-wrap +msgid "DB-9 to DB-25 Null-Modem Cable" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:348 +msgid "" +"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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:353 +msgid "" +"Serial ports are the devices through which data is transferred between the " +"FreeBSD host computer and the terminal. 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 FreeBSD system." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:358 +msgid "" +"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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:361 +msgid "" +"In FreeBSD, each serial port is accessed through an entry in [.filename]#/" +"dev#. There are two different kinds of entries:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:363 +msgid "" +"Call-in ports are named [.filename]#/dev/ttyuN# where _N_ is the port " +"number, starting from zero. If a terminal is connected to the first serial " +"port ([.filename]#COM1#), use [.filename]#/dev/ttyu0# to refer to the " +"terminal. If the terminal is on the second serial port ([.filename]#COM2#), " +"use [.filename]#/dev/ttyu1#, and so forth. Generally, the call-in port is " +"used for terminals. Call-in ports require that the serial line assert the " +"\"Data Carrier Detect\" signal to work correctly." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:364 +msgid "" +"Call-out ports are named [.filename]#/dev/cuauN# on FreeBSD versions 8.X and " +"higher and [.filename]#/dev/cuadN# on FreeBSD versions 7.X and lower. 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 \"Data Carrier Detect\" signal." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:369 +msgid "" +"FreeBSD also provides initialization devices ([.filename]#/dev/ttyuN.init# " +"and [.filename]#/dev/cuauN.init# or [.filename]#/dev/cuadN.init#) and " +"locking devices ([.filename]#/dev/ttyuN.lock# and [.filename]#/dev/cuauN." +"lock# or [.filename]#/dev/cuadN.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. Refer to man:termios[4], man:" +"uart[4], and man:stty[1] for information on terminal settings, locking and " +"initializing devices, and setting terminal options, respectively." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:371 +#, no-wrap +msgid "Serial Port Configuration" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:376 +msgid "" +"By default, FreeBSD supports four serial ports which are commonly known as [." +"filename]#COM1#, [.filename]#COM2#, [.filename]#COM3#, and [." +"filename]#COM4#. FreeBSD also supports dumb multi-port serial interface " +"cards, such as the BocaBoard 1008 and 2016, as well as more intelligent " +"multi-port cards such as those made by Digiboard. However, the default " +"kernel only looks for the standard [.filename]#COM# ports." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:378 +msgid "" +"To see if the system recognizes the serial ports, look for system boot " +"messages that start with `uart`:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:382 +#, no-wrap +msgid "# grep uart /var/run/dmesg.boot\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:388 +msgid "" +"If the system does not recognize all of the needed serial ports, additional " +"entries can be added to [.filename]#/boot/device.hints#. This file already " +"contains `hint.uart.0.\\*` entries for [.filename]#COM1# and `hint.uart.1.*` " +"entries for [.filename]#COM2#. When adding a port entry for [." +"filename]#COM3# use `0x3E8`, and for [.filename]#COM4# use `0x2E8`. Common " +"IRQ addresses are `5` for [.filename]#COM3# and `9` for [.filename]#COM4#." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:391 +msgid "" +"To determine the default set of terminal I/O settings used by the port, " +"specify its device name. This example determines the settings for the call-" +"in port on [.filename]#COM2#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:395 +#, no-wrap +msgid "# stty -a -f /dev/ttyu1\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:403 +msgid "" +"System-wide initialization of serial devices is controlled by [.filename]#/" +"etc/rc.d/serial#. This file affects the default settings of serial " +"devices. To change the settings for a device, use `stty`. By default, the " +"changed settings are in effect until the device is closed and when the " +"device is reopened, it goes back to the default set. To permanently change " +"the default set, open and adjust the settings of the initialization device. " +"For example, to turn on `CLOCAL` mode, 8 bit communication, and `XON/XOFF` " +"flow control for [.filename]#ttyu5#, type:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:407 +#, no-wrap +msgid "# stty -f /dev/ttyu5.init clocal cs8 ixon ixoff\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:411 +msgid "" +"To prevent certain settings from being changed by an application, make " +"adjustments to the locking device. For example, to lock the speed of [." +"filename]#ttyu5# to 57600 bps, type:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:415 +#, no-wrap +msgid "# stty -f /dev/ttyu5.lock 57600\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:418 +msgid "" +"Now, any application that opens [.filename]#ttyu5# and tries to change the " +"speed of the port will be stuck with 57600 bps." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:420 +#, no-wrap +msgid "Terminals" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:424 +msgid "" +"Terminals provide a convenient and low-cost way to access a FreeBSD system " +"when not at the computer's console or on a connected network. This section " +"describes how to use terminals with FreeBSD." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:427 +msgid "" +"The original UNIX(R) systems did not have consoles. Instead, users logged " +"in and ran programs through terminals that were connected to the computer's " +"serial ports." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:430 +msgid "" +"The ability to establish a login session on a serial port still exists in " +"nearly every UNIX(R)-like operating system today, including FreeBSD. 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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:434 +msgid "" +"Many terminals can be attached to a FreeBSD system. An older spare computer " +"can be used as a terminal wired into a more powerful computer running " +"FreeBSD. This can turn what might otherwise be a single-user computer into " +"a powerful multiple-user system." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:436 +msgid "FreeBSD supports three types of terminals:" +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:437 +#, no-wrap +msgid "Dumb terminals" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:441 +msgid "" +"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. Instead, dumb terminals connect to a computer that " +"runs the needed programs." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:444 +msgid "" +"There are hundreds of kinds of dumb terminals made by many manufacturers, " +"and 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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:446 +msgid "" +"Dumb terminals are popular in work environments where workers do not need " +"access to graphical applications." +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:447 +#, no-wrap +msgid "Computers Acting as Terminals" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:450 +msgid "" +"Since 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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:453 +msgid "" +"This configuration can be useful. For example, if one user is busy working " +"at the FreeBSD 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 FreeBSD system." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:455 +msgid "" +"There are at least two utilities in the base-system of FreeBSD that can be " +"used to work through a serial connection: man:cu[1] and man:tip[1]." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:457 +msgid "" +"For example, to connect from a client system that runs FreeBSD to the serial " +"connection of another system:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:461 +#, no-wrap +msgid "# cu -l /dev/cuauN\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:465 +msgid "" +"Ports are numbered starting from zero. This means that [.filename]#COM1# is " +"[.filename]#/dev/cuau0#." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:467 +msgid "" +"Additional programs are available through the Ports Collection, such as " +"package:comms/minicom[]." +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:468 +#, no-wrap +msgid "X Terminals" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:472 +msgid "" +"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 Xorg application." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:474 +msgid "" +"This chapter does not cover the setup, configuration, or use of X terminals." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:476 +#, no-wrap +msgid "Terminal Configuration" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:480 +msgid "" +"This section describes how to configure a FreeBSD system to enable a login " +"session on a serial terminal. It assumes that the system recognizes the " +"serial port to which the terminal is connected and that the terminal is " +"connected with the correct cable." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:488 +msgid "" +"In FreeBSD, `init` reads [.filename]#/etc/ttys# and starts a `getty` process " +"on the available terminals. The `getty` process is responsible for reading " +"a login name and starting the `login` program. The ports on the FreeBSD " +"system which allow logins are listed in [.filename]#/etc/ttys#. For " +"example, the first virtual console, [.filename]#ttyv0#, has an entry in this " +"file, allowing logins on the console. This file also contains entries for " +"the other virtual consoles, serial ports, and pseudo-ttys. For a hardwired " +"terminal, the serial port's [.filename]#/dev# entry is listed without the `/" +"dev` part. For example, [.filename]#/dev/ttyv0# is listed as `ttyv0`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:490 +msgid "" +"The default [.filename]#/etc/ttys# configures support for the first four " +"serial ports, [.filename]#ttyu0# through [.filename]#ttyu3#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:497 +#, no-wrap +msgid "" +"ttyu0 \"/usr/libexec/getty std.9600\" dialup off secure\n" +"ttyu1 \"/usr/libexec/getty std.9600\" dialup off secure\n" +"ttyu2 \"/usr/libexec/getty std.9600\" dialup off secure\n" +"ttyu3 \"/usr/libexec/getty std.9600\" dialup off secure\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:501 +msgid "" +"When attaching a terminal to one of those ports, modify the default entry to " +"set the required speed and terminal type, to turn the device `on` and, if " +"needed, to change the port's `secure` setting. If the terminal is connected " +"to another port, add an entry for the port." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:506 +msgid "" +"<<ex-etc-ttys>> configures two terminals in [.filename]#/etc/ttys#. The " +"first entry configures a Wyse-50 connected to [.filename]#COM2#. The second " +"entry configures an old computer running Procomm terminal software emulating " +"a VT-100 terminal. The computer is connected to the sixth serial port on a " +"multi-port serial card." +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:509 +#, no-wrap +msgid "Configuring Terminal Entries" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:516 +#, no-wrap +msgid "" +"ttyu1 \"/usr/libexec/getty std.38400\" wy50 on insecure\n" +"ttyu5 \"/usr/libexec/getty std.19200\" vt100 on insecure\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:519 +msgid "The first field specifies the device name of the serial terminal." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:529 +msgid "" +"The second field tells `getty` to initialize and open the line, set the line " +"speed, prompt for a user name, and then execute the `login` program. The " +"optional _getty type_ configures characteristics on the terminal line, like " +"bps rate and parity. The available getty types are listed in [.filename]#/" +"etc/gettytab#. In almost all cases, the getty types that start with `std` " +"will work for hardwired terminals as these entries ignore parity. There is " +"a `std` entry for each bps rate from 110 to 115200. Refer to man:" +"gettytab[5] for more information. When setting the getty type, make sure to " +"match the communications settings used by the terminal. For this example, " +"the Wyse-50 uses no parity and connects at 38400 bps. The computer uses no " +"parity and connects at 19200 bps." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:534 +msgid "" +"The third field is the type of terminal. For dial-up ports, `unknown` or " +"`dialup` is typically used since users may dial up with practically any type " +"of terminal or software. Since the terminal type does not change for " +"hardwired terminals, a real terminal type from [.filename]#/etc/termcap# can " +"be specified. For this example, the Wyse-50 uses the real terminal type " +"while the computer running Procomm is set to emulate a VT-100." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:537 +msgid "" +"The fourth field specifies if the port should be enabled. To enable logins " +"on this port, this field must be set to `on`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:543 +msgid "" +"The final field is used to specify whether the port is secure. Marking a " +"port as `secure` means that it is trusted enough to allow `root` to login " +"from that port. Insecure ports do not allow `root` logins. On an insecure " +"port, users must login from unprivileged accounts and then use `su` or a " +"similar mechanism to gain superuser privileges, as described in crossref:" +"basics[users-superuser,“The Superuser Account”]. For security reasons, it " +"is recommended to change this setting to `insecure`." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:546 +msgid "" +"After making any changes to [.filename]#/etc/ttys#, send a SIGHUP (hangup) " +"signal to the `init` process to force it to re-read its configuration file:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:550 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:724 +#, no-wrap +msgid "# kill -HUP 1\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:553 +msgid "" +"Since `init` is always the first process run on a system, it always has a " +"process ID of `1`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:555 +msgid "" +"If everything is set up correctly, all cables are in place, and the " +"terminals are powered up, a `getty` process should now be running on each " +"terminal and login prompts should be available on each terminal." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:557 +#, no-wrap +msgid "Troubleshooting the Connection" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:561 +msgid "" +"Even with the most meticulous attention to detail, something could still go " +"wrong while setting up a terminal. Here is a list of common symptoms and " +"some suggested fixes." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:564 +msgid "" +"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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:567 +msgid "" +"Make sure the cable is connected firmly to both the terminal and the FreeBSD " +"computer. Make sure it is the right kind of cable." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:571 +msgid "" +"Make sure the terminal and FreeBSD 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." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:574 +msgid "" +"Use `ps` to make sure that a `getty` process is running and serving the " +"terminal. For example, the following listing shows that a `getty` is " +"running on the second serial port, [.filename]#ttyu1#, and is using the " +"`std.38400` entry in [.filename]#/etc/gettytab#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:579 +#, no-wrap +msgid "" +"# ps -axww|grep ttyu\n" +"22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyu1\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:583 +msgid "" +"If no `getty` process is running, make sure the port is enabled in [." +"filename]#/etc/ttys#. Remember to run `kill -HUP 1` after modifying [." +"filename]#/etc/ttys#." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:588 +msgid "" +"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 accept typed input, " +"the terminal or cable may not support hardware handshaking. Try changing " +"the entry in [.filename]#/etc/ttys# from `std.38400` to `3wire.38400`, then " +"run `kill -HUP 1` after modifying [.filename]#/etc/ttys#. The `3wire` entry " +"is similar to `std`, but ignores hardware handshaking. The bps may also " +"need to be reduced or software flow control enabled when using `3wire` to " +"prevent buffer overflows." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:592 +msgid "" +"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 [." +"filename]#/etc/ttys# and run `kill -HUP 1`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:594 +msgid "" +"If characters appear doubled and the password appears when typed, switch the " +"terminal, or the terminal emulation software, from \"half duplex\" or " +"\"local echo\" to \"full duplex.\"" +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:596 +#, no-wrap +msgid "Dial-in Service" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:600 +msgid "" +"Configuring a FreeBSD system for dial-in service is similar to configuring " +"terminals, except that modems are used instead of terminal devices. FreeBSD " +"supports both external and internal modems." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:602 +msgid "" +"External modems are more convenient because they often can be configured via " +"parameters stored in non-volatile RAM and they usually provide lighted " +"indicators that display the state of important RS-232 signals, indicating " +"whether the modem is operating properly." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:605 +msgid "" +"Internal modems usually lack non-volatile RAM, so their configuration may be " +"limited to setting DIP switches. If the internal modem has any signal " +"indicator lights, they are difficult to view when the system's cover is in " +"place." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:608 +msgid "" +"When using an external modem, a proper cable is needed. A standard RS-232C " +"serial cable should suffice." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:612 +msgid "" +"FreeBSD needs the RTS and CTS signals for flow control at speeds above 2400 " +"bps, the CD signal to detect when a call has been answered or the line has " +"been hung up, and the DTR signal to reset the modem after a session is " +"complete. Some cables are wired without all of the needed signals, so if a " +"login session does not go away when the line hangs up, there may be a " +"problem with the cable. Refer to <<term-cables-null>> for more information " +"about these signals." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:615 +msgid "" +"Like other UNIX(R)-like operating systems, FreeBSD uses the hardware signals " +"to find out when a call has been answered or a line has been hung up and to " +"hangup and reset the modem after a call. FreeBSD avoids sending commands to " +"the modem or watching for status reports from the modem." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:622 +msgid "" +"FreeBSD supports the NS8250, NS16450, NS16550, and NS16550A-based RS-232C " +"(CCITT V.24) communications interfaces. The 8250 and 16450 devices have " +"single-character buffers. The 16550 device provides a 16-character buffer, " +"which allows for better system performance. Bugs in plain 16550 devices " +"prevent the use of the 16-character buffer, so use 16550A devices if " +"possible. As single-character-buffer devices require more work by the " +"operating system than the 16-character-buffer devices, 16550A-based serial " +"interface cards are preferred. If the system has many active serial ports " +"or will have a heavy load, 16550A-based cards are better for low-error-rate " +"communications." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:624 +msgid "" +"The rest of this section demonstrates how to configure a modem to receive " +"incoming connections, how to communicate with the modem, and offers some " +"troubleshooting tips." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:626 +#, no-wrap +msgid "Modem Configuration" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:633 +msgid "" +"As with terminals, `init` spawns a `getty` process for each configured " +"serial port used for dial-in connections. When a user dials the modem's " +"line and the modems connect, the \"Carrier Detect\" signal is reported by " +"the modem. The kernel notices that the carrier has been detected and " +"instructs `getty` to open the port and display a `login:` prompt at the " +"specified initial line speed. In a typical configuration, if garbage " +"characters are received, usually due to the modem's connection speed being " +"different than the configured speed, `getty` tries adjusting the line speeds " +"until it receives reasonable characters. After the user enters their login " +"name, `getty` executes `login`, which completes the login process by asking " +"for the user's password and then starting the user's shell." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:638 +msgid "" +"There are two schools of thought regarding dial-up modems. One " +"configuration method is to set the modems and systems so that no matter at " +"what speed a remote user dials in, the dial-in RS-232 interface runs at a " +"locked speed. The benefit of this configuration is that the remote user " +"always sees a system login prompt immediately. The downside is that the " +"system does not know what a user's true data rate is, so full-screen " +"programs like Emacs will not adjust their screen-painting methods to make " +"their response better for slower connections." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:645 +msgid "" +"The second method is to configure the RS-232 interface to vary its speed " +"based on the remote user's connection speed. As `getty` does not understand " +"any particular modem's connection speed reporting, it gives a `login:` " +"message at an initial speed and watches the characters that come back in " +"response. If the user sees junk, they should press kbd:[Enter] until they " +"see a recognizable prompt. If the data rates do not match, `getty` sees " +"anything the user types as junk, tries the next speed, and gives the `login:" +"` prompt again. This procedure normally only takes a keystroke or two " +"before the user sees a good prompt. This login sequence does not look as " +"clean as the locked-speed method, but a user on a low-speed connection " +"should receive better interactive response from full-screen programs." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:652 +msgid "" +"When locking a modem's data communications rate at a particular speed, no " +"changes to [.filename]#/etc/gettytab# should be needed. However, for a " +"matching-speed configuration, additional entries may be required in order to " +"define the speeds to use for the modem. This example configures a 14.4 Kbps " +"modem with a top interface speed of 19.2 Kbps using 8-bit, no parity " +"connections. It configures `getty` to start the communications rate for a " +"V.32bis connection at 19.2 Kbps, then cycles through 9600 bps, 2400 bps, " +"1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate cycling is " +"implemented with the `nx=` (next table) capability. Each line uses a `tc=` " +"(table continuation) entry to pick up the rest of the settings for a " +"particular data rate." +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:668 +#, no-wrap +msgid "" +"#\n" +"# Additions for a V.32bis Modem\n" +"#\n" +"um|V300|High Speed Modem at 300,8-bit:\\\n" +" :nx=V19200:tc=std.300:\n" +"un|V1200|High Speed Modem at 1200,8-bit:\\\n" +" :nx=V300:tc=std.1200:\n" +"uo|V2400|High Speed Modem at 2400,8-bit:\\\n" +" :nx=V1200:tc=std.2400:\n" +"up|V9600|High Speed Modem at 9600,8-bit:\\\n" +" :nx=V2400:tc=std.9600:\n" +"uq|V19200|High Speed Modem at 19200,8-bit:\\\n" +" :nx=V9600:tc=std.19200:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:671 +msgid "" +"For a 28.8 Kbps modem, or to take advantage of compression on a 14.4 Kbps " +"modem, use a higher communications rate, as seen in this example:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:688 +#, no-wrap +msgid "" +"#\n" +"# Additions for a V.32bis or V.34 Modem\n" +"# Starting at 57.6 Kbps\n" +"#\n" +"vm|VH300|Very High Speed Modem at 300,8-bit:\\\n" +" :nx=VH57600:tc=std.300:\n" +"vn|VH1200|Very High Speed Modem at 1200,8-bit:\\\n" +" :nx=VH300:tc=std.1200:\n" +"vo|VH2400|Very High Speed Modem at 2400,8-bit:\\\n" +" :nx=VH1200:tc=std.2400:\n" +"vp|VH9600|Very High Speed Modem at 9600,8-bit:\\\n" +" :nx=VH2400:tc=std.9600:\n" +"vq|VH57600|Very High Speed Modem at 57600,8-bit:\\\n" +" :nx=VH9600:tc=std.57600:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:691 +msgid "" +"For a slow CPU or a heavily loaded system without 16550A-based serial ports, " +"this configuration may produce `uart` \"silo\" errors at 57.6 Kbps." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:694 +msgid "" +"The configuration of [.filename]#/etc/ttys# is similar to <<ex-etc-ttys>>, " +"but a different argument is passed to `getty` and `dialup` is used for the " +"terminal type. Replace _xxx_ with the process `init` will run on the device:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:698 +#, no-wrap +msgid "ttyu0 \"/usr/libexec/getty xxx\" dialup on\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:702 +msgid "" +"The `dialup` terminal type can be changed. For example, setting `vt102` as " +"the default terminal type allows users to use VT102 emulation on their " +"remote systems." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:705 +msgid "" +"For a locked-speed configuration, specify the speed with a valid type listed " +"in [.filename]#/etc/gettytab#. This example is for a modem whose port speed " +"is locked at 19.2 Kbps:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:709 +#, no-wrap +msgid "ttyu0 \"/usr/libexec/getty std.19200\" dialup on\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:713 +msgid "" +"In a matching-speed configuration, the entry needs to reference the " +"appropriate beginning \"auto-baud\" entry in [.filename]#/etc/gettytab#. To " +"continue the example for a matching-speed modem that starts at 19.2 Kbps, " +"use this entry:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:717 +#, no-wrap +msgid "ttyu0 \"/usr/libexec/getty V19200\" dialup on\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:720 +msgid "" +"After editing [.filename]#/etc/ttys#, wait until the modem is properly " +"configured and connected before signaling `init`:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:729 +msgid "" +"High-speed modems, like V.32, V.32bis, and V.34 modems, use hardware (`RTS/" +"CTS`) flow control. Use `stty` to set the hardware flow control flag for " +"the modem port. This example sets the `crtscts` flag on [.filename]#COM2#'s " +"dial-in and dial-out initialization devices:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:734 +#, no-wrap +msgid "" +"# stty -f /dev/ttyu1.init crtscts\n" +"# stty -f /dev/cuau1.init crtscts\n" +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:736 +#, no-wrap +msgid "Troubleshooting" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:739 +msgid "" +"This section provides a few tips for troubleshooting a dial-up modem that " +"will not connect to a FreeBSD system." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:743 +msgid "" +"Hook up the modem to the FreeBSD system and boot the system. If the modem " +"has status indication lights, watch to see whether the modem's DTR indicator " +"lights when the `login:` prompt appears on the system's console. If it " +"lights up, that should mean that FreeBSD has started a `getty` process on " +"the appropriate communications port and is waiting for the modem to accept a " +"call." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:745 +msgid "" +"If the DTR indicator does not light, login to the FreeBSD system through the " +"console and type `ps ax` to see if FreeBSD is running a `getty` process on " +"the correct port:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:749 +#, no-wrap +msgid " 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu0\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:753 +msgid "" +"If the second column contains a `d0` instead of a `??` and the modem has not " +"accepted a call yet, this means that `getty` has completed its open on the " +"communications port. This could indicate a problem with the cabling or a " +"misconfigured modem because `getty` should not be able to open the " +"communications port until the carrier detect signal has been asserted by the " +"modem." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:756 +msgid "" +"If no `getty` processes are waiting to open the port, double-check that the " +"entry for the port is correct in [.filename]#/etc/ttys#. Also, check [." +"filename]#/var/log/messages# to see if there are any log messages from " +"`init` or `getty`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:762 +msgid "" +"Next, try dialing into the system. Be sure to use 8 bits, no parity, and 1 " +"stop bit on the remote system. If a prompt does not appear right away, or " +"the prompt shows garbage, try pressing kbd:[Enter] about once per second. " +"If there is still no `login:` prompt, try sending a `BREAK`. When using a " +"high-speed modem, try dialing again after locking the dialing modem's " +"interface speed." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:764 +msgid "" +"If there is still no `login:` prompt, check [.filename]#/etc/gettytab# again " +"and double-check that:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:766 +msgid "" +"The initial capability name specified in the entry in [.filename]#/etc/ttys# " +"matches the name of a capability in [.filename]#/etc/gettytab#." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:767 +msgid "Each `nx=` entry matches another [.filename]#gettytab# capability name." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:768 +msgid "Each `tc=` entry matches another [.filename]#gettytab# capability name." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:771 +msgid "" +"If the modem on the FreeBSD system will not answer, make sure that the modem " +"is configured to answer the phone when DTR is asserted. If the modem seems " +"to be configured correctly, verify that the DTR line is asserted by checking " +"the modem's indicator lights." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:773 +msgid "" +"If it still does not work, try sending an email to the {freebsd-questions} " +"describing the modem and the problem." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:775 +#, no-wrap +msgid "Dial-out Service" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:779 +msgid "" +"The following are tips for getting the host to connect over the modem to " +"another computer. This is appropriate for establishing a terminal session " +"with a remote host." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:783 +msgid "" +"This kind of connection can be helpful to get a file on the Internet if " +"there are problems using PPP. If PPP is not working, use the terminal " +"session to FTP the needed file. Then use zmodem to transfer it to the " +"machine." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:785 +#, no-wrap +msgid "Using a Stock Hayes Modem" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:789 +msgid "" +"A generic Hayes dialer is built into `tip`. Use `at=hayes` in [.filename]#/" +"etc/remote#." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:792 +msgid "" +"The Hayes driver is not smart enough to recognize some of the advanced " +"features of newer modems messages like `BUSY`, `NO DIALTONE`, or `CONNECT " +"115200`. Turn those messages off when using `tip` with `ATX0&W`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:796 +msgid "" +"The dial timeout for `tip` is 60 seconds. The modem should use something " +"less, or else `tip` will think there is a communication problem. Try " +"`ATS7=45&W`." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:798 +#, no-wrap +msgid "Using `AT` Commands" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:802 +msgid "" +"Create a \"direct\" entry in [.filename]#/etc/remote#. For example, if the " +"modem is hooked up to the first serial port, [.filename]#/dev/cuau0#, use " +"the following line:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:806 +#, no-wrap +msgid "cuau0:dv=/dev/cuau0:br#19200:pa=none\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:810 +msgid "" +"Use the highest bps rate the modem supports in the `br` capability. Then, " +"type `tip cuau0` to connect to the modem." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:812 +msgid "Or, use `cu` as `root` with the following command:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:816 +#, no-wrap +msgid "# cu -lline -sspeed\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:820 +msgid "" +"_line_ is the serial port, such as [.filename]#/dev/cuau0#, and _speed_ is " +"the speed, such as `57600`. When finished entering the AT commands, type `~." +"` to exit." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:822 +#, no-wrap +msgid "The `@` Sign Does Not Work" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:826 +msgid "" +"The `@` sign in the phone number capability tells `tip` to look in [." +"filename]#/etc/phones# for a phone number. But, the `@` sign is also a " +"special character in capability files like [.filename]#/etc/remote#, so it " +"needs to be escaped with a backslash:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:830 +#, no-wrap +msgid "pn=\\@\n" +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:833 +#, no-wrap +msgid "Dialing from the Command Line" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:836 +msgid "Put a \"generic\" entry in [.filename]#/etc/remote#. For example:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:843 +#, no-wrap +msgid "" +"tip115200|Dial any phone number at 115200 bps:\\\n" +" :dv=/dev/cuau0:br#115200:at=hayes:pa=none:du:\n" +"tip57600|Dial any phone number at 57600 bps:\\\n" +" :dv=/dev/cuau0:br#57600:at=hayes:pa=none:du:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:846 +msgid "This should now work:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:850 +#, no-wrap +msgid "# tip -115200 5551234\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:853 +msgid "Users who prefer `cu` over `tip`, can use a generic `cu` entry:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:858 +#, no-wrap +msgid "" +"cu115200|Use cu to dial any number at 115200bps:\\\n" +" :dv=/dev/cuau1:br#57600:at=hayes:pa=none:du:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:861 +msgid "and type:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:865 +#, no-wrap +msgid "# cu 5551234 -s 115200\n" +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:868 +#, no-wrap +msgid "Setting the bps Rate" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:873 +msgid "" +"Put in an entry for `tip1200` or `cu1200`, but go ahead and use whatever bps " +"rate is appropriate with the `br` capability. `tip` thinks a good default " +"is 1200 bps which is why it looks for a `tip1200` entry. 1200 bps does not " +"have to be used, though." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:875 +#, no-wrap +msgid "Accessing a Number of Hosts Through a Terminal Server" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:879 +msgid "" +"Rather than waiting until connected and typing `CONNECT _host_` each time, " +"use ``tip``'s `cm` capability. For example, these entries in [.filename]#/" +"etc/remote# will let you type `tip pain` or `tip muffin` to connect to the " +"hosts `pain` or `muffin`, and `tip deep13` to connect to the terminal server." +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:888 +#, no-wrap +msgid "" +"pain|pain.deep13.com|Forrester's machine:\\\n" +" :cm=CONNECT pain\\n:tc=deep13:\n" +"muffin|muffin.deep13.com|Frank's machine:\\\n" +" :cm=CONNECT muffin\\n:tc=deep13:\n" +"deep13:Gizmonics Institute terminal server:\\\n" +" :dv=/dev/cuau2:br#38400:at=hayes:du:pa=none:pn=5551234:\n" +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:891 +#, no-wrap +msgid "Using More Than One Line with `tip`" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:894 +msgid "" +"This is often a problem where a university has several modem lines and " +"several thousand students trying to use them." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:896 +msgid "" +"Make an entry in [.filename]#/etc/remote# and use `@` for the `pn` " +"capability:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:903 +#, no-wrap +msgid "" +"big-university:\\\n" +" :pn=\\@:tc=dialout\n" +"dialout:\\\n" +" :dv=/dev/cuau3:br#9600:at=courier:du:pa=none:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:906 +msgid "Then, list the phone numbers in [.filename]#/etc/phones#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:913 +#, no-wrap +msgid "" +"big-university 5551111\n" +"big-university 5551112\n" +"big-university 5551113\n" +"big-university 5551114\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:917 +msgid "" +"`tip` will try each number in the listed order, then give up. To keep " +"retrying, run `tip` in a `while` loop." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:919 +#, no-wrap +msgid "Using the Force Character" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:923 +msgid "" +"kbd:[Ctrl+P] is the default \"force\" character, used to tell `tip` that the " +"next character is literal data. The force character can be set to any other " +"character with the `~s` escape, which means \"set a variable.\"" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:928 +msgid "" +"Type `~sforce=_single-char_` followed by a newline. _single-char_ is any " +"single character. If _single-char_ is left out, then the force character is " +"the null character, which is accessed by typing kbd:[Ctrl+2] or kbd:" +"[Ctrl+Space]. A pretty good value for _single-char_ is kbd:[Shift+Ctrl+6], " +"which is only used on some terminal servers." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:930 +msgid "" +"To change the force character, specify the following in [.filename]#~/." +"tiprc#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:934 +#, no-wrap +msgid "force=single-char\n" +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:937 +#, no-wrap +msgid "Upper Case Characters" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:942 +msgid "" +"This happens when kbd:[Ctrl+A] is pressed, which is ``tip``'s \"raise " +"character\", specially designed for people with broken caps-lock keys. Use " +"`~s` to set `raisechar` to something reasonable. It can be set to be the " +"same as the force character, if neither feature is used." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:944 +msgid "" +"Here is a sample [.filename]#~/.tiprc# for Emacs users who need to type kbd:" +"[Ctrl+2] and kbd:[Ctrl+A]:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:949 +#, no-wrap +msgid "" +"force=^^\n" +"raisechar=^^\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:952 +msgid "The `^^` is kbd:[Shift+Ctrl+6]." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:954 +#, no-wrap +msgid "File Transfers with `tip`" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:960 +msgid "" +"When talking to another UNIX(R)-like operating system, files can be sent and " +"received using `~p` (put) and `~t` (take). These commands run `cat` and " +"`echo` on the remote system to accept and send files. The syntax is: `~p` " +"local-file [ remote-file ] `~t` remote-file [ local-file ]" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:962 +msgid "" +"There is no error checking, so another protocol, like zmodem, should " +"probably be used." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:964 +#, no-wrap +msgid "Using zmodem with `tip`?" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:968 +msgid "" +"To receive files, start the sending program on the remote end. Then, type " +"`~C rz` to begin receiving them locally." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:971 +msgid "" +"To send files, start the receiving program on the remote end. Then, type " +"`~C sz _files_` to send them to the remote system." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:973 +#, no-wrap +msgid "Setting Up the Serial Console" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:977 +msgid "" +"FreeBSD has the ability to boot a system with a dumb terminal on a serial " +"port as a console. This configuration is useful for system administrators " +"who wish to install FreeBSD on machines that have no keyboard or monitor " +"attached, and developers who want to debug the kernel or device drivers." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:981 +msgid "" +"As described in crossref:boot[boot,The FreeBSD Booting Process], FreeBSD " +"employs a three stage bootstrap. The first two stages are in the boot block " +"code which is stored at the beginning of the FreeBSD slice on the boot " +"disk. The boot block then loads and runs the boot loader as the third stage " +"code." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:983 +msgid "" +"In order to set up booting from a serial console, the boot block code, the " +"boot loader code, and the kernel need to be configured." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:985 +#, no-wrap +msgid "Quick Serial Console Configuration" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:989 +msgid "" +"This section provides a fast overview of setting up the serial console. " +"This procedure can be used when the dumb terminal is connected to [." +"filename]#COM1#." +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:991 +#, no-wrap +msgid "Procedure: Configuring a Serial Console on [.filename]#COM1#" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:993 +msgid "" +"Connect the serial cable to [.filename]#COM1# and the controlling terminal." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:994 +msgid "" +"To configure boot messages to display on the serial console, issue the " +"following command as the superuser:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:998 +#, no-wrap +msgid "# echo 'console=\"comconsole\"' >> /boot/loader.conf\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1001 +msgid "" +"Edit [.filename]#/etc/ttys# and change `off` to `on` and `dialup` to `vt100` " +"for the [.filename]#ttyu0# entry. Otherwise, a password will not be required " +"to connect via the serial console, resulting in a potential security hole." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1002 +msgid "Reboot the system to see if the changes took effect." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1004 +msgid "" +"If a different configuration is required, see the next section for a more in-" +"depth configuration explanation." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1006 +#, no-wrap +msgid "In-Depth Serial Console Configuration" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1009 +msgid "" +"This section provides a more detailed explanation of the steps needed to " +"setup a serial console in FreeBSD." +msgstr "" + +#. type: Block title +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1011 +#, no-wrap +msgid "Procedure: Configuring a Serial Console" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1013 +msgid "Prepare a serial cable." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1016 +msgid "" +"Use either a null-modem cable or a standard serial cable and a null-modem " +"adapter. See <<term-cables-null>> for a discussion on serial cables." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1017 +msgid "Unplug the keyboard." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1020 +msgid "" +"Many systems probe for the keyboard during the Power-On Self-Test (POST) and " +"will generate an error if the keyboard is not detected. Some machines will " +"refuse to boot until the keyboard is plugged in." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1022 +msgid "" +"If the computer complains about the error, but boots anyway, no further " +"configuration is needed." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1025 +msgid "" +"If the computer refuses to boot without a keyboard attached, configure the " +"BIOS so that it ignores this error. Consult the motherboard's manual for " +"details on how to do this." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1032 +msgid "" +"Try setting the keyboard to \"Not installed\" in the BIOS. This setting " +"tells the BIOS not to probe for a keyboard at power-on so it should not " +"complain if the keyboard is absent. If that option is not present in the " +"BIOS, look for an \"Halt on Error\" option instead. Setting this to \"All " +"but Keyboard\" or to \"No Errors\" will have the same effect." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1036 +msgid "" +"If the system has a PS/2(R) mouse, unplug it as well. PS/2(R) mice share " +"some hardware with the keyboard and leaving the mouse plugged in can fool " +"the keyboard probe into thinking the keyboard is still there." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1044 +msgid "" +"While most systems will boot without a keyboard, quite a few will not boot " +"without a graphics adapter. Some systems can be configured to boot with no " +"graphics adapter by changing the \"graphics adapter\" setting in the BIOS " +"configuration to \"Not installed\". Other systems do not support this " +"option and will refuse to boot if there is no display hardware in the " +"system. With these machines, leave some kind of graphics card plugged in, " +"even if it is just a junky mono board. A monitor does not need to be " +"attached." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1047 +msgid "" +"Plug a dumb terminal, an old computer with a modem program, or the serial " +"port on another UNIX(R) box into the serial port." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1048 +msgid "" +"Add the appropriate `hint.uart.*` entries to [.filename]#/boot/device.hints# " +"for the serial port. Some multi-port cards also require kernel configuration " +"options. Refer to man:uart[4] for the required options and device hints for " +"each supported serial port." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1049 +msgid "" +"Create [.filename]#boot.config# in the root directory of the `a` partition " +"on the boot drive." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1053 +msgid "" +"This file instructs the boot block code how to boot the system. In order to " +"activate the serial console, one or more of the following options are " +"needed. When using multiple options, include them all on the same line:" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1054 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1107 +#, no-wrap +msgid "`-h`" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1059 +msgid "" +"Toggles between the internal and serial consoles. Use this to switch " +"console devices. For instance, to boot from the internal (video) console, " +"use `-h` to direct the boot loader and the kernel to use the serial port as " +"its console device. Alternatively, to boot from the serial port, use `-h` " +"to tell the boot loader and the kernel to use the video display as the " +"console instead." +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1060 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1110 +#, no-wrap +msgid "`-D`" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1066 +msgid "" +"Toggles between the single and dual console configurations. In the single " +"configuration, the console will be either the internal console (video " +"display) or the serial port, depending on the state of `-h`. In the dual " +"console configuration, both the video display and the serial port will " +"become the console at the same time, regardless of the state of `-h`. " +"However, the dual console configuration takes effect only while the boot " +"block is running. Once the boot loader gets control, the console specified " +"by `-h` becomes the only console." +msgstr "" + +#. type: Labeled list +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1067 +#, no-wrap +msgid "`-P`" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1069 +msgid "" +"Makes the boot block probe the keyboard. If no keyboard is found, the `-D` " +"and `-h` options are automatically set." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1076 +msgid "" +"Due to space constraints in the current version of the boot blocks, `-P` is " +"capable of detecting extended keyboards only. Keyboards with less than 101 " +"keys and without F11 and F12 keys may not be detected. Keyboards on some " +"laptops may not be properly found because of this limitation. If this is " +"the case, do not use `-P`." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1080 +msgid "" +"Use either `-P` to select the console automatically or `-h` to activate the " +"serial console. Refer to man:boot[8] and man:boot.config[5] for more " +"details." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1084 +msgid "" +"The options, except for `-P`, are passed to the boot loader. The boot " +"loader will determine whether the internal video or the serial port should " +"become the console by examining the state of `-h`. This means that if `-D` " +"is specified but `-h` is not specified in [.filename]#/boot.config#, the " +"serial port can be used as the console only during the boot block as the " +"boot loader will use the internal video display as the console." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1085 +msgid "Boot the machine." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1087 +msgid "" +"When FreeBSD starts, the boot blocks echo the contents of [.filename]#/boot." +"config# to the console. For example:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1092 +#, no-wrap +msgid "" +"/boot.config: -P\n" +"Keyboard: no\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1096 +msgid "" +"The second line appears only if `-P` is in [.filename]#/boot.config# and " +"indicates the presence or absence of the keyboard. These messages go to " +"either the serial or internal console, or both, depending on the option in [." +"filename]#/boot.config#:" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1101 +#, no-wrap +msgid "Options" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1103 +#, no-wrap +msgid "Message goes to" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1104 +#, no-wrap +msgid "none" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1106 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1118 +#, no-wrap +msgid "internal console" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1109 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1120 +#, no-wrap +msgid "serial console" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1112 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1115 +#, no-wrap +msgid "serial and internal consoles" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1113 +#, no-wrap +msgid "`-Dh`" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1116 +#, no-wrap +msgid "`-P`, keyboard present" +msgstr "" + +#. type: Table +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1119 +#, no-wrap +msgid "`-P`, keyboard absent" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1124 +msgid "" +"After the message, there will be a small pause before the boot blocks " +"continue loading the boot loader and before any further messages are printed " +"to the console. Under normal circumstances, there is no need to interrupt " +"the boot blocks, but one can do so in order to make sure things are set up " +"correctly." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1127 +msgid "" +"Press any key, other than kbd:[Enter], at the console to interrupt the boot " +"process. The boot blocks will then prompt for further action:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1133 +#, no-wrap +msgid "" +">> FreeBSD/i386 BOOT\n" +"Default: 0:ad(0,a)/boot/loader\n" +"boot:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1137 +msgid "" +"Verify that the above message appears on either the serial or internal " +"console, or both, according to the options in [.filename]#/boot.config#. If " +"the message appears in the correct console, press kbd:[Enter] to continue " +"the boot process." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1141 +msgid "" +"If there is no prompt on the serial terminal, something is wrong with the " +"settings. Enter `-h` then kbd:[Enter] or kbd:[Return] to tell the boot " +"block (and then the boot loader and the kernel) to choose the serial port " +"for the console. Once the system is up, go back and check what went wrong." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1144 +msgid "" +"During the third stage of the boot process, one can still switch between the " +"internal console and the serial console by setting appropriate environment " +"variables in the boot loader. See man:loader[8] for more information." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1148 +msgid "" +"This line in [.filename]#/boot/loader.conf# or [.filename]#/boot/loader.conf." +"local# configures the boot loader and the kernel to send their boot messages " +"to the serial console, regardless of the options in [.filename]#/boot." +"config#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1152 +#, no-wrap +msgid "console=\"comconsole\"\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1155 +msgid "" +"That line should be the first line of [.filename]#/boot/loader.conf# so that " +"boot messages are displayed on the serial console as early as possible." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1158 +msgid "" +"If that line does not exist, or if it is set to `console=\"vidconsole\"`, " +"the boot loader and the kernel will use whichever console is indicated by `-" +"h` in the boot block. See man:loader.conf[5] for more information." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1160 +msgid "" +"At the moment, the boot loader has no option equivalent to `-P` in the boot " +"block, and there is no provision to automatically select the internal " +"console and the serial console based on the presence of the keyboard." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1167 +msgid "" +"While it is not required, it is possible to provide a `login` prompt over " +"the serial line. To configure this, edit the entry for the serial port in [." +"filename]#/etc/ttys# using the instructions in <<term-config>>. If the " +"speed of the serial port has been changed, change `std.9600` to match the " +"new setting." +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1169 +#, no-wrap +msgid "Setting a Faster Serial Port Speed" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1173 +msgid "" +"By default, the serial port settings are 9600 baud, 8 bits, no parity, and 1 " +"stop bit. To change the default console speed, use one of the following " +"options:" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1176 +msgid "" +"Edit [.filename]#/etc/make.conf# and set `BOOT_COMCONSOLE_SPEED` to the new " +"console speed. Then, recompile and install the boot blocks and the boot " +"loader:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1183 +#, no-wrap +msgid "" +"# cd /sys/boot\n" +"# make clean\n" +"# make\n" +"# make install\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1186 +msgid "" +"If the serial console is configured in some other way than by booting with `-" +"h`, or if the serial console used by the kernel is different from the one " +"used by the boot blocks, add the following option, with the desired speed, " +"to a custom kernel configuration file and compile a new kernel:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1190 +#, no-wrap +msgid "options CONSPEED=19200\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1193 +msgid "" +"Add the `-S__19200__` boot option to [.filename]#/boot.config#, replacing " +"`_19200_` with the speed to use." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1194 +msgid "" +"Add the following options to [.filename]#/boot/loader.conf#. Replace " +"`_115200_` with the speed to use." +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1201 +#, no-wrap +msgid "" +"boot_multicons=\"YES\"\n" +"boot_serial=\"YES\"\n" +"comconsole_speed=\"115200\"\n" +"console=\"comconsole,vidconsole\"\n" +msgstr "" + +#. type: Title === +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1204 +#, no-wrap +msgid "Entering the DDB Debugger from the Serial Line" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1209 +msgid "" +"To configure the ability to drop into the kernel debugger from the serial " +"console, add the following options to a custom kernel configuration file and " +"compile the kernel using the instructions in crossref:" +"kernelconfig[kernelconfig,Configuring the FreeBSD Kernel]. Note that while " +"this is useful for remote diagnostics, it is also dangerous if a spurious " +"BREAK is generated on the serial port. Refer to man:ddb[4] and man:ddb[8] " +"for more information about the kernel debugger." +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/serialcomms/_index.adoc:1214 +#, no-wrap +msgid "" +"options BREAK_TO_DEBUGGER\n" +"options DDB\n" +msgstr "" |