gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Removed obsolete commented text, chapter03.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4595 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Manuel Canales Esparcia 2005-01-30 10:28:53 +00:00
parent d7ea6f24b8
commit 4642c8986a
2 changed files with 2 additions and 59 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
chapter03/introduction.xml
View File

@ -7,54 +7,12 @@
<title>Introduction</title>
<?dbhtml filename="introduction.html"?>
<!--
<para>Below is a list of packages you need to download for building a basic
Linux system. The listed version numbers correspond to versions of the
software that are <emphasis>known</emphasis> to work, and this book is
based upon them. Unless you are an experienced LFS builder, we highly
recommend not to try out newer versions, as the build commands for one
version may not work with a newer version. Also, there is often a good
reason for not using the latest version due to known problems that haven't
been worked around yet.</para>
<para>All the URLs, when possible, refer to the project's page at
<ulink url="http://www.freshmeat.net/"/>. The Freshmeat
pages will give you easy access to the official download sites as well as
project websites, mailing lists, FAQs, changelogs and more.</para>
<para>We can't guarantee that these download locations are always available.
In case a download location has changed since this book was published, please
try to google for the package. Should you remain unsuccessful with this,
try one of the alternative means of downloading listed on
<ulink url="&lfs-root;lfs/packages.html"/>.</para>
<para>You'll need to store all the downloaded packages and patches somewhere
that is conveniently available throughout the entire build. You'll also need a
working directory in which to unpack the sources and build them. A scheme that
works well is to use <filename class="directory">$LFS/sources</filename> as the place to store
the tarballs and patches, <emphasis>and</emphasis> as a working directory.
This way everything you need will be located on the LFS partition and available
during all stages of the building process.</para>
<para>So you may want to execute, as <emphasis>root</emphasis>, the following
command before starting your download session:</para>
-->
<para>Create a dir for the sources:</para>
<screen><userinput>mkdir $LFS/sources</userinput></screen>
<!--
<para>And make this directory writable (and sticky) for your normal user - as
you won't do the downloading as <emphasis>root</emphasis>, we guess:</para>
-->
<para>Set the permissions of that dir:</para>
<screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
<!--
<para>For your convenience the top of the list contains a link to a file
you can use with the <ulink url="http://wget.sunsite.dk">wget</ulink>
program. Using this file and the <command>wget</command> program will
make it easy to download all the files at once, rather than downloading each
and every individual file manually.</para>
-->
</sect1>

15
chapter03/patches.xml
View File

@ -7,13 +7,6 @@
<title>Needed patches</title>
<?dbhtml filename="patches.html"?>
<!--
<para>Besides all those packages, you'll also need several patches. These
correct tiny mistakes in the packages that should be fixed by the maintainer,
or just make some small modifications to bend things our way. You'll need the
following:</para>
-->
<variablelist role="materials">
<varlistentry>
@ -149,12 +142,4 @@ following:</para>
</variablelist>
<!--
<para>In addition to the above required patches, there exist a number of
optional ones created by the LFS community. Most of these solve slight
problems, or enable some functionality that's not enabled by default.
Feel free to examine the patches database, located at <ulink url="&lfs-root;patches/"/>,
and pick any additional patches you wish to use.</para>
-->
</sect1>