Attachment 222510 Details for Bug 253578 – patch to fix typos and improve wording in handbook

[patch] patch to fix typos and improve wording in handbook

0001-fix-typos-and-improve-wording.patch (text/plain), 5.10 KB, created by Andreas Bjørnestad on 2021-02-17 08:18:56 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Andreas Bjørnestad

Created: 2021-02-17 08:18:56 UTC

Size: 5.10 KB

patch

obsolete

>From 24dca01dbe09de2464aabf91aed0f1e7b49c584b Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Andreas=20Bj=C3=B8rnestad?= <panden@gmail.com>
>Date: Wed, 17 Feb 2021 09:17:46 +0100
>Subject: [PATCH] fix typos and improve wording
>
>---
> .../content/en/books/handbook/ppp-and-slip/_index.adoc        | 4 ++--
> .../content/en/books/handbook/serialcomms/_index.adoc         | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc b/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc
>index 36c33900d7..0d058a254b 100644
>--- a/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc
>+++ b/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc
>@@ -176,7 +176,7 @@ set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0
> Line 17:::
> Keep this line as-is as it adds a default route to the gateway. The `HISADDR` will automatically be replaced with the gateway address specified on line 16. It is important that this line appears after line 16.
> 
>-Depending upon whether man:ppp[8] is started manually or automatically, a [.filename]#/etc/ppp/ppp.linkup# may also need to be created which contains the following lines. This file is required when running `ppp` in `-auto` mode. This file is used after the connection has been established. At this point, the IP address will have been assigned and it is now be possible to add the routing table entries. When creating this file, make sure that _provider_ matches the value demonstrated in line 11 of [.filename]#ppp.conf#.
>+Depending upon whether man:ppp[8] is started manually or automatically, a [.filename]#/etc/ppp/ppp.linkup# may also need to be created which contains the following lines. This file is required when running `ppp` in `-auto` mode. This file is used after the connection has been established. At this point, the IP address will have been assigned and it is now possible to add the routing table entries. When creating this file, make sure that _provider_ matches the value demonstrated in line 11 of [.filename]#ppp.conf#.
> 
> [.programlisting]
> ....
>@@ -562,7 +562,7 @@ PPP ON example>add default HISADDR
> 
> Here we add our default route, we need to do this before we can talk to the outside world as currently the only established connection is with the peer. If this fails due to existing routes, put a bang character `!` in front of the `add`. Alternatively, set this before making the actual connection and it will negotiate a new route accordingly.
> 
>-If everything went good we should now have an active connection to the Internet, which could be thrown into the background using kbd:[CTRL+z] If `PPP` returns to `ppp` then the connection has bee lost. This is good to know because it shows the connection status. Capital P's represent a connection to the ISP and lowercase p's show that the connection has been lost.
>+If everything went good we should now have an active connection to the Internet, which could be thrown into the background using kbd:[CTRL+z]. If `PPP` returns to `ppp` the connection has been lost. This is good to know because it shows the connection status. Capital P's represent a connection to the ISP and lowercase p's show that the connection has been lost.
> 
> === Debugging
> 
>diff --git a/documentation/content/en/books/handbook/serialcomms/_index.adoc b/documentation/content/en/books/handbook/serialcomms/_index.adoc
>index 6e5ec52c47..3f38c654ad 100644
>--- a/documentation/content/en/books/handbook/serialcomms/_index.adoc
>+++ b/documentation/content/en/books/handbook/serialcomms/_index.adoc
>@@ -489,7 +489,7 @@ Use `ps` to make sure that a `getty` process is running and serving the terminal
> 
> If no `getty` process is running, make sure the port is enabled in [.filename]#/etc/ttys#. Remember to run `kill -HUP 1` after modifying [.filename]#/etc/ttys#.
> 
>-If the `getty` process is running but the terminal still does not display a login prompt, or if it displays a prompt but will not accept typed input, the terminal or cable may not support hardware handshaking. Try changing the entry in [.filename]#/etc/ttys# from `std.38400` to `3wire.38400`, then run `kill -HUP 1` after modifying [.filename]#/etc/ttys#. The `3wire` entry is similar to `std`, but ignores hardware handshaking. The baud rate may need to be reduced or software flow control enabled when using `3wire` to prevent buffer overflows.
>+If the `getty` process is running but the terminal still does not display a login prompt, or if it displays a prompt but will not accept typed input, the terminal or cable may not support hardware handshaking. Try changing the entry in [.filename]#/etc/ttys# from `std.38400` to `3wire.38400`, then run `kill -HUP 1` after modifying [.filename]#/etc/ttys#. The `3wire` entry is similar to `std`, but ignores hardware handshaking. The bps may need to be reduced or software flow control enabled when using `3wire` to prevent buffer overflows.
> 
> If garbage appears instead of a login prompt, make sure the terminal and FreeBSD agree on the bps rate and parity settings. Check the `getty` processes to make sure the correct _getty_ type is in use. If not, edit [.filename]#/etc/ttys# and run `kill -HUP 1`.
> 
>-- 
>2.20.1
>

Actions: View | Diff

Attachments on bug 253578: 222510