LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

ad IDs to <footnote/> and <article/>

This commit is contained in:
Martin A. Brown 2016-03-29 09:55:37 -07:00
parent 8b9a9ccb7e
commit d366b5e397
8 changed files with 32 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
LDP/howto/docbook/Flash-Memory-HOWTO.xml
View File

@ -2,7 +2,7 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<article id="Flash-Memory-HOWTO">
<articleinfo>
@ -288,7 +288,7 @@
<para>
Users of this document might want to acquaint themselves with
the following:
<footnote>
<footnote id="ftn-heavy-dependencies">
<para>
This document leans heavily on the texts marked with an asterisk
</para>

4
LDP/howto/docbook/LDP-Reviewer-HOWTO.xml
View File

@ -1,6 +1,6 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://oasis-open.org/docbook/xml/4.2/docbookx.dtd"[]>
<article>
<article id="LDP-Reviewer-HOWTO">
<articleinfo>
<title>Linux Documentation Project Reviewer HOWTO</title>
@ -144,7 +144,7 @@
<para>When reviewing newly submitted documents, refer to the <xref linkend="techreview" /> and
<xref linkend="languagereview" /> portions of this guide for the types of information to verify and correct.
As a reviewer, you will need to check the documents out of the CVS
<footnote>
<footnote id="ftn-ok-to-return-changes-to-coordinator">
<para>Alternatively, if you've obtained the file from the Review Coordinator, or are unfamiliar with CVS, you can return the changes to the coordinator for further handling.</para>
</footnote>

20
LDP/howto/docbook/Linux-i386-Boot-Code-HOWTO.xml
View File

@ -3,7 +3,7 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" []>
<article>
<article id="Linux-i386-Boot-Code-HOWTO">
<articleinfo>
@ -469,7 +469,7 @@ SECTIONS
<tbody>
<row>
<entry>zImage
<footnote>
<footnote id="ftn-zimage-compressed">
<para>
<emphasis>zImage</emphasis> alias:
<emphasis>compressed</emphasis>;
@ -478,7 +478,7 @@ SECTIONS
</entry>
<entry><command>@$(MAKE) -C arch/i386/boot zImage</command>
<!-- Break it into paras to beautify html output -->
<footnote>
<footnote id="ftn-make-C-option">
<para>
"-C" is a MAKE command line option
to change directory before reading makefiles;
@ -682,7 +682,7 @@ if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi</screen>
<entry>tools/build: tools/build.c</entry>
<entry>
<command>$(HOSTCC) $(HOSTCFLAGS) -o $@ $&lt; -I$(TOPDIR)/include</command>
<footnote><para>
<footnote id="ftn-make-dollar-at"><para>
"$@" means target, "$&lt;" means first prerequisite; Refer to
<ulink url="http://www.gnu.org/software/make/manual/html_chapter/make_10.html#SEC111">
GNU make: Automatic Variables</ulink>;
@ -693,7 +693,7 @@ if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi</screen>
<entry>bootsect: bootsect.o</entry>
<entry>
<command>$(LD) -Ttext 0x0 -s --oformat binary bootsect.o</command>
<footnote>
<footnote id="ftn-oformat-binary">
<para>
"--oformat binary" asks for raw binary output,
which is identical to the memory dump of the executable;
@ -804,7 +804,7 @@ if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi</screen>
</thead>
<tbody>
<row>
<entry>vmlinux<footnote><para>
<entry>vmlinux<footnote id="ftn-vmlinux-target"><para>
Target <emphasis>vmlinux</emphasis> here is different from
that defined in <filename>linux/Makefile</filename>;
</para></footnote>
@ -829,7 +829,7 @@ if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi</screen>
<entry>misc.o</entry>
<entry>
<screen>$(CC) $(CFLAGS) -DKBUILD_BASENAME=$(subst $(comma),_,$(subst -,_,$(*F)))
-c misc.c<footnote><para>"subst" is a MAKE function; Refer to
-c misc.c<footnote id="ftn-make-function-subst"><para>"subst" is a MAKE function; Refer to
<ulink url="http://www.gnu.org/software/make/manual/html_chapter/make_8.html#SEC85">GNU make: Functions for String Substitution and Analysis</ulink>.
</para></footnote></screen>
</entry>
@ -2692,7 +2692,7 @@ asmlinkage int decompress_kernel(struct moveparams *mv, void *rmode)
<entry>IDentification 2</entry>
<entry>1</entry>
<entry>139 (0x8b, \213)
<footnote><para>
<footnote id="ftn-gzip-id2"><para>
ID2 value can be 158 (0x9e, \236) for gzip 0.5;
</para></footnote>
</entry>
@ -2720,7 +2720,7 @@ asmlinkage int decompress_kernel(struct moveparams *mv, void *rmode)
<entry>eXtra FLags</entry>
<entry>1</entry>
<entry>2 - compressor used maximum compression, slowest algorithm
<footnote><para>
<footnote id="ftn-gzip-xfl"><para>
XFL value 4 - compressor used fastest algorithm;
</para></footnote>
</entry>
@ -2736,7 +2736,7 @@ asmlinkage int decompress_kernel(struct moveparams *mv, void *rmode)
<entry>-</entry>
<entry>-</entry>
<entry>variable length, field indicated by FLG
<footnote><para>
<footnote id="ftn-gzip-extra-fields"><para>
FLG bit 0, FTEXT, does not indicate any "extra field".
</para></footnote>
</entry>

