Changeset b0ed1af for chapter03/introduction.xml

Timestamp:

01/13/2006 08:08:51 PM (18 years ago)

Author:

Manuel Canales Esparcia <manuel@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

6a3b6af

Parents:

87bae31

Message:

Indented chapter 03.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7273 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter03/introduction.xml (modified) (1 diff)

chapter03/introduction.xml

@@ -1 +1 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
+
 <sect1 id="materials-introduction">
-<title>Introduction</title>
-<?dbhtml filename="introduction.html"?>
+  <?dbhtml filename="introduction.html"?>
 
-<para>This chapter includes a list of packages that need to be downloaded for
-building a basic Linux system. The listed version numbers correspond to versions
-of the software that are known to work, and this book is based on their use. We
-highly recommend not using newer versions because the build commands for one
-version may not work with a newer version. The newest package versions may also
-have problems that require work-arounds. These work-arounds will be developed
-and stabilized in the development version of the book.</para>
+  <title>Introduction</title>
 
-<para>Download locations may not always be accessible. If a download
-location has changed since this book was published, Google (<ulink
-url="http://www.google.com/"/>) provides a useful search engine for
-most packages. If this search is unsuccessful, try one of the
-alternative means of downloading discussed at <ulink
-url="&lfs-root;lfs/packages.html"/>.</para>
+  <para>This chapter includes a list of packages that need to be downloaded for
+  building a basic Linux system. The listed version numbers correspond to versions
+  of the software that are known to work, and this book is based on their use. We
+  highly recommend not using newer versions because the build commands for one
+  version may not work with a newer version. The newest package versions may also
+  have problems that require work-arounds. These work-arounds will be developed
+  and stabilized in the development version of the book.</para>
 
-<para>Downloaded packages and patches will need to be stored somewhere
-that is conveniently available throughout the entire build. A working
-directory is also required to unpack the sources and build them.
-<filename class="directory">$LFS/sources</filename> can be used both
-as the place to store the tarballs and patches and as a working
-directory. By using this directory, the required elements will be
-located on the LFS partition and will be available during all stages
-of the building process.</para>
+  <para>Download locations may not always be accessible. If a download
+  location has changed since this book was published, Google (<ulink
+  url="http://www.google.com/"/>) provides a useful search engine for
+  most packages. If this search is unsuccessful, try one of the
+  alternative means of downloading discussed at <ulink
+  url="&lfs-root;lfs/packages.html"/>.</para>
 
-<para>To create this directory, execute, as user
-<emphasis>root</emphasis>, the following command before starting the
-download session:</para>
+  <para>Downloaded packages and patches will need to be stored somewhere
+  that is conveniently available throughout the entire build. A working
+  directory is also required to unpack the sources and build them.
+  <filename class="directory">$LFS/sources</filename> can be used both
+  as the place to store the tarballs and patches and as a working
+  directory. By using this directory, the required elements will be
+  located on the LFS partition and will be available during all stages
+  of the building process.</para>
+
+  <para>To create this directory, execute, as user <systemitem
+  class="username">root</systemitem>, the following command before starting
+  the download session:</para>
 
 <screen role="nodump"><userinput>mkdir -v $LFS/sources</userinput></screen>
 
-<para>Make this directory writable and sticky. <quote>Sticky</quote>
-means that even if multiple users have write permission on a
-directory, only the owner of a file can delete the file within a
-sticky directory. The following command will enable the write and
-sticky modes:</para>
+  <para>Make this directory writable and sticky. <quote>Sticky</quote>
+  means that even if multiple users have write permission on a
+  directory, only the owner of a file can delete the file within a
+  sticky directory. The following command will enable the write and
+  sticky modes:</para>
 
 <screen role="nodump"><userinput>chmod -v a+wt $LFS/sources</userinput></screen>
 
 </sect1>
-