diff options
| author | David Bryant <david@davidcbryant.net> | 2022-12-31 10:23:56 -0600 |
|---|---|---|
| committer | David Bryant <david@davidcbryant.net> | 2022-12-31 10:23:56 -0600 |
| commit | dfb8516c83c2a3377829096892579c969e0a5906 (patch) | |
| tree | 856eaa04fd73af52ef964a4db25783705bdf38a4 | |
| parent | 06df566407a129388f9bfdc4ec4838e5ce3aa6c8 (diff) | |
Minor tweaks: a couple of commas, "your time zone".
| -rw-r--r-- | chapter09/usage.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/chapter09/usage.xml b/chapter09/usage.xml index ffbfc408a..2e9843988 100644 --- a/chapter09/usage.xml +++ b/chapter09/usage.xml @@ -249,7 +249,7 @@ EOF</userinput></screen> any words in this file other than comments are considered subsystem names to trigger at retry time. To find the subsystem of a device, use <command>udevadm info --attribute-walk <device></command> where - <device> is an absolute path in /dev or /sys such as /dev/sr0 or + <device> is an absolute path in /dev or /sys, such as /dev/sr0, or /sys/class/rtc.</para> <para>For information on kernel module loading and udev, see @@ -283,7 +283,7 @@ EOF</userinput></screen> clock. If this time matches whatever your watch says, then the hardware clock is set to local time. If the output from <command>hwclock</command> is not local time, chances are it is set to UTC time. Verify this by adding or subtracting - the proper number of hours for the time zone to the time shown by + the proper number of hours for your time zone to the time shown by <command>hwclock</command>. For example, if you are currently in the MST time zone, which is also known as GMT -0700, add seven hours to the local time.</para> |