6
LDP/howto/docbook/PA-RISC-Linux-Boot-HOWTO.xml
View File

@ -266,7 +266,8 @@
<para>With the release of &PA; architecture in &D;&nbsp;3.0
(aka <emphasis>Woody</emphasis>), a major improvement was
made in term of quantity and quality of hardware support.
Since 0.9.3 released<footnote><para>Before the first release of Debian on hppa,
Since 0.9.3 released<footnote id="ftn-debian-support"><para>
Before the first release of Debian on hppa,
there has been unofficial releases of Woody snapshots, entitled "&PL; releases",
and numbered <emphasis>0.x</emphasis>. Immediately after the release of Woody,
the &PL; port switched to the normal Debian numbering scheme. In other words,
@ -1065,7 +1066,8 @@ BOOT_ADMIN&gt; boot lan isl
(both have a userland application and a boot loader executable),
it&apos;s worth mentioning that &PO; doesn&apos;t usually need to be called
every time you build and install a new kernel, as
<application>LILO</application> does<footnote><para>For the knowledge addict:
<application>LILO</application> does<footnote id="ftn-compare-po-lilo">
<para>For the knowledge addict:
&PO; can actually access and read ext2/ext3 filesystem, and therefore follow symlinks,
whereas <application>LILO</application> bootloader will only know the physical
disk address to access the kernel. See

4
LDP/howto/docbook/Secure-CVS-Pserver.xml
View File

@ -2,7 +2,7 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<article id="Secure-CVS-Pserver">
<articleinfo>
<title>Secure CVS Pserver Mini-HOWTO</title>
@ -271,7 +271,7 @@ Limit coredumpsize 0
The file <filename>READERS</filename> is a list of users who have
read-only access to the CVS repository. People with write access
are listed in the file <filename>WRITERS</filename>. Read the cvs
manual <footnote><para>info cvs, if you have the stand-alone
manual <footnote id="ftn-try-info-cvs"><para>info cvs, if you have the stand-alone
<command>info</command> viewer installed on your system</para></footnote>
for more information on these files.
</para>

12
LDP/howto/docbook/TimeSys-Linux-Install-HOWTO.xml
View File

