os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

<abbrev> -> <acronym> in some cases.

Browse source
This commit is contained in:
Nik Clayton 1998-10-26 23:52:05 +00:00
parent 84712fedb0
commit a02c3d7f5e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=3681
4 changed files with 83 additions and 81 deletions
en/handbook
READMEhandbook.sgml
en_US.ISO8859-1/books/handbook
book.sgml
en_US.ISO_8859-1/books/handbook
book.sgml

2
en/handbook/README
View file

@ -545,3 +545,5 @@ for example,
Search for: \s-+</email>
Replace with: </email>
50. <abbrev> -> <acronym> in some cases.

54
en/handbook/handbook.sgml
View file

@ -17826,9 +17826,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<filename>/usr/obj</filename> and other directory trees that
can be exactly recreated by your computer. An example is the
files that comprise these handbook pages-they have been
generated from <abbrev>SGML</abbrev> input files. Creating
backups of these <abbrev>HTML</abbrev> files is not
necessary. The <abbrev>SGML</abbrev> source files are
generated from <acronym>SGML</acronym> input files. Creating
backups of these <acronym>HTML</acronym> files is not
necessary. The <acronym>SGML</acronym> source files are
backed up regularly.</para>
</sect4>
@ -19451,45 +19451,45 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
<itemizedlist>
<listitem>
<para>Transmitted Data (<abbrev>SD</abbrev>)</para>
<para>Transmitted Data (<acronym>SD</acronym>)</para>
</listitem>
<listitem>
<para>Received Data (<abbrev>RD</abbrev>)</para>
<para>Received Data (<acronym>RD</acronym>)</para>
</listitem>
<listitem>
<para>Request to Send (<abbrev>RTS</abbrev>)</para>
<para>Request to Send (<acronym>RTS</acronym>)</para>
</listitem>
<listitem>
<para>Clear to Send (<abbrev>CTS</abbrev>)</para>
<para>Clear to Send (<acronym>CTS</acronym>)</para>
</listitem>
<listitem>
<para>Data Set Ready (<abbrev>DSR</abbrev>)</para>
<para>Data Set Ready (<acronym>DSR</acronym>)</para>
</listitem>
<listitem>
<para>Data Terminal Ready (<abbrev>DTR</abbrev>)</para>
<para>Data Terminal Ready (<acronym>DTR</acronym>)</para>
</listitem>
<listitem>
<para>Carrier Detect (<abbrev>CD</abbrev>)</para>
<para>Carrier Detect (<acronym>CD</acronym>)</para>
</listitem>
<listitem>
<para>Signal Ground (<abbrev>SG</abbrev>)</para>
<para>Signal Ground (<acronym>SG</acronym>)</para>
</listitem>
</itemizedlist>
<para>FreeBSD needs the <abbrev>RTS</abbrev> and
<abbrev>CTS</abbrev> signals for flow-control at speeds above
2400bps, the <abbrev>CD</abbrev> signal to detect when a call
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call
has been answered or the line has been hung up, and the
<abbrev>DTR</abbrev> signal to reset the modem after a session
<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 the line hangs up, you may have a problem with
@ -19548,7 +19548,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
</informalexample>
<para>When a user dials the modem's line and the modems connect, the
<abbrev>CD</abbrev> line is asserted by the modem. The kernel
<acronym>CD</acronym> line is asserted by the modem. The kernel
notices that carrier has been detected and completes
<command>getty</command>'s open of the
port. <command>getty</command> sends a <prompt>login:</prompt> prompt at the specified initial line
@ -20051,24 +20051,24 @@ stty -f /dev/ttyd3 crtscts
<itemizedlist>
<listitem>
<para><abbrev>CD</abbrev> asserted when connected</para>
<para><acronym>CD</acronym> asserted when connected</para>
</listitem>
<listitem>
<para><abbrev>DTR</abbrev> asserted for operation; dropping
<para><acronym>DTR</acronym> asserted for operation; dropping
DTR hangs up line &amp; resets modem</para>
</listitem>
<listitem>
<para><abbrev>CTS</abbrev> transmitted data flow control</para>
<para><acronym>CTS</acronym> transmitted data flow control</para>
</listitem>
<listitem>
<para>Disable <filename>XON/XOFF</filename> flow control</para>
<para>Disable <acronym>XON/XOFF</acronym> flow control</para>
</listitem>
<listitem>
<para><abbrev>RTS</abbrev> received data flow control</para>
<para><acronym>RTS</acronym> received data flow control</para>
</listitem>
<listitem>
@ -20215,14 +20215,14 @@ AT&amp;B2&amp;W
<para>Hook up your modem to your FreeBSD system, boot the system,
and, if your modem has status indication lights, watch to see
whether the modem's <abbrev>DTR</abbrev> indicator lights when
whether the modem's <acronym>DTR</acronym> indicator lights when
the <prompt>login:</prompt> prompt appears on the
system's console &mdash; if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
<para>If the <abbrev>DTR</abbrev> indicator doesn't light, login
<para>If the <acronym>DTR</acronym> indicator doesn't light, login
to the FreeBSD system through the console and issue a <command>ps ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port.
You should see a lines like this among the processes
@ -20243,7 +20243,7 @@ AT&amp;B2&amp;W
<command>getty</command> has completed its open on
the communications port. This could indicate a problem with the
cabling or a mis-configured modem, because <command>getty</command> should not be able to open the
communications port until <abbrev>CD</abbrev> (carrier detect)
communications port until <acronym>CD</acronym> (carrier detect)
has been asserted by the modem.</para>
<para>If you do not see any <command>getty</command>
@ -20304,9 +20304,9 @@ AT&amp;B2&amp;W
<para>If you dial but the modem on the FreeBSD system will not
answer, make sure that the modem is configured to answer the
phone when <abbrev>DTR</abbrev> is asserted. If the modem
phone when <acronym>DTR</acronym> is asserted. If the modem
seems to be configured correctly, verify that the
<abbrev>DTR</abbrev> line is asserted by checking the modem's
<acronym>DTR</acronym> line is asserted by checking the modem's
indicator lights (if it has any).</para>
<para>If you have gone over everything several times and it still
@ -28154,7 +28154,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# Date created: 5 December 1994
# Whom: asami
#
# $Id: handbook.sgml,v 1.49 1998-10-26 23:51:32 nik Exp $
# $Id: handbook.sgml,v 1.50 1998-10-26 23:52:03 nik Exp $
#
DISTNAME= oneko-1.1b

54
en_US.ISO8859-1/books/handbook/book.sgml
View file

@ -17826,9 +17826,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<filename>/usr/obj</filename> and other directory trees that
can be exactly recreated by your computer. An example is the
files that comprise these handbook pages-they have been
generated from <abbrev>SGML</abbrev> input files. Creating
backups of these <abbrev>HTML</abbrev> files is not
necessary. The <abbrev>SGML</abbrev> source files are
generated from <acronym>SGML</acronym> input files. Creating
backups of these <acronym>HTML</acronym> files is not
necessary. The <acronym>SGML</acronym> source files are
backed up regularly.</para>
</sect4>
@ -19451,45 +19451,45 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
<itemizedlist>
<listitem>
<para>Transmitted Data (<abbrev>SD</abbrev>)</para>
<para>Transmitted Data (<acronym>SD</acronym>)</para>
</listitem>
<listitem>
<para>Received Data (<abbrev>RD</abbrev>)</para>
<para>Received Data (<acronym>RD</acronym>)</para>
</listitem>
<listitem>
<para>Request to Send (<abbrev>RTS</abbrev>)</para>
<para>Request to Send (<acronym>RTS</acronym>)</para>
</listitem>
<listitem>
<para>Clear to Send (<abbrev>CTS</abbrev>)</para>
<para>Clear to Send (<acronym>CTS</acronym>)</para>
</listitem>
<listitem>
<para>Data Set Ready (<abbrev>DSR</abbrev>)</para>
<para>Data Set Ready (<acronym>DSR</acronym>)</para>
</listitem>
<listitem>
<para>Data Terminal Ready (<abbrev>DTR</abbrev>)</para>
<para>Data Terminal Ready (<acronym>DTR</acronym>)</para>
</listitem>
<listitem>
<para>Carrier Detect (<abbrev>CD</abbrev>)</para>
<para>Carrier Detect (<acronym>CD</acronym>)</para>
</listitem>
<listitem>
<para>Signal Ground (<abbrev>SG</abbrev>)</para>
<para>Signal Ground (<acronym>SG</acronym>)</para>
</listitem>
</itemizedlist>
<para>FreeBSD needs the <abbrev>RTS</abbrev> and
<abbrev>CTS</abbrev> signals for flow-control at speeds above
2400bps, the <abbrev>CD</abbrev> signal to detect when a call
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call
has been answered or the line has been hung up, and the
<abbrev>DTR</abbrev> signal to reset the modem after a session
<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 the line hangs up, you may have a problem with
@ -19548,7 +19548,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
</informalexample>
<para>When a user dials the modem's line and the modems connect, the
<abbrev>CD</abbrev> line is asserted by the modem. The kernel
<acronym>CD</acronym> line is asserted by the modem. The kernel
notices that carrier has been detected and completes
<command>getty</command>'s open of the
port. <command>getty</command> sends a <prompt>login:</prompt> prompt at the specified initial line
@ -20051,24 +20051,24 @@ stty -f /dev/ttyd3 crtscts
<itemizedlist>
<listitem>
<para><abbrev>CD</abbrev> asserted when connected</para>
<para><acronym>CD</acronym> asserted when connected</para>
</listitem>
<listitem>
<para><abbrev>DTR</abbrev> asserted for operation; dropping
<para><acronym>DTR</acronym> asserted for operation; dropping
DTR hangs up line &amp; resets modem</para>
</listitem>
<listitem>
<para><abbrev>CTS</abbrev> transmitted data flow control</para>
<para><acronym>CTS</acronym> transmitted data flow control</para>
</listitem>
<listitem>
<para>Disable <filename>XON/XOFF</filename> flow control</para>
<para>Disable <acronym>XON/XOFF</acronym> flow control</para>
</listitem>
<listitem>
<para><abbrev>RTS</abbrev> received data flow control</para>
<para><acronym>RTS</acronym> received data flow control</para>
</listitem>
<listitem>
@ -20215,14 +20215,14 @@ AT&amp;B2&amp;W
<para>Hook up your modem to your FreeBSD system, boot the system,
and, if your modem has status indication lights, watch to see
whether the modem's <abbrev>DTR</abbrev> indicator lights when
whether the modem's <acronym>DTR</acronym> indicator lights when
the <prompt>login:</prompt> prompt appears on the
system's console &mdash; if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
<para>If the <abbrev>DTR</abbrev> indicator doesn't light, login
<para>If the <acronym>DTR</acronym> indicator doesn't light, login
to the FreeBSD system through the console and issue a <command>ps ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port.
You should see a lines like this among the processes
@ -20243,7 +20243,7 @@ AT&amp;B2&amp;W
<command>getty</command> has completed its open on
the communications port. This could indicate a problem with the
cabling or a mis-configured modem, because <command>getty</command> should not be able to open the
communications port until <abbrev>CD</abbrev> (carrier detect)
communications port until <acronym>CD</acronym> (carrier detect)
has been asserted by the modem.</para>
<para>If you do not see any <command>getty</command>
@ -20304,9 +20304,9 @@ AT&amp;B2&amp;W
<para>If you dial but the modem on the FreeBSD system will not
answer, make sure that the modem is configured to answer the
phone when <abbrev>DTR</abbrev> is asserted. If the modem
phone when <acronym>DTR</acronym> is asserted. If the modem
seems to be configured correctly, verify that the
<abbrev>DTR</abbrev> line is asserted by checking the modem's
<acronym>DTR</acronym> line is asserted by checking the modem's
indicator lights (if it has any).</para>
<para>If you have gone over everything several times and it still
@ -28154,7 +28154,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# Date created: 5 December 1994
# Whom: asami
#
# $Id: book.sgml,v 1.49 1998-10-26 23:51:32 nik Exp $
# $Id: book.sgml,v 1.50 1998-10-26 23:52:03 nik Exp $
#
DISTNAME= oneko-1.1b

54
en_US.ISO_8859-1/books/handbook/book.sgml
View file

@ -17826,9 +17826,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<filename>/usr/obj</filename> and other directory trees that
can be exactly recreated by your computer. An example is the
files that comprise these handbook pages-they have been
generated from <abbrev>SGML</abbrev> input files. Creating
backups of these <abbrev>HTML</abbrev> files is not
necessary. The <abbrev>SGML</abbrev> source files are
generated from <acronym>SGML</acronym> input files. Creating
backups of these <acronym>HTML</acronym> files is not
necessary. The <acronym>SGML</acronym> source files are
backed up regularly.</para>
</sect4>
@ -19451,45 +19451,45 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
<itemizedlist>
<listitem>
<para>Transmitted Data (<abbrev>SD</abbrev>)</para>
<para>Transmitted Data (<acronym>SD</acronym>)</para>
</listitem>
<listitem>
<para>Received Data (<abbrev>RD</abbrev>)</para>
<para>Received Data (<acronym>RD</acronym>)</para>
</listitem>
<listitem>
<para>Request to Send (<abbrev>RTS</abbrev>)</para>
<para>Request to Send (<acronym>RTS</acronym>)</para>
</listitem>
<listitem>
<para>Clear to Send (<abbrev>CTS</abbrev>)</para>
<para>Clear to Send (<acronym>CTS</acronym>)</para>
</listitem>
<listitem>
<para>Data Set Ready (<abbrev>DSR</abbrev>)</para>
<para>Data Set Ready (<acronym>DSR</acronym>)</para>
</listitem>
<listitem>
<para>Data Terminal Ready (<abbrev>DTR</abbrev>)</para>
<para>Data Terminal Ready (<acronym>DTR</acronym>)</para>
</listitem>
<listitem>
<para>Carrier Detect (<abbrev>CD</abbrev>)</para>
<para>Carrier Detect (<acronym>CD</acronym>)</para>
</listitem>
<listitem>
<para>Signal Ground (<abbrev>SG</abbrev>)</para>
<para>Signal Ground (<acronym>SG</acronym>)</para>
</listitem>
</itemizedlist>
<para>FreeBSD needs the <abbrev>RTS</abbrev> and
<abbrev>CTS</abbrev> signals for flow-control at speeds above
2400bps, the <abbrev>CD</abbrev> signal to detect when a call
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call
has been answered or the line has been hung up, and the
<abbrev>DTR</abbrev> signal to reset the modem after a session
<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 the line hangs up, you may have a problem with
@ -19548,7 +19548,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom
</informalexample>
<para>When a user dials the modem's line and the modems connect, the
<abbrev>CD</abbrev> line is asserted by the modem. The kernel
<acronym>CD</acronym> line is asserted by the modem. The kernel
notices that carrier has been detected and completes
<command>getty</command>'s open of the
port. <command>getty</command> sends a <prompt>login:</prompt> prompt at the specified initial line
@ -20051,24 +20051,24 @@ stty -f /dev/ttyd3 crtscts
<itemizedlist>
<listitem>
<para><abbrev>CD</abbrev> asserted when connected</para>
<para><acronym>CD</acronym> asserted when connected</para>
</listitem>
<listitem>
<para><abbrev>DTR</abbrev> asserted for operation; dropping
<para><acronym>DTR</acronym> asserted for operation; dropping
DTR hangs up line &amp; resets modem</para>
</listitem>
<listitem>
<para><abbrev>CTS</abbrev> transmitted data flow control</para>
<para><acronym>CTS</acronym> transmitted data flow control</para>
</listitem>
<listitem>
<para>Disable <filename>XON/XOFF</filename> flow control</para>
<para>Disable <acronym>XON/XOFF</acronym> flow control</para>
</listitem>
<listitem>
<para><abbrev>RTS</abbrev> received data flow control</para>
<para><acronym>RTS</acronym> received data flow control</para>
</listitem>
<listitem>
@ -20215,14 +20215,14 @@ AT&amp;B2&amp;W
<para>Hook up your modem to your FreeBSD system, boot the system,
and, if your modem has status indication lights, watch to see
whether the modem's <abbrev>DTR</abbrev> indicator lights when
whether the modem's <acronym>DTR</acronym> indicator lights when
the <prompt>login:</prompt> prompt appears on the
system's console &mdash; if it lights up, that should mean that
FreeBSD has started a <command>getty</command>
process on the appropriate communications port and is waiting
for the modem to accept a call.</para>
<para>If the <abbrev>DTR</abbrev> indicator doesn't light, login
<para>If the <acronym>DTR</acronym> indicator doesn't light, login
to the FreeBSD system through the console and issue a <command>ps ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port.
You should see a lines like this among the processes
@ -20243,7 +20243,7 @@ AT&amp;B2&amp;W
<command>getty</command> has completed its open on
the communications port. This could indicate a problem with the
cabling or a mis-configured modem, because <command>getty</command> should not be able to open the
communications port until <abbrev>CD</abbrev> (carrier detect)
communications port until <acronym>CD</acronym> (carrier detect)
has been asserted by the modem.</para>
<para>If you do not see any <command>getty</command>
@ -20304,9 +20304,9 @@ AT&amp;B2&amp;W
<para>If you dial but the modem on the FreeBSD system will not
answer, make sure that the modem is configured to answer the
phone when <abbrev>DTR</abbrev> is asserted. If the modem
phone when <acronym>DTR</acronym> is asserted. If the modem
seems to be configured correctly, verify that the
<abbrev>DTR</abbrev> line is asserted by checking the modem's
<acronym>DTR</acronym> line is asserted by checking the modem's
indicator lights (if it has any).</para>
<para>If you have gone over everything several times and it still
@ -28154,7 +28154,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# Date created: 5 December 1994
# Whom: asami
#
# $Id: book.sgml,v 1.49 1998-10-26 23:51:32 nik Exp $
# $Id: book.sgml,v 1.50 1998-10-26 23:52:03 nik Exp $
#
DISTNAME= oneko-1.1b