Bug 197244 - Possible Typo in Command in FreeBSD Handbook (26.6.3. Setting A Faster Serial Port Speed)
Summary: Possible Typo in Command in FreeBSD Handbook (26.6.3. Setting A Faster Serial...
Status: Closed FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Jason Helfman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-01 16:44 UTC by dal36
Modified: 2015-02-06 22:09 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dal36 2015-02-01 16:44:11 UTC
Section '26.6.3. Setting a Faster Serial Port Speed' of the version of the handbook on the website gives the following instruction for setting a faster serial port speed (in the second of the three bullet points in this section):

"Add the -S 19200 boot option to /boot.config, replacing 19200 with the speed to use."

This appears inconsistent with boot(8), which indicates that there should not be a space between '-S' and '19200'. I've found that following the instruction given in the handbook (i.e. setting this with the space, in /boot.config) causes the boot process to stop at the boot2 prompt (requiring manual intervention), whereas not including the space between the option and the speed parameter gives a complete boot.

Would it be appropriate to change this line to:

"Add the -S19200 boot option to /boot.config, replacing 19200 with the speed to use."
Comment 1 commit-hook freebsd_committer freebsd_triage 2015-02-06 22:08:23 UTC
A commit references this bug:

Author: jgh
Date: Fri Feb  6 22:07:59 UTC 2015
New revision: 46261
URL: https://svnweb.freebsd.org/changeset/doc/46261

Log:
  - address typo which causes a failed boot sequence

  PR:		197244
  Differential Revision:	https://reviews.freebsd.org/D1760
  Reported by:	dal36@gmx.co.uk
  Approved by:	bcr (mentor)

Changes:
  head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml
Comment 2 Jason Helfman freebsd_committer freebsd_triage 2015-02-06 22:09:11 UTC
Committed fix. Thanks for the report!