@ -3,7 +3,7 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://docbook.org/xml/4.2/docbookx.dtd" []>
<article>
<article id="TimeSys-Linux-Install-HOWTO">
<articleinfo>
@ -19,7 +19,7 @@
<pubdate>2005-04-05</pubdate>
<revhistory>
<revhistory id="revhistory">
<revision>
<revnumber>1.0</revnumber>
<date>2005-04-05</date>
@ -146,12 +146,12 @@
<itemizedlist>
<listitem>
<para>
<ulink url="ftp://ftp.redhat.com/pub/redhat/linux/9/en/">Red Hat Linux 9</ulink> <footnote><para>Other Linux distributions are compatible with TimeSys Linux, but I find that RHL9 is the most TimeSys-friendly.</para></footnote>
<ulink url="ftp://ftp.redhat.com/pub/redhat/linux/9/en/">Red Hat Linux 9</ulink> <footnote id="ftn-friendly-distros"><para>Other Linux distributions are compatible with TimeSys Linux, but I find that RHL9 is the most TimeSys-friendly.</para></footnote>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://timesys.com/index.cfm?bdy=linux_bdy_download.cfm&amp;item_id=3827">TimeSys Linux 4.1 Build 155 for the generic Pentium</ulink> <footnote><para>Other versions should work, of course, but this is the one I tested. Note, too, that TimeSys may occasionally update its kernel with security fixes, so obtaining the most recent build is recommended.</para></footnote>
<ulink url="http://timesys.com/index.cfm?bdy=linux_bdy_download.cfm&amp;item_id=3827">TimeSys Linux 4.1 Build 155 for the generic Pentium</ulink> <footnote id="ftn-version-viability"><para>Other versions should work, of course, but this is the one I tested. Note, too, that TimeSys may occasionally update its kernel with security fixes, so obtaining the most recent build is recommended.</para></footnote>
</para>
</listitem>
<listitem>
@ -245,7 +245,7 @@
<programlisting>
<prompt># </prompt><userinput><command>make</command> dep</userinput>
<prompt># </prompt><userinput><command>make</command> bzImage</userinput> <footnote><para>If you get errors about not finding <command>i586-linux-gcc</command>, edit the <filename>Makefile</filename> and comment out the line about CROSS_COMPILE.</para></footnote>
<prompt># </prompt><userinput><command>make</command> bzImage</userinput> <footnote id="ftn-cross-compile-tip"><para>If you get errors about not finding <command>i586-linux-gcc</command>, edit the <filename>Makefile</filename> and comment out the line about CROSS_COMPILE.</para></footnote>
<prompt># </prompt><userinput><command>make</command> modules</userinput>
<prompt># </prompt><userinput><command>make</command> modules_install</userinput>
<prompt># </prompt><userinput><command>make</command> install</userinput>
@ -270,7 +270,7 @@
</para>
<programlisting>
<prompt># </prompt><userinput><command>rpmbuild</command> -ba rpm.spec</userinput> <footnote><para>If your system can't find <command>rpmbuild</command>, you may need to install the <filename>rpm-build</filename> package first.</para></footnote>
<prompt># </prompt><userinput><command>rpmbuild</command> -ba rpm.spec</userinput> <footnote id="ftn-rpm-build-package"><para>If your system can't find <command>rpmbuild</command>, you may need to install the <filename>rpm-build</filename> package first.</para></footnote>
</programlisting>
<para>

2
LDP/howto/docbook/XFree-Local-multi-user-HOWTO.xml
View File

@ -164,7 +164,7 @@ but on the web page of it's author, the pioneer Miguel Freitas.
<para>So Backstreet Ruby brings to the current stable Linux kernel (Linux-2.4) the enhanced input subsystem and the ability to use multiple graphic cards and multiple keyboards independently, in order to make multiple local XFree users on a single PC system possible. </para>
<para>You can have multiple independent graphic cards and multiple independent mice, but in order for multiple users to interact with the system, they do need independent keyboards as well. Multiple independent keyboards is the feature that Linux-2.4 (and in the future Linux-2.6) lacks, and this is what Backstreet Ruby adds to the stable Linux kernel Linux-2.4. </para>
<para>The entire work on back porting Ruby to Linux-2.4 is done by Aivils Stoss. <email>Aivils.Stoss (at) unibanka.lv</email></para>
<para>Aivils got recently his hands on Ruby, and now Ruby is fully functional<footnote>
<para>Aivils got recently his hands on Ruby, and now Ruby is fully functional<footnote id="ftn-backstreet-ruby">
<para>All the features in Backstreet Ruby are included ( "/proc " interface &amp; hot-plugging, video hack, ...), support for Framebuffer devices, support for single Framebuffer console which takes over the VGA console (support for multiple independent Framebuffer consoles is not yet implemented)</para>
</footnote> too, so if you prefer the Linux-2.6 kernel you might use Ruby instead of Linux-2.4 + Backstreet Ruby.</para>
<para>Visit his web site for more information on the patch itself, on the current status, how to build a kernel using his patch or how to build modified XFree86 server.</para>

11
LDP/howto/docbook/XWindow-User-HOWTO.xml
View File

@ -33,11 +33,10 @@
</authorgroup>
<revhistory>
<revision
><revnumber>v4.0</revnumber
><date>2010-01-12</date><authorinitials>cy</authorinitials
><revremark>Converted to XML docbook and to the new domain.</revremark
></revision>
<revision><revnumber>v4.0
</revnumber><date>2010-01-12</date>
<authorinitials>cy</authorinitials>
<revremark>Converted to XML docbook and to the new domain.</revremark></revision>
<revision>
<revnumber>v3.1</revnumber>
<date>2002-10-10</date>
@ -73,7 +72,7 @@
<abstract>
<para>
<footnote><literallayout>
<footnote id="ftn-changelog-dump"><literallayout>
<![CDATA[
v4.x changes:
- artheader tag changed to articleinfo