diff options
Diffstat (limited to 'zh_TW.Big5/books/handbook/serialcomms/chapter.xml')
| -rw-r--r-- | zh_TW.Big5/books/handbook/serialcomms/chapter.xml | 295 |
1 files changed, 133 insertions, 162 deletions
diff --git a/zh_TW.Big5/books/handbook/serialcomms/chapter.xml b/zh_TW.Big5/books/handbook/serialcomms/chapter.xml index 1f131746aa..8a42da92eb 100644 --- a/zh_TW.Big5/books/handbook/serialcomms/chapter.xml +++ b/zh_TW.Big5/books/handbook/serialcomms/chapter.xml @@ -5,11 +5,10 @@ $FreeBSD$ Original revision: 1.108 --> - -<chapter id="serialcomms"> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="serialcomms"> <title>Serial Communications</title> - <sect1 id="serial-synopsis"> + <sect1 xml:id="serial-synopsis"> <title>Synopsis</title> <indexterm><primary>serial communications</primary></indexterm> @@ -34,8 +33,7 @@ <para>Before reading this chapter, you should:</para> <itemizedlist> - <listitem><para>Know how to configure and install a new kernel (<xref - linkend="kernelconfig"/>).</para></listitem> + <listitem><para>Know how to configure and install a new kernel (<xref linkend="kernelconfig"/>).</para></listitem> <listitem><para>Understand &unix; permissions and processes (<xref linkend="basics"/>).</para></listitem> <listitem><para>Have access to the technical manual for the serial hardware (modem or multi-port card) that you would like @@ -43,12 +41,12 @@ </itemizedlist> </sect1> - <sect1 id="serial"> + <sect1 xml:id="serial"> <title>Introduction</title> <!-- XXX Write me! --> - <sect2 id="serial-terminology"> + <sect2 xml:id="serial-terminology"> <title>Terminology</title> <variablelist> @@ -98,7 +96,7 @@ seem to bother the curmudgeons quite as much).</para> </sect2> - <sect2 id="serial-cables-ports"> + <sect2 xml:id="serial-cables-ports"> <title>Cables and Ports</title> <para>To connect a modem or terminal to your FreeBSD system, you @@ -107,7 +105,7 @@ hardware and the cable it requires, you can safely skip this section.</para> - <sect3 id="term-cables"> + <sect3 xml:id="term-cables"> <title>Cables</title> <para>There are several different kinds of serial cables. The @@ -116,7 +114,7 @@ for your hardware should describe the type of cable required.</para> - <sect4 id="term-cables-null"> + <sect4 xml:id="term-cables-null"> <title>Null-modem Cables</title> <indexterm> @@ -144,7 +142,7 @@ <row> <entry align="left">Signal</entry> <entry align="left">Pin #</entry> - <entry></entry> + <entry/> <entry align="left">Pin #</entry> <entry align="left">Signal</entry> </row> @@ -236,7 +234,7 @@ <row> <entry align="left">Signal</entry> <entry align="left">Pin #</entry> - <entry></entry> + <entry/> <entry align="left">Pin #</entry> <entry align="left">Signal</entry> </row> @@ -326,7 +324,7 @@ <row> <entry align="left">Signal</entry> <entry align="left">Pin #</entry> - <entry></entry> + <entry/> <entry align="left">Pin #</entry> <entry align="left">Signal</entry> </row> @@ -421,7 +419,7 @@ CTS connect to DCD, DTR connects to DSR, and vice-versa.</para> </sect4> - <sect4 id="term-cables-std"> + <sect4 xml:id="term-cables-std"> <title>Standard RS-232C Cables</title> <indexterm><primary>RS-232C cables</primary></indexterm> @@ -434,7 +432,7 @@ </sect4> </sect3> - <sect3 id="term-ports"> + <sect3 xml:id="term-ports"> <title>Ports</title> <para>Serial ports are the devices through which data is transferred @@ -442,7 +440,7 @@ describes the kinds of ports that exist and how they are addressed in FreeBSD.</para> - <sect4 id="term-portkinds"> + <sect4 xml:id="term-portkinds"> <title>Kinds of Ports</title> <para>Several kinds of serial ports exist. Before you purchase or @@ -459,7 +457,7 @@ the port often works too.</para> </sect4> - <sect4 id="term-portnames"> + <sect4 xml:id="term-portnames"> <title>Port Names</title> <para>In FreeBSD, you access each serial port through an entry in @@ -469,7 +467,7 @@ <itemizedlist> <listitem> <para>Call-in ports are named - <filename>/dev/ttyd<replaceable>N</replaceable></filename> + <filename>/dev/ttydN</filename> where <replaceable>N</replaceable> is the port number, starting from zero. Generally, you use the call-in port for terminals. Call-in ports require that the serial line assert @@ -478,23 +476,23 @@ <listitem> <para>Call-out ports are named - <filename>/dev/cuad<replaceable>N</replaceable></filename>. + <filename>/dev/cuadN</filename>. You usually do not use the call-out port for terminals, just for modems. You may use the call-out port if the serial cable or the terminal does not support the carrier detect signal.</para> <note><para>Call-out ports are named - <filename>/dev/cuaa<replaceable>N</replaceable></filename> in + <filename>/dev/cuaaN</filename> in &os; 5.X and older.</para></note> </listitem> </itemizedlist> <para>If you have connected a terminal to the first serial port - (<devicename>COM1</devicename> in &ms-dos;), then you will + (<filename>COM1</filename> in &ms-dos;), then you will use <filename>/dev/ttyd0</filename> to refer to the terminal. If the terminal is on the second serial port (also known as - <devicename>COM2</devicename>), use + <filename>COM2</filename>), use <filename>/dev/ttyd1</filename>, and so forth.</para> </sect4> @@ -506,10 +504,10 @@ <para>FreeBSD supports four serial ports by default. In the &ms-dos; world, these are known as - <devicename>COM1</devicename>, - <devicename>COM2</devicename>, - <devicename>COM3</devicename>, and - <devicename>COM4</devicename>. FreeBSD currently supports + <filename>COM1</filename>, + <filename>COM2</filename>, + <filename>COM3</filename>, and + <filename>COM4</filename>. FreeBSD currently supports <quote>dumb</quote> multiport serial interface cards, such as the BocaBoard 1008 and 2016, as well as more intelligent multi-port cards such as those made by Digiboard @@ -547,8 +545,7 @@ sio3: type 16550A</screen> have.</para> <para>On &os; 4.X you have to edit your kernel configuration file. - For detailed information on configuring your kernel, please see <xref - linkend="kernelconfig"/>. The relevant device lines would look like + For detailed information on configuring your kernel, please see <xref linkend="kernelconfig"/>. The relevant device lines would look like this:</para> <programlisting>device sio0 at isa? port IO_COM1 irq 4 @@ -584,23 +581,23 @@ device sio3 at isa? port IO_COM4 irq 9</programlisting> <para>Most devices in the kernel are accessed through <quote>device special files</quote>, which are located in the - <filename>/dev</filename> directory. The <devicename>sio</devicename> + <filename>/dev</filename> directory. The <filename>sio</filename> devices are accessed through the - <filename>/dev/ttyd<replaceable>N</replaceable></filename> (dial-in) - and <filename>/dev/cuad<replaceable>N</replaceable></filename> + <filename>/dev/ttydN</filename> (dial-in) + and <filename>/dev/cuadN</filename> (call-out) devices. FreeBSD also provides initialization devices - (<filename>/dev/ttyd<replaceable>N</replaceable>.init</filename> and - <filename>/dev/cuad<replaceable>N</replaceable>.init</filename> on + (<filename>/dev/ttydN.init</filename> and + <filename>/dev/cuadN.init</filename> on &os; 6.X, - <filename>/dev/ttyid<replaceable>N</replaceable></filename> and - <filename>/dev/cuaid<replaceable>N</replaceable></filename> on + <filename>/dev/ttyidN</filename> and + <filename>/dev/cuaidN</filename> on &os; 5.X and older) and locking devices - (<filename>/dev/ttyd<replaceable>N</replaceable>.lock</filename> and - <filename>/dev/cuad<replaceable>N</replaceable>.lock</filename> on + (<filename>/dev/ttydN.lock</filename> and + <filename>/dev/cuadN.lock</filename> on &os; 6.X, - <filename>/dev/ttyld<replaceable>N</replaceable></filename> and - <filename>/dev/cuald<replaceable>N</replaceable></filename> on + <filename>/dev/ttyldN</filename> and + <filename>/dev/cualdN</filename> on &os; 5.X and older). The initialization devices are used to initialize communications port parameters each time a port is opened, such as @@ -624,21 +621,21 @@ device sio3 at isa? port IO_COM4 irq 9</programlisting> <para>A shell script called <command>MAKEDEV</command> in the <filename>/dev</filename> directory manages the device special files. To use <command>MAKEDEV</command> to make dial-up device - special files for <devicename>COM1</devicename> (port 0), + special files for <filename>COM1</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue the command <command>MAKEDEV ttyd0</command>. Likewise, to make dial-up - device special files for <devicename>COM2</devicename> (port 1), + device special files for <filename>COM2</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> <para><command>MAKEDEV</command> not only creates the - <filename>/dev/ttyd<replaceable>N</replaceable></filename> device + <filename>/dev/ttydN</filename> device special files, but also the - <filename>/dev/cuaa<replaceable>N</replaceable></filename>, - <filename>/dev/cuaia<replaceable>N</replaceable></filename>, - <filename>/dev/cuala<replaceable>N</replaceable></filename>, - <filename>/dev/ttyld<replaceable>N</replaceable></filename>, + <filename>/dev/cuaaN</filename>, + <filename>/dev/cuaiaN</filename>, + <filename>/dev/cualaN</filename>, + <filename>/dev/ttyldN</filename>, and - <filename>/dev/ttyid<replaceable>N</replaceable></filename> + <filename>/dev/ttyidN</filename> nodes.</para> <para>After making new device special files, be sure to check the @@ -653,21 +650,21 @@ device sio3 at isa? port IO_COM4 irq 9</programlisting> crw-rw---- 1 uucp dialer 28, 161 Feb 15 14:38 /dev/cuaia1 crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> - <para>These permissions allow the user <username>uucp</username> and - users in the group <username>dialer</username> to use the call-out + <para>These permissions allow the user <systemitem class="username">uucp</systemitem> and + users in the group <systemitem class="username">dialer</systemitem> to use the call-out devices.</para> </sect3> </sect2> - <sect2 id="serial-hw-config"> + <sect2 xml:id="serial-hw-config"> <title>Serial Port Configuration</title> - <indexterm><primary><devicename>ttyd</devicename></primary></indexterm> - <indexterm><primary><devicename>cuad</devicename></primary></indexterm> + <indexterm><primary><filename>ttyd</filename></primary></indexterm> + <indexterm><primary><filename>cuad</filename></primary></indexterm> - <para>The <devicename>ttyd<replaceable>N</replaceable></devicename> (or - <devicename>cuad<replaceable>N</replaceable></devicename>) device is the + <para>The <filename>ttydN</filename> (or + <filename>cuadN</filename>) device is the regular device you will want to open for your applications. When a process opens the device, it will have a default set of terminal I/O settings. You can see these settings with the command</para> @@ -680,7 +677,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> adjust the settings of the <quote>initial state</quote> device. For example, to turn on <option>CLOCAL</option> mode, 8 bit communication, and <option>XON/XOFF</option> flow control by default for - <devicename>ttyd5</devicename>, type:</para> + <filename>ttyd5</filename>, type:</para> <screen>&prompt.root; <userinput>stty -f /dev/ttyd5.init clocal cs8 ixon ixoff</userinput></screen> @@ -701,34 +698,30 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> <para>To prevent certain settings from being changed by an application, make adjustments to the <quote>lock state</quote> device. For example, to lock the speed of - <devicename>ttyd5</devicename> to 57600 bps, type:</para> + <filename>ttyd5</filename> to 57600 bps, type:</para> <screen>&prompt.root; <userinput>stty -f /dev/ttyd5.lock 57600</userinput></screen> <para>Now, an application that opens - <devicename>ttyd5</devicename> and tries to change the speed of + <filename>ttyd5</filename> and tries to change the speed of the port will be stuck with 57600 bps.</para> <indexterm> <primary><command>MAKEDEV</command></primary> </indexterm> <para>Naturally, you should make the initial state and lock state devices - writable only by the <username>root</username> account.</para> + writable only by the <systemitem class="username">root</systemitem> account.</para> </sect2> </sect1> - <sect1 id="term"> - <sect1info> + <sect1 xml:id="term"> + <info><title>Terminals</title> <authorgroup> - <author> - <firstname>Sean</firstname> - <surname>Kelly</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Sean</firstname><surname>Kelly</surname></personname><contrib>Contributed by </contrib></author> <!-- 28 July 1996 --> </authorgroup> - </sect1info> - <title>Terminals</title> + </info> + <indexterm><primary>terminals</primary></indexterm> @@ -737,7 +730,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> a connected network. This section describes how to use terminals with FreeBSD.</para> - <sect2 id="term-uses"> + <sect2 xml:id="term-uses"> <title>Uses and Types of Terminals</title> <para>The original &unix; systems did not have consoles. Instead, people @@ -779,7 +772,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> <para>The remaining subsections describe each kind.</para> - <sect3 id="term-dumb"> + <sect3 xml:id="term-dumb"> <title>Dumb Terminals</title> <para>Dumb terminals are specialized pieces of hardware that let you @@ -802,7 +795,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> the X Window System.</para> </sect3> - <sect3 id="term-pcs"> + <sect3 xml:id="term-pcs"> <title>PCs Acting as Terminals</title> <para>If a <link linkend="term-dumb">dumb terminal</link> has just @@ -817,7 +810,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> computer hooked up as a terminal to the FreeBSD system.</para> </sect3> - <sect3 id="term-x"> + <sect3 xml:id="term-x"> <title>X Terminals</title> <para>X terminals are the most sophisticated kind of terminal @@ -831,7 +824,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> </sect3> </sect2> - <sect2 id="term-config"> + <sect2 xml:id="term-config"> <title>Configuration</title> <para>This section describes what you need to configure on your FreeBSD @@ -850,7 +843,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> program.</para> <para>Thus, to configure terminals for your FreeBSD system the - following steps should be taken as <username>root</username>:</para> + following steps should be taken as <systemitem class="username">root</systemitem>:</para> <procedure> <step> @@ -892,7 +885,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> &man.gettytab.5; and the &man.getty.8; manual pages for more information.</para> - <sect3 id="term-etcttys"> + <sect3 xml:id="term-etcttys"> <title>Adding an Entry to <filename>/etc/ttys</filename></title> <para>The <filename>/etc/ttys</filename> file lists all of the ports @@ -904,7 +897,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> port's <filename>/dev</filename> entry without the <filename>/dev</filename> part (for example, <filename>/dev/ttyv0</filename> would be listed as - <devicename>ttyv0</devicename>).</para> + <filename>ttyv0</filename>).</para> <para>A default FreeBSD install includes an <filename>/etc/ttys</filename> file with support for the first @@ -912,7 +905,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> <filename>ttyd3</filename>. If you are attaching a terminal to one of those ports, you do not need to add another entry.</para> - <example id="ex-etc-ttys"> + <example xml:id="ex-etc-ttys"> <title>Adding Terminal Entries to <filename>/etc/ttys</filename></title> @@ -925,12 +918,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen> entries in the <filename>/etc/ttys</filename> file would look like this:</para> - <programlisting>ttyd1<co - id="co-ttys-line1col1"/> "/usr/libexec/getty std.38400"<co - id="co-ttys-line1col2"/> wy50<co - id="co-ttys-line1col3"/> on<co - id="co-ttys-line1col4"/> insecure<co - id="co-ttys-line1col5"/> + <programlisting>ttyd1<co xml:id="co-ttys-line1col1"/> "/usr/libexec/getty std.38400"<co xml:id="co-ttys-line1col2"/> wy50<co xml:id="co-ttys-line1col3"/> on<co xml:id="co-ttys-line1col4"/> insecure<co xml:id="co-ttys-line1col5"/> ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure </programlisting> @@ -1011,9 +999,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure <para>The final field is used to specify whether the port is secure. Marking a port as secure means that you trust it enough to allow the - <username>root</username> account (or any account with + <systemitem class="username">root</systemitem> account (or any account with a user ID of 0) to login from that port. Insecure - ports do not allow <username>root</username> logins. + ports do not allow <systemitem class="username">root</systemitem> logins. On an insecure port, users must login from unprivileged accounts and then use &man.su.1; or a similar mechanism to gain superuser privileges.</para> @@ -1028,7 +1016,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure </example> </sect3> - <sect3 id="term-hup"> + <sect3 xml:id="term-hup"> <title>Force <command>init</command> to Reread <filename>/etc/ttys</filename></title> @@ -1052,7 +1040,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure </sect3> </sect2> - <sect2 id="term-debug"> + <sect2 xml:id="term-debug"> <title>Troubleshooting Your Connection</title> <para>Even with the most meticulous attention to detail, something could @@ -1140,24 +1128,16 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure </sect2> </sect1> - <sect1 id="dialup"> - <sect1info> + <sect1 xml:id="dialup"> + <info><title>Dial-in Service</title> <authorgroup> - <author> - <firstname>Guy</firstname> - <surname>Helmer</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Guy</firstname><surname>Helmer</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Sean</firstname> - <surname>Kelly</surname> - <contrib>Additions by </contrib> - </author> + <author><personname><firstname>Sean</firstname><surname>Kelly</surname></personname><contrib>Additions by </contrib></author> </authorgroup> - </sect1info> - <title>Dial-in Service</title> + </info> + <indexterm><primary>dial-in service</primary></indexterm> <para>Configuring your FreeBSD system for dial-in service is very @@ -1189,7 +1169,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure cable should suffice as long as all of the normal signals are wired:</para> - <table frame="none" pgwide="1" id="serialcomms-signal-names"> + <table frame="none" pgwide="1" xml:id="serialcomms-signal-names"> <title>Signal Names</title> <tgroup cols="2"> @@ -1460,7 +1440,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ </sect4> </sect3> - <sect3 id="dialup-ttys"> + <sect3 xml:id="dialup-ttys"> <title><filename>/etc/ttys</filename></title> <indexterm> <primary><filename>/etc/ttys</filename></primary> @@ -1480,7 +1460,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ <filename>/dev/ttyd0</filename> is the file that this <command>getty</command> will be watching. The second item, <literal>"/usr/libexec/getty - <replaceable>xxx</replaceable>"</literal> + xxx"</literal> (<replaceable>xxx</replaceable> will be replaced by the initial <filename>gettytab</filename> capability) is the process <command>init</command> will run on the device. The third item, @@ -1526,7 +1506,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ <para>If your modem is locked at a different data rate, substitute the appropriate value for - <literal>std.<replaceable>speed</replaceable></literal> + <literal>std.speed</literal> instead of <literal>std.19200</literal>. Make sure that you use a valid type listed in <filename>/etc/gettytab</filename>.</para> @@ -1564,7 +1544,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ <para>For example to set the <literal>termios</literal> flag <varname>crtscts</varname> on serial port #1's - (<devicename>COM2</devicename>) dial-in and dial-out initialization + (<filename>COM2</filename>) dial-in and dial-out initialization devices, the following lines could be added to <filename>/etc/rc.d/serial</filename>:</para> <programlisting># Serial port initial configuration @@ -1759,7 +1739,7 @@ AT&B2&W</programlisting> <para>If you do not see any <command>getty</command> processes waiting to open the desired - <filename>ttyd<replaceable>N</replaceable></filename> port, + <filename>ttydN</filename> port, double-check your entries in <filename>/etc/ttys</filename> to see if there are any mistakes there. Also, check the log file <filename>/var/log/messages</filename> to see if there are any log @@ -1824,7 +1804,7 @@ AT&B2&W</programlisting> </sect1> - <sect1 id="dialout"> + <sect1 xml:id="dialout"> <title>Dial-out Service</title> <indexterm><primary>dial-out service</primary></indexterm> @@ -1872,7 +1852,7 @@ AT&B2&W</programlisting> </note> </sect2> - <sect2 id="direct-at"> + <sect2 xml:id="direct-at"> <title>How Am I Expected to Enter These AT Commands?</title> <indexterm> @@ -1889,10 +1869,10 @@ AT&B2&W</programlisting> Then, type <command>tip cuad0</command> and you will be connected to your modem.</para> - <para>Or use <command>cu</command> as <username>root</username> with the + <para>Or use <command>cu</command> as <systemitem class="username">root</systemitem> with the following command:</para> - <screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>cu -lline -sspeed</userinput></screen> <para><replaceable>line</replaceable> is the serial port (e.g.<filename>/dev/cuad0</filename>) and @@ -2019,7 +1999,7 @@ big-university 5551114</programlisting> variable.</quote></para> <para>Type - <command>~sforce=<replaceable>single-char</replaceable></command> + <command>~sforce=single-char</command> followed by a newline. <replaceable>single-char</replaceable> is any single character. If you leave out <replaceable>single-char</replaceable>, then the force character is @@ -2114,32 +2094,24 @@ raisechar=^^</programlisting> locally.</para> <para>To send files, start the receiving program on the remote end. - Then, type <command>~C sz <replaceable>files</replaceable></command> + Then, type <command>~C sz files</command> to send them to the remote system.</para> </sect2> </sect1> - <sect1 id="serialconsole-setup"> - <sect1info> + <sect1 xml:id="serialconsole-setup"> + <info><title>Setting Up the Serial Console</title> <authorgroup> - <author> - <firstname>Kazutaka</firstname> - <surname>YOKOTA</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Kazutaka</firstname><surname>YOKOTA</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Bill</firstname> - <surname>Paul</surname> - <contrib>Based on a document by </contrib> - </author> + <author><personname><firstname>Bill</firstname><surname>Paul</surname></personname><contrib>Based on a document by </contrib></author> </authorgroup> - </sect1info> - <title>Setting Up the Serial Console</title> + </info> + <indexterm><primary>serial console</primary></indexterm> - <sect2 id="serialconsole-intro"> + <sect2 xml:id="serialconsole-intro"> <title>Introduction</title> <para>FreeBSD has the ability to boot on a system with only @@ -2160,7 +2132,7 @@ raisechar=^^</programlisting> </sect2> - <sect2 id="serialconsole-howto-fast"> + <sect2 xml:id="serialconsole-howto-fast"> <title>Serial Console Configuration, Terse Version</title> <para>This section assumes that you are using the default setup @@ -2200,7 +2172,7 @@ raisechar=^^</programlisting> <xref linkend="serialconsole-howto"/>.</para> </sect2> - <sect2 id="serialconsole-howto"> + <sect2 xml:id="serialconsole-howto"> <title>Serial Console Configuration</title> <procedure> @@ -2255,31 +2227,31 @@ raisechar=^^</programlisting> </step> <step> - <para>Plug a dumb terminal into <devicename>COM1</devicename> - (<devicename>sio0</devicename>).</para> + <para>Plug a dumb terminal into <filename>COM1</filename> + (<filename>sio0</filename>).</para> <para>If you do not have a dumb terminal, you can use an old PC/XT with a modem program, or the serial port on another &unix; box. If - you do not have a <devicename>COM1</devicename> - (<devicename>sio0</devicename>), get one. At this time, there is - no way to select a port other than <devicename>COM1</devicename> + you do not have a <filename>COM1</filename> + (<filename>sio0</filename>), get one. At this time, there is + no way to select a port other than <filename>COM1</filename> for the boot blocks without recompiling the boot blocks. If you - are already using <devicename>COM1</devicename> for another + are already using <filename>COM1</filename> for another device, you will have to temporarily remove that device and install a new boot block and kernel once you get FreeBSD up and - running. (It is assumed that <devicename>COM1</devicename> will + running. (It is assumed that <filename>COM1</filename> will be available on a file/compute/terminal server anyway; if you - really need <devicename>COM1</devicename> for something else + really need <filename>COM1</filename> for something else (and you cannot switch that something else to - <devicename>COM2</devicename> (<devicename>sio1</devicename>)), + <filename>COM2</filename> (<filename>sio1</filename>)), then you probably should not even be bothering with all this in the first place.)</para> </step> <step> <para>Make sure the configuration file of your kernel has - appropriate flags set for <devicename>COM1</devicename> - (<devicename>sio0</devicename>).</para> + appropriate flags set for <filename>COM1</filename> + (<filename>sio0</filename>).</para> <para>Relevant flags are:</para> @@ -2320,9 +2292,8 @@ raisechar=^^</programlisting> this flag to the serial port unit which you want to use as the serial console. The only use of this flag is to designate the unit for kernel remote - debugging. See <ulink - url="&url.books.developers-handbook;/index.html">The - Developer's Handbook</ulink> for more information on + debugging. See <link xlink:href="&url.books.developers-handbook;/index.html">The + Developer's Handbook</link> for more information on remote debugging.</para> <note> @@ -2499,7 +2470,7 @@ Keyboard: no</screen> interrupt the boot process. The boot blocks will then prompt you for further action. You should now see something like:</para> - <screen>>> FreeBSD/i386 BOOT + <screen>>> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot:</screen> @@ -2524,7 +2495,7 @@ boot:</screen> boot loader. See <xref linkend="serialconsole-loader"/>.</para> </sect2> - <sect2 id="serialconsole-summary"> + <sect2 xml:id="serialconsole-summary"> <title>Summary</title> <para>Here is the summary of various settings discussed in this section @@ -2532,7 +2503,7 @@ boot:</screen> <sect3> <title>Case 1: You Set the Flags to 0x10 for - <devicename>sio0</devicename></title> + <filename>sio0</filename></title> <programlisting>device sio0 at isa? port IO_COM1 flags 0x10 irq 4</programlisting> @@ -2658,7 +2629,7 @@ boot:</screen> </sect3> </sect2> - <sect2 id="serialconsole-tips"> + <sect2 xml:id="serialconsole-tips"> <title>Tips for the Serial Console</title> <sect3> @@ -2684,11 +2655,11 @@ boot:</screen> <programlisting>options CONSPEED=19200</programlisting> </sect3> - <sect3 id="serialconsole-com2"> - <title>Using Serial Port Other Than <devicename>sio0</devicename> for + <sect3 xml:id="serialconsole-com2"> + <title>Using Serial Port Other Than <filename>sio0</filename> for the Console</title> - <para>Using a port other than <devicename>sio0</devicename> as the + <para>Using a port other than <filename>sio0</filename> as the console requires some recompiling. If you want to use another serial port for whatever reasons, recompile the boot blocks, the boot loader and the kernel as follows.</para> @@ -2702,9 +2673,9 @@ boot:</screen> <para>Edit <filename>/etc/make.conf</filename> and set <literal>BOOT_COMCONSOLE_PORT</literal> to the address of the port you want to use (0x3F8, 0x2F8, 0x3E8 or 0x2E8). Only - <devicename>sio0</devicename> through - <devicename>sio3</devicename> (<devicename>COM1</devicename> - through <devicename>COM4</devicename>) can be used; multiport + <filename>sio0</filename> through + <filename>sio3</filename> (<filename>COM1</filename> + through <filename>COM4</filename>) can be used; multiport serial cards will not work. No interrupt setting is needed.</para> </step> @@ -2712,8 +2683,8 @@ boot:</screen> <step> <para>Create a custom kernel configuration file and add appropriate flags for the serial port you want to use. For - example, if you want to make <devicename>sio1</devicename> - (<devicename>COM2</devicename>) the console:</para> + example, if you want to make <filename>sio1</filename> + (<filename>COM2</filename>) the console:</para> <programlisting>device sio1 at isa? port IO_COM2 flags 0x10 irq 3</programlisting> @@ -2745,7 +2716,7 @@ boot:</screen> </procedure> </sect3> - <sect3 id="serialconsole-ddb"> + <sect3 xml:id="serialconsole-ddb"> <title>Entering the DDB Debugger from the Serial Line</title> <para>If you wish to drop into the kernel debugger from the serial @@ -2774,8 +2745,8 @@ ttyd2 "/usr/libexec/getty std.9600" unknown off secure ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting> <para><literal>ttyd0</literal> through <literal>ttyd3</literal> - corresponds to <devicename>COM1</devicename> through - <devicename>COM4</devicename>. Change <literal>off</literal> to + corresponds to <filename>COM1</filename> through + <filename>COM4</filename>. Change <literal>off</literal> to <literal>on</literal> for the desired port. If you have changed the speed of the serial port, you need to change <literal>std.9600</literal> to match the current setting, e.g. @@ -2790,7 +2761,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting> </sect3> </sect2> - <sect2 id="serialconsole-loader"> + <sect2 xml:id="serialconsole-loader"> <title>Changing Console from the Boot Loader</title> <para>Previous sections described how to set up the serial console by @@ -2854,16 +2825,16 @@ start</programlisting> </sect3> <sect3> - <title>Using a Serial Port Other Than <devicename>sio0</devicename> for + <title>Using a Serial Port Other Than <filename>sio0</filename> for the Console</title> <para>You need to recompile the boot loader to use a serial port other - than <devicename>sio0</devicename> for the serial console. Follow the + than <filename>sio0</filename> for the serial console. Follow the procedure described in <xref linkend="serialconsole-com2"/>.</para> </sect3> </sect2> - <sect2 id="serialconsole-caveats"> + <sect2 xml:id="serialconsole-caveats"> <title>Caveats</title> <para>The idea here is to allow people to set up dedicated servers that |