Date: Fri, 22 Apr 2005 14:40:38 -0600 (MDT) From: Brad Davis <so14k@so14k.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/80263: Fix read-only sysctl wording Message-ID: <20050422204038.09FF7B86B@mccaffrey.house.so14k.com> Resent-Message-ID: <200504222050.j3MKoOLN072725@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 80263
>Category: docs
>Synopsis: Fix read-only sysctl wording
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Apr 22 20:50:24 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Brad Davis
>Release: FreeBSD 5.4-STABLE i386
>Organization:
>Environment:
System: FreeBSD mccaffrey.house.so14k.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Wed Apr 20 22:22:19 MDT 2005 root@mccaffrey.house.so14k.com:/usr/obj/usr/src/sys/SMP i386
>Description:
Fix read-only sysctl wording.
>How-To-Repeat:
>Fix:
--- doc-ori/en_US.ISO8859-1/books/handbook/config/chapter.sgml Fri Apr 22 11:51:50 2005
+++ doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml Fri Apr 22 14:37:59 2005
@@ -1651,7 +1651,8 @@
<title>&man.sysctl.8; Read-only</title>
<para>In some cases it may be desirable to modify read-only &man.sysctl.8;
- values. While this is not recommended, it is also sometimes unavoidable.</para>
+ values. While this is sometimes unavoidable, is can only be done
+ on (re)boot.</para>
<para>For instance on some laptop models the &man.cardbus.4; device will
not probe memory ranges, and fail with errors which look similar to:</para>
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050422204038.09FF7B86B>