Date: Thu, 4 May 2023 00:28:23 GMT From: Graham Perrin <grahamperrin@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: e63798df73 - main - =?utf-8?Q?FreeBSD=20Handbook:=20Config=E2=80=A6=20and=20Tuning:=20corrections?= Message-ID: <202305040028.3440SNbo048021@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by grahamperrin: URL: https://cgit.FreeBSD.org/doc/commit/?id=e63798df73d7d956d8c3ce3f81225421fdd1db23 commit e63798df73d7d956d8c3ce3f81225421fdd1db23 Author: Graham Perrin <grahamperrin@FreeBSD.org> AuthorDate: 2023-05-04 00:19:20 +0000 Commit: Graham Perrin <grahamperrin@FreeBSD.org> CommitDate: 2023-05-04 00:19:20 +0000 FreeBSD Handbook: Config… and Tuning: corrections Minor corrections. Names of some mailing lists lacked the 'the' prefix. If referring to an outdated/legacy list archive, without mentioning that it is not current: also, refer to the current archive. One sentence per line should apply to most areas where a question mark is followed by a space. --- .../content/en/books/handbook/config/_index.adoc | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/documentation/content/en/books/handbook/config/_index.adoc b/documentation/content/en/books/handbook/config/_index.adoc index de68f3fdc3..f157c3c897 100644 --- a/documentation/content/en/books/handbook/config/_index.adoc +++ b/documentation/content/en/books/handbook/config/_index.adoc @@ -672,7 +672,11 @@ For more information, refer to man:hosts[5] and to [.filename]#/usr/share/exampl ==== Troubleshooting When troubleshooting hardware and software configurations, check the simple things first. -Is the network cable plugged in? Are the network services properly configured? Is the firewall configured correctly? Is the NIC supported by FreeBSD? Before sending a bug report, always check the Hardware Notes, update the version of FreeBSD to the latest STABLE version, check the mailing list archives, and search the Internet. +Is the network cable plugged in? +Are the network services properly configured? +Is the firewall configured correctly? +Is the NIC supported by FreeBSD? +Before sending a bug report, always check the Hardware Notes, update the version of FreeBSD to the latest STABLE version, check the mailing list archives, and search the Internet. If the card works, yet performance is poor, read through man:tuning[7]. Also, check the network configuration as incorrect network settings can cause slow connections. @@ -1907,7 +1911,7 @@ acpi_dsdt_name="/boot/DSDT.aml" .... Be sure to copy [.filename]#DSDT.aml# to [.filename]#/boot#, then reboot the system. -If this fixes the problem, send a man:diff[1] of the old and new ASL to {freebsd-acpi} so that developers can work around the buggy behavior in [.filename]#acpica#. +If this fixes the problem, send a man:diff[1] of the old and new ASL to the {freebsd-acpi} so that developers can work around the buggy behavior in [.filename]#acpica#. [[ACPI-submitdebug]] === Getting and Submitting Debugging Info @@ -1941,7 +1945,7 @@ If the required information is triggered by a specific event, such as a suspend Instead, use `sysctl` to specify the layer and level after booting and preparing the system for the specific event. The variables which can be set using `sysctl` are named the same as the tunables in [.filename]#/boot/loader.conf#. -Once the debugging information is gathered, it can be sent to {freebsd-acpi} so that it can be used by the FreeBSD ACPI maintainers to identify the root cause of the problem and to develop a solution. +Once the debugging information is gathered, it can be sent to the {freebsd-acpi} so that it can be used by the FreeBSD ACPI maintainers to identify the root cause of the problem and to develop a solution. [NOTE] ==== @@ -1964,18 +1968,18 @@ When submitting a problem report, include the following information: Substitute the login name for _name_ and manufacturer/model for _system_. For example, use [.filename]#njl-FooCo6000.asl#. -Most FreeBSD developers watch the {freebsd-current}, but one should submit problems to {freebsd-acpi} to be sure it is seen. +Most FreeBSD developers watch the {freebsd-current}, but one should submit problems to the {freebsd-acpi} to be sure it is seen. Be patient when waiting for a response. If the bug is not immediately apparent, submit a bug report. When entering a PR, include the same information as requested above. This helps developers to track the problem and resolve it. -Do not send a PR without emailing {freebsd-acpi} first as it is likely that the problem has been reported before. +Do not send a PR without emailing the {freebsd-acpi} first as it is likely that the problem has been reported before. [[ACPI-References]] === References More information about ACPI may be found in the following locations: -* The FreeBSD ACPI Mailing List Archives (https://lists.freebsd.org/pipermail/freebsd-acpi/[https://lists.freebsd.org/pipermail/freebsd-acpi/]) +* Archives at https://lists.freebsd.org/pipermail/freebsd-acpi/[] and more recent https://lists.freebsd.org/archives/freebsd-acpi/[] * The ACPI 2.0 Specification (http://acpi.info/spec.htm[http://acpi.info/spec.htm]) * man:acpi[4], man:acpi_thermal[4], man:acpidump[8], man:iasl[8], and man:acpidb[8]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202305040028.3440SNbo048021>