Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Aug 1996 23:14:16 +0900 (JST)
From:      max@sfc.wide.ad.jp
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   docs/1477: typos in /usr/src/share/doc/handbook/dialup.sgml
Message-ID:  <199608081414.XAA16250@mail.tky007.tth.expo96.ad.jp>
Resent-Message-ID: <199608081420.HAA10000@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         1477
>Category:       docs
>Synopsis:       typos in /usr/src/share/doc/handbook/dialup.sgml
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug  8 07:20:02 PDT 1996
>Last-Modified:
>Originator:     Masafumi NAKANE
>Organization:
>Release:        FreeBSD 2.2-CURRENT i386
>Environment:

	
These typos are found in :
     $Id: dialup.sgml,v 1.11 1996/06/07 15:56:37 alex Exp $

>Description:

	
Not really interesting problems or anything, just several typos in
/usr/src/share/doc/handbook/dialup.sgml.

>How-To-Repeat:

	

>Fix:
	
	
Here's a patch to 1.11 revision to fix them.

*** /usr/src/share/doc/handbook/dialup.sgml	Sun Jun 30 11:43:08 1996
--- dialup.sgml.new	Thu Aug  8 15:29:26 1996
***************
*** 68,74 ****
  in general, the author remembers reading that <em/The RS-232 Bible/
  (anybody have an ISBN?) is a good reference.
  
! When talking about communications data rates, the author does notuse
  the term <bf/baud/.  Baud refers to the number of electrical state
  transitions that may be made in a period of time, while <bf/bps/ (bits
  per second) is the ``correct'' term to use (at least it does not seem
--- 68,74 ----
  in general, the author remembers reading that <em/The RS-232 Bible/
  (anybody have an ISBN?) is a good reference.
  
! When talking about communications data rates, the author does not use
  the term <bf/baud/.  Baud refers to the number of electrical state
  transitions that may be made in a period of time, while <bf/bps/ (bits
  per second) is the ``correct'' term to use (at least it does not seem
***************
*** 310,316 ****
  and issue the command <tt/MAKEDEV ttyd0/.  Likewise, to make dialup
  device special files for <tt/COM2:/ (port 1), use <tt/MAKEDEV ttyd1/.
  
! <tt/MAKDEV/ not only creates the <tt>/dev/ttyd?</tt> device special
  files, but also creates the <tt>/dev/cua0?</tt> (and all of the
  initializing and locking special files under FreeBSD 1.1.5 and up) and
  removes the hardwired terminal special file <tt>/dev/tty0?</tt>, if it
--- 310,316 ----
  and issue the command <tt/MAKEDEV ttyd0/.  Likewise, to make dialup
  device special files for <tt/COM2:/ (port 1), use <tt/MAKEDEV ttyd1/.
  
! <tt/MAKEDEV/ not only creates the <tt>/dev/ttyd?</tt> device special
  files, but also creates the <tt>/dev/cua0?</tt> (and all of the
  initializing and locking special files under FreeBSD 1.1.5 and up) and
  removes the hardwired terminal special file <tt>/dev/tty0?</tt>, if it
***************
*** 336,342 ****
  <p>
  
  There are three system configuration files in the <tt>/etc</tt>
! directory that yo will probably need to edit to allow dialup access to
  your FreeBSD system.  The first, <tt>/etc/gettytab</tt>, contains
  configuration information for the <tt>/usr/libexec/getty</tt> daemon.
  Second, <tt>/etc/ttys</tt> holds information that tells
--- 336,342 ----
  <p>
  
  There are three system configuration files in the <tt>/etc</tt>
! directory that you will probably need to edit to allow dialup access to
  your FreeBSD system.  The first, <tt>/etc/gettytab</tt>, contains
  configuration information for the <tt>/usr/libexec/getty</tt> daemon.
  Second, <tt>/etc/ttys</tt> holds information that tells
***************
*** 417,423 ****
  
  If you have a higher speed modem, you will probably need to add an entry
  in <tt>/etc/gettytab</tt>; here is an entry you could use for a 14.4
! Kbps modem with a top interface speed of 19.2 Kpbs:
  
  <tscreen><verb>
  #
--- 417,423 ----
  
  If you have a higher speed modem, you will probably need to add an entry
  in <tt>/etc/gettytab</tt>; here is an entry you could use for a 14.4
! Kbps modem with a top interface speed of 19.2 Kbps:
  
  <tscreen><verb>
  #
***************
*** 451,462 ****
  If you have a 28.8 Kbps modem and/or you want to take advantage of
  compression on a 14.4 Kbps modem, you need to use a higher
  communications rate than 19.2 Kbps.  Here is an example of a
! <tt/gettytab/ entry starting a 57.6 Kpbs:
  
  <tscreen><verb>
  #
  # Additions for a V.32bis or V.34 Modem
! # Starting at 57.6 Kpbs
  #
  vm|VH300|Very High Speed Modem at 300,8-bit:\
          :nx=VH57600:tc=std.300:
--- 451,462 ----
  If you have a 28.8 Kbps modem and/or you want to take advantage of
  compression on a 14.4 Kbps modem, you need to use a higher
  communications rate than 19.2 Kbps.  Here is an example of a
! <tt/gettytab/ entry starting a 57.6 Kbps:
  
  <tscreen><verb>
  #
  # Additions for a V.32bis or V.34 Modem
! # Starting at 57.6 Kbps
  #
  vm|VH300|Very High Speed Modem at 300,8-bit:\
          :nx=VH57600:tc=std.300:
***************
*** 470,476 ****
          :nx=VH9600:tc=std.57600:
  </verb></tscreen>
  
! If you have a slow CPU or a heavily loaded system and you dobnot have
  16550A-based serial ports, you may receive sio ``silo'' errors at 57.6
  Kbps.
  
--- 470,476 ----
          :nx=VH9600:tc=std.57600:
  </verb></tscreen>
  
! If you have a slow CPU or a heavily loaded system and you do not have
  16550A-based serial ports, you may receive sio ``silo'' errors at 57.6
  Kbps.
  
***************
*** 793,799 ****
  If you have gone over everything several times and it still does not work,
  take a break and come back to it later.  If it still does not work,
  perhaps you can send an electronic mail message to the &a.questions
! describing your modem and youer problem, and the good folks on the list will
  try to help.
  
  <sect1><heading>Acknowledgments</heading>
--- 793,799 ----
  If you have gone over everything several times and it still does not work,
  take a break and come back to it later.  If it still does not work,
  perhaps you can send an electronic mail message to the &a.questions
! describing your modem and your problem, and the good folks on the list will
  try to help.
  
  <sect1><heading>Acknowledgments</heading>

>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608081414.XAA16250>