doc-el commit 1019:fa35abe81cc2 - Replace english text of 'seria...

freebsd-doc-el at lists.hellug.gr freebsd-doc-el at lists.hellug.gr
Sun Nov 9 06:50:07 EET 2008


changeset: 1019:fa35abe81cc2
user:      Manolis Kiagias <sonicy at otenet.gr>
date:      2008-11-06 16:55 +0200
details:   http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=fa35abe81cc2

description:
	Replace english text of 'serialcomms' chapter with rev. 1.130 (no changes in synopsis)

diffstat:

1 file changed, 170 insertions(+), 208 deletions(-)
el_GR.ISO8859-7/books/handbook/serialcomms/chapter.sgml |  378 ++++++---------

diffs (truncated from 832 to 300 lines):

diff -r 494933920725 -r fa35abe81cc2 el_GR.ISO8859-7/books/handbook/serialcomms/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/serialcomms/chapter.sgml	Thu Nov 06 16:50:20 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/serialcomms/chapter.sgml	Thu Nov 06 16:55:26 2008 +0200
@@ -7,7 +7,7 @@
   $FreeBSD: doc/el_GR.ISO8859-7/books/handbook/serialcomms/chapter.sgml,v 1.2 2008/01/14 14:19:47 keramida Exp $
 
   %SOURCE%	en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
-  %SRCID%	1.1
+  %SRCID%	1.130
 
 -->
 
@@ -81,7 +81,7 @@
 	  <term>DCE</term>
 	  <indexterm><primary>DCE</primary></indexterm>
 	  <listitem>
-	    <para>Data Communications Equipment &mdash;  your modem</para>
+	    <para>Data Communications Equipment &mdash; your modem</para>
 	  </listitem>
 	</varlistentry>
 
@@ -106,8 +106,8 @@
       <title>Cables and Ports</title>
 
       <para>To connect a modem or terminal to your FreeBSD system, you
-	will need a serial port on your computer and the proper cable to connect
-	to your serial device.  If you are already familiar with your
+	will need a serial port on your computer and the proper cable to
+	connect to your serial device.  If you are already familiar with your
 	hardware and the cable it requires, you can safely skip this
 	section.</para>
 
@@ -116,8 +116,8 @@
 
 	<para>There are several different kinds of serial cables.  The
 	  two most common types for our purposes are null-modem cables
-	  and standard (<quote>straight</quote>) RS-232 cables.  The documentation
-	  for your hardware should describe the type of cable
+	  and standard (<quote>straight</quote>) RS-232 cables.  The
+	  documentation for your hardware should describe the type of cable
 	  required.</para>
 
 	<sect4 id="term-cables-null">
@@ -126,19 +126,22 @@
 	  <indexterm>
 	    <primary>null-modem cable</primary>
 	  </indexterm>
-	  <para>A null-modem cable passes some signals, such as <quote>Signal
-	    Ground</quote>, straight through, but switches other signals.  For
-	    example, the <quote>Transmitted Data</quote> pin on one end goes to the
-	    <quote>Received Data</quote> pin on the other end.</para>
+
+	  <para>A null-modem cable passes some signals, such as
+	    <quote>Signal Ground</quote>, straight through, but switches other
+	    signals.  For example, the <quote>Transmitted Data</quote> pin on
+	    one end goes to the <quote>Received Data</quote> pin on the other
+	    end.</para>
 
 	  <para>You can also construct your own null-modem cable for use with
-	    terminals (e.g., for quality purposes).  This table shows the RS-232C
-	    <link linkend="serialcomms-signal-names">signals</link> and the pin
-	    numbers on a DB-25 connector.  Note that the standard also calls for a
-	    straight-through pin 1 to pin 1 <emphasis>Protective Ground</emphasis>
-	    line, but it is often omitted.  Some terminals work OK using only
-	    pins 2, 3 and 7, while others require different configurations than
-	    the examples shown below.</para>
+	    terminals (e.g., for quality purposes).  This table shows the
+	    RS-232C <link linkend="serialcomms-signal-names">signals</link>
+	    and the pin numbers on a DB-25 connector.  Note that the standard
+	    also calls for a straight-through pin 1 to pin 1
+	    <emphasis>Protective Ground</emphasis> line, but it is often
+	    omitted.  Some terminals work OK using only pins 2, 3 and 7,
+	    while others require different configurations than the examples
+	    shown below.</para>
 
 	  <table frame="none" pgwide="1">
 	    <title>DB-25 to DB-25 Null-Modem Cable</title>
@@ -430,11 +433,11 @@
 	  <indexterm><primary>RS-232C cables</primary></indexterm>
 
 	  <para>A standard serial cable passes all of the RS-232C signals
-	    straight through.  That is, the <quote>Transmitted Data</quote> pin on one
-	    end of the cable goes to the <quote>Transmitted Data</quote> pin on the
-	    other end. This is the type of cable to use to connect a modem to your
-	    FreeBSD system, and is also appropriate for some
-	    terminals.</para>
+	    straight through.  That is, the <quote>Transmitted Data</quote>
+	    pin on one end of the cable goes to the
+	    <quote>Transmitted Data</quote> pin on the other end.  This is
+	    the type of cable to use to connect a modem to your FreeBSD
+	    system, and is also appropriate for some terminals.</para>
 	</sect4>
       </sect3>
 
@@ -454,8 +457,8 @@
 	    your terminal and on the FreeBSD system.</para>
 
 	  <para>Most terminals will have DB-25 ports.  Personal computers,
-	    including PCs running FreeBSD, will have DB-25 or DB-9 ports. If you
-	    have a multiport serial card for your PC, you may have RJ-12 or
+	    including PCs running FreeBSD, will have DB-25 or DB-9 ports.  If
+	    you have a multiport serial card for your PC, you may have RJ-12 or
 	    RJ-45 ports.</para>
 
 	  <para>See the documentation that accompanied the hardware for
@@ -487,10 +490,6 @@
 		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
-		&os;&nbsp;5.X and older.</para></note>
 	    </listitem>
 	  </itemizedlist>
 
@@ -584,18 +583,12 @@
 	and <filename>/dev/cuad<replaceable>N</replaceable></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
-	&os;&nbsp;6.X,
-	<filename>/dev/ttyid<replaceable>N</replaceable></filename> and
-	<filename>/dev/cuaia<replaceable>N</replaceable></filename> on
-	&os;&nbsp;5.X) and
+	<filename>/dev/cuad<replaceable>N</replaceable>.init</filename>)
+	and
 	locking devices
 	(<filename>/dev/ttyd<replaceable>N</replaceable>.lock</filename> and
-	<filename>/dev/cuad<replaceable>N</replaceable>.lock</filename> on
-	&os;&nbsp;6.X,
-	<filename>/dev/ttyld<replaceable>N</replaceable></filename> and
-	<filename>/dev/cuala<replaceable>N</replaceable></filename> on
-	&os;&nbsp;5.X).  The
+	<filename>/dev/cuad<replaceable>N</replaceable>.lock</filename>).
+	The
 	initialization devices are used to initialize communications port
 	parameters each time a port is opened, such as
 	<literal>crtscts</literal> for modems which use
@@ -768,10 +761,7 @@
 	<para>Where <quote>serial-port-device</quote> is the name of a
 	  special device file denoting a serial port of your system.
 	  These device files are called
-	  <devicename>/dev/cuaa<replaceable>N</replaceable></devicename>
-	  for &os; versions older than 6.0, and
-	  <devicename>/dev/cuad<replaceable>N</replaceable></devicename>
-	  for 6.0 and later versions.</para>
+	  <devicename>/dev/cuad<replaceable>N</replaceable></devicename>.</para>
 
 	<para>The <quote>N</quote>-part of a device name is the serial
 	  port number.</para>
@@ -779,9 +769,9 @@
 	<note>
 	  <para>Note that device numbers in &os; start from zero and not
 	    one (like they do, for instance in &ms-dos;-derived systems).
-	    This means that what &ms-dos;-based systems
-	    call <quote>COM1</quote> is
-	    usually <filename>/dev/cuad0</filename> in &os;.</para>
+	    This means that what &ms-dos;-based systems call
+	    <devicename>COM1</devicename> is usually
+	    <filename>/dev/cuad0</filename> in &os;.</para>
 	</note>
 
 	<note>
@@ -873,19 +863,19 @@
 
 	<para>The <filename>/etc/ttys</filename> file lists all of the ports
 	  on your FreeBSD system where you want to allow logins.  For example,
-	  the first virtual console <filename>ttyv0</filename> has an entry in
-	  this file.  You can log in on the console using this entry.  This
-	  file also contains entries for the other virtual consoles, serial ports,
-	  and pseudo-ttys.  For a hardwired terminal, just list the serial
-	  port's <filename>/dev</filename> entry without the
+	  the first virtual console <devicename>ttyv0</devicename> has an entry
+	  in this file.  You can log in on the console using this entry.  This
+	  file also contains entries for the other virtual consoles, serial
+	  ports, and pseudo-ttys.  For a hardwired terminal, just list the
+	  serial port's <filename>/dev</filename> entry without the
 	  <filename>/dev</filename> part (for example,
 	  <filename>/dev/ttyv0</filename> would be listed as
 	  <devicename>ttyv0</devicename>).</para>
 
 	<para>A default FreeBSD install includes an
 	  <filename>/etc/ttys</filename> file with support for the first
-	  four serial ports: <filename>ttyd0</filename> through
-	  <filename>ttyd3</filename>.  If you are attaching a terminal
+	  four serial ports: <devicename>ttyd0</devicename> through
+	  <devicename>ttyd3</devicename>.  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">
@@ -916,8 +906,8 @@
 	      the terminal special file as it is found in
 	      <filename>/dev</filename>.</para>
 	    </callout>
+
 	    <callout arearefs="co-ttys-line1col2">
-
 	      <para>The second field is the command to execute for
 		this line, which is usually &man.getty.8;.
 		<command>getty</command> initializes and opens the
@@ -949,13 +939,11 @@
 		match.</para>
 
 	      <para>For our example, the Wyse-50 uses no parity and
-		connects at 38400&nbsp;bps.  The 286&nbsp;PC uses no parity and
-		connects at 19200&nbsp;bps.</para>
-
+		connects at 38400&nbsp;bps.  The 286&nbsp;PC uses no parity
+		and connects at 19200&nbsp;bps.</para>
 	    </callout>
 
 	    <callout arearefs="co-ttys-line1col3">
-
 	      <para>The third field is the type of terminal usually
 		connected to that tty line.  For dial-up ports,
 		<literal>unknown</literal> or
@@ -970,7 +958,6 @@
 		terminal type while the 286 PC running
 		<application>Procomm</application> will be set to
 		emulate at VT-100. </para>
-
 	    </callout>
 
 	    <callout arearefs="co-ttys-line1col4">
@@ -1063,7 +1050,7 @@
 	<para>You should see an entry for the terminal.  For
 	  example, the following display shows that a
 	  <command>getty</command> is running on the second serial
-	  port <literal>ttyd1</literal> and is using the
+	  port <devicename>ttyd1</devicename> and is using the
 	  <literal>std.38400</literal> entry in
 	  <filename>/etc/gettytab</filename>:</para>
 
@@ -1106,7 +1093,8 @@
       </sect3>
 
       <sect3>
-	<title>Characters Appear Doubled; the Password Appears When Typed</title>
+	<title>Characters Appear Doubled; the Password Appears When
+	  Typed</title>
 
 	<para>Switch the terminal (or the terminal emulation software)
 	  from <quote>half duplex</quote> or <quote>local echo</quote> to
@@ -1223,8 +1211,8 @@
 
 	<para>FreeBSD needs the <acronym>RTS</acronym> and
 	  <acronym>CTS</acronym> signals for flow control at speeds above
-	  2400&nbsp;bps, the <acronym>CD</acronym> signal to detect when a call has
-	  been answered or the line has been hung up, and the
+	  2400&nbsp;bps, the <acronym>CD</acronym> signal to detect when a
+	  call has been answered or the line has been hung up, and the
 	  <acronym>DTR</acronym> signal to reset the modem after a session is
 	  complete.  Some cables are wired without all of the needed signals,
 	  so if you have problems, such as a login session not going away when
@@ -1306,27 +1294,27 @@
 	Lastly, you can place port initialization commands in the
 	<filename>/etc/rc.d/serial</filename> script.</para>
 
-      <para>There are two schools of thought regarding dial-up modems on &unix;.
-	One group likes to configure their modems and systems so that no matter
-	at what speed a remote user dials in, the local computer-to-modem
-	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.</para>
+      <para>There are two schools of thought regarding dial-up modems on
+	&unix;.  One group likes to configure their modems and systems so that
+	no matter at what speed a remote user dials in, the local
+	computer-to-modem 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
+	<application>Emacs</application> will not adjust their screen-painting
+	methods to make their response better for slower connections.</para>
 
       <para>The other school configures their modems' RS-232 interface to vary
 	its speed based on the remote user's connection speed.  For example,
-	V.32bis (14.4&nbsp;Kbps) connections to the modem might make the modem run
-	its RS-232 interface at 19.2&nbsp;Kbps, while 2400&nbsp;bps connections make the
-	modem's RS-232 interface run at 2400&nbsp;bps. Because
-	<command>getty</command> does not understand any particular modem's
-	connection speed reporting, <command>getty</command> gives a
+	V.32bis (14.4&nbsp;Kbps) connections to the modem might make the modem
+	run its RS-232 interface at 19.2&nbsp;Kbps, while 2400&nbsp;bps
+	connections make the modem's RS-232 interface run at 2400&nbsp;bps.
+	Because <command>getty</command> does not understand any particular
+	modem's connection speed reporting, <command>getty</command> gives a
 	<prompt>login:</prompt> message at an initial speed and watches the
 	characters that come back in response.  If the user sees junk, it is
 	assumed that they know they should press the
-	<keycode>Enter</keycode> key until they see a recognizable
+	<keycap>Enter</keycap> key until they see a recognizable
 	prompt.  If the data rates do not match, <command>getty</command> sees
 	anything the user types as <quote>junk</quote>, tries going to the next
 	speed and gives the <prompt>login:</prompt> prompt again.  This
@@ -1400,19 +1388,21 @@
 




More information about the Freebsd-doc-el mailing list