aboutsummaryrefslogtreecommitdiffstats
path: root/chapter07/setclock.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter07/setclock.xml')
-rw-r--r--chapter07/setclock.xml39
1 files changed, 18 insertions, 21 deletions
diff --git a/chapter07/setclock.xml b/chapter07/setclock.xml
index a5a43f6a0..08c751cb4 100644
--- a/chapter07/setclock.xml
+++ b/chapter07/setclock.xml
@@ -11,28 +11,25 @@
<primary sortas="d-setclock">setclock</primary>
<secondary>configuring</secondary></indexterm>
-<para>The <command>setclock</command> script reads the time from the hardware clock,
-also known as the BIOS or the Complementary Metal Oxide Semiconductor
-(CMOS) clock. If the hardware clock is set to UTC, this script will convert the hardware clock's time to
-the local time using the <filename>/etc/localtime</filename> file
-(which tells the <command>hwclock</command> program which timezone the
-user is in). There is no way to
-detect whether or not the hardware clock is set to UTC time, so this
-needs to be manually configured.</para>
-
-<para>If you cannot remember whether or not the hardware
-clock is set to UTC time, find out by running
-the <userinput>hwclock --localtime --show</userinput> command. This will tell
-what the current time is according to the hardware 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 amount of hours for the timezone to this
-<command>hwclock</command> time. For example, if you live in the MST
+<para>The <command>setclock</command> script reads the time from the hardware
+clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
+(CMOS) clock. If the hardware clock is set to UTC, this script will convert the
+hardware clock's time to the local time using the
+<filename>/etc/localtime</filename> file (which tells the
+<command>hwclock</command> program which timezone the user is in). There is no
+way to detect whether or not the hardware clock is set to UTC time, so this
+needs to be configured manually.</para>
+
+<para>If you cannot remember whether or not the hardware clock is set to UTC
+time, find out by running the <userinput>hwclock --localtime --show</userinput>
+command. This will display what the current time is according to the hardware
+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 amount of hours for the timezone to the time shown by
+<command>hwclock</command>. For example, if you are currently in the MST
timezone, which is also known as GMT -0700, add seven hours to the local
-time. Then, account for Daylight Savings Time, which requires
-subtracting an hour (or only add six in the first place) during the summer
-months.</para>
+time.</para>
<para>Change the value of the <envar>UTC</envar> variable below
to a value of <parameter>0</parameter> (zero) if the hardware clock