mirror of https://github.com/tLDP/LDP
DocBook validation correction
Wrapping a <caution/> in a <para/>, wrapping a bunch of <procedure/> elements in <blockquote/> and correcting a bad xreflinkend attribute to xreflabel, all to allow for validation.
This commit is contained in:
Martin A. Brown
parent
fea669531f
commit
8be30ab554
|
|
@ -453,7 +453,7 @@ directory for the newly patched kernel. You should create a backup of all import
|
|||
<listitem><para><filename>/usr/src/System.map</filename></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>It is possible the location of these files differs on your system. Use <application>locate</application> as follows if the files are not in the locations specified above: <cmdsynopsis><command>locate</command> <replaceable><file></replaceable></cmdsynopsis></para>
|
||||
<para>It is possible the location of these files differs on your system. Use <application>locate</application> as follows if the files are not in the locations specified above: <cmdsynopsis><command>locate <replaceable><file></replaceable></command></cmdsynopsis></para>
|
||||
|
||||
</example>
|
||||
|
||||
|
|
@ -476,8 +476,10 @@ directory for the newly patched kernel. You should create a backup of all import
|
|||
<listitem><para>debian packages: binutils, e2fsprogs, gcc, make, module-init-tools, procps, util-linux (see also the list from 2.4)</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
<caution><title>Learn more about the 2.6 kernel before you upgrade</title>
|
||||
<para>This HOWTO does not include information on how to migrate from a 2.4 series kernel to a 2.6 series kernel. Please read the resources listed in <xref linkend="ref-upgrade-26" /> before attempting a kernel upgrade.</para></caution>
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<title>2.4.x series kernels</title>
|
||||
|
|
@ -509,11 +511,13 @@ site to find the kernel you would like.</para></tip>
|
|||
|
||||
<example id="ex-downloadkernel" xreflabel="Download the kernel and patch">
|
||||
<title>Download the kernel and patch</title>
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><cmdsynopsis><command>wget</command> <filename>http://kernel.org/pub/linux/kernel/v2.4/linux-&kernel-version;.tar.bz2</filename></cmdsynopsis></step>
|
||||
<step><cmdsynopsis><command>wget <filename>http://kernel.org/pub/linux/kernel/v2.4/linux-&kernel-version;.tar.bz2</filename></command></cmdsynopsis></step>
|
||||
<step><para>Download the latest patch for your kernel. This may or may not be the newest patch available. Please look carefully. For example: if you are using the 2.4.20 kernel you would get <filename>acpi-20021212-2.4.20.diff.gz</filename>. The patches can be downloaded from: <ulink url="http://prdownloads.sourceforge.net/acpi"/>.</para></step>
|
||||
<step><para>Note the revision date. In this example above the date is 20021212 (December 12, 2002), but it will almost certainly be different for your kernel. You will need to know this number when you check to make sure the patch worked.</para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
</example>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -525,6 +529,7 @@ to your current kernel. This link must point to the new kernel, you will update
|
|||
|
||||
<example id="ex-unpack" xreflabel="Unpacking your kernel source files">
|
||||
<title>Unpacking your kernel source files</title>
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para>
|
||||
<command>
|
||||
|
|
@ -549,6 +554,7 @@ to your current kernel. This link must point to the new kernel, you will update
|
|||
</command>
|
||||
</para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
</example>
|
||||
|
||||
<para>If your kernel needs to be patched, do so now.
|
||||
|
|
@ -577,6 +583,7 @@ different ACPI related options that you will need to select.</para>
|
|||
|
||||
<para>Please also read the list of <xref linkend="known-issues" />.</para>
|
||||
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para>
|
||||
<command>cd
|
||||
|
|
@ -610,6 +617,7 @@ different ACPI related options that you will need to select.</para>
|
|||
</procedure>
|
||||
</step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
|
||||
</example>
|
||||
|
||||
|
|
@ -629,11 +637,13 @@ kernel. I still need this option even in the 2.6.6 kernel due to my nVidia graph
|
|||
|
||||
<para>Each of these steps should be performed as the root user.</para>
|
||||
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para><command>cd <filename class="directory">/usr/src/linux</filename></command></para></step>
|
||||
<step><para><command>make-kpkg <parameter>clean</parameter></command></para></step>
|
||||
<step><para><command>make-kpkg <option>--append-to-version=.&kernel-name;</option> <parameter>kernel_image</parameter> <parameter>modules_image</parameter></command></para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
|
||||
<para>I no longer use <replaceable>.date</replaceable> to distinguish
|
||||
kernel builds. It was too frustrating to have 030627a, 032627b (etc) as I tried to figure things out. I now use names, in alphabetical order, starting with the kernel build <quote>alien</quote>. My current kernel build is <quote>Ulairi.</quote> (The machine itself is <quote>Smeagol</quote>--a name it has earned.)</para>
|
||||
|
|
@ -646,6 +656,7 @@ kernel builds. It was too frustrating to have 030627a, 032627b (etc) as I tried
|
|||
|
||||
<para>Each of these steps should be performed as the root user.</para>
|
||||
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para><command>cd <filename class="directory">/usr/src</filename></command></para></step>
|
||||
<step><para><command>dpkg <option>-i</option> kernel-image-&kernel-version;.&kernel-name;_10.00.Custom_i386.deb</command></para></step>
|
||||
|
|
@ -680,6 +691,7 @@ read-only
|
|||
<filename class="extension">.deb</filename> files.
|
||||
</para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
|
||||
</example>
|
||||
|
||||
|
|
@ -697,28 +709,36 @@ system), you will need to check that you are running the new kernel with the cor
|
|||
<para>First you need to make sure you are running the correct kernel. This can be done with the command line tool <application>uname</application>. The
|
||||
revision is the date the patch was released and will be different for each kernel release.</para>
|
||||
|
||||
<para>
|
||||
<userinput>
|
||||
&prompt; <command>uname <option>-a</option></command>
|
||||
</userinput>
|
||||
</para>
|
||||
|
||||
<para>Assuming you are indeed running the new kernel, you can now check the ACPI's revision date with the following command.</para>
|
||||
|
||||
<para>
|
||||
<userinput>&prompt; <command>cat <filename>/proc/acpi/info</filename></command>
|
||||
</userinput>
|
||||
</para>
|
||||
|
||||
<para>This may give you only a version number, or a more detailed list. You are looking for the line that starts with <parameter>version:</parameter>.</para>
|
||||
|
||||
<para>If for some reason that gives you no information, you can also check the message printed when ACPI was first loaded as the system was booting. This information can be printed to a terminal window with the application <application>dmesg</application>.</para>
|
||||
|
||||
<para>
|
||||
<userinput>&prompt; <command>dmesg</command> | <command>grep <parameter>ACPI.*Subsystem\ revision</parameter></command>
|
||||
</userinput>
|
||||
</para>
|
||||
|
||||
<para>It should give the output:
|
||||
<computeroutput>ACPI: Subsystem revision 20040326</computeroutput>. The revision number is the date the patch was originally released by the development team. If you patched your kernel according to <xref linkend="howto-patch"/> this number will match the patch that you installed in <xref linkend="ex-patch" />.</para>
|
||||
|
||||
<para>To read all the ACPI-related information, you can expand the pattern that <application>grep</application> matches and selectively print all ACPI messages:</para>
|
||||
|
||||
<para>
|
||||
<userinput>&prompt; <command>dmesg</command> | <command>grep <parameter>ACPI</parameter></command> </userinput>
|
||||
</para>
|
||||
</example>
|
||||
|
||||
</sect2>
|
||||
|
|
@ -908,6 +928,7 @@ look for the absence of errors.)</para>
|
|||
<example id="ex-patch" xreflabel="Patching your kernel">
|
||||
<title>Patching your kernel</title>
|
||||
<para>These steps should be performed as the root user.</para>
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para>
|
||||
<command>cd
|
||||
|
|
@ -936,6 +957,7 @@ look for the absence of errors.)</para>
|
|||
(this is the actual patching part)
|
||||
</para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
</example>
|
||||
|
||||
<para>Once you have finished patching your kernel, continue reading at <xref
|
||||
|
|
@ -956,8 +978,9 @@ generic way. In fact it is probably only 10 or so lines of difference.</para>
|
|||
<para>The <quote>normal</quote> way of compiling a kernel does not use
|
||||
<command>make-kpkg</command>. Instead, it uses the following steps:</para>
|
||||
|
||||
<example id="ex-compilenodeb" xreflinkend="Compile the kernel">
|
||||
<example id="ex-compilenodeb" xreflabel="Compile the kernel">
|
||||
<title>Compile the kernel</title>
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para>
|
||||
<command>cd
|
||||
|
|
@ -982,6 +1005,7 @@ generic way. In fact it is probably only 10 or so lines of difference.</para>
|
|||
(remember to unpack your modules first)
|
||||
</para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
</example>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -994,6 +1018,7 @@ lilo. If you are not doing things <citetitle>The Debian Way</citetitle> your <qu
|
|||
<example id="ex-nodebinstall" xreflabel="Install the new kernel">
|
||||
<title>Install the new kernel</title>
|
||||
|
||||
<blockquote>
|
||||
<procedure>
|
||||
<step><para>
|
||||
<command>cd
|
||||
|
|
@ -1025,6 +1050,7 @@ lilo. If you are not doing things <citetitle>The Debian Way</citetitle> your <qu
|
|||
the new kernel.
|
||||
</para></step>
|
||||
</procedure>
|
||||
</blockquote>
|
||||
</example>
|
||||
|
||||
<warning>
|
||||
|
|
|
|||
Loading…
Reference in New Issue