Changeset 4afc2603
- Timestamp:
- 12/29/2005 01:24:51 AM (18 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 5254d12
- Parents:
- 17be8c3
- Files:
-
- 2 added
- 18 edited
Legend:
- Unmodified
- Added
- Removed
-
book/preface.xml
r17be8c3 r4afc2603 106 106 107 107 <para>Changes and upgrades to the individual packages are detailed in the 108 <xref linkend=' intro-welcome-changelog'/>. There you will see literally hundreds of108 <xref linkend='changelog'/>. There you will see literally hundreds of 109 109 changes made since the last edition. In this change log, one name that you 110 110 will see over and over is Randy McMurchy. Without his efforts this … … 144 144 extending a basic Linux From Scratch system. The instructions in this 145 145 version of BLFS are based on the LFS 6.1 Book. As usual, the list of 146 packages that have been upgraded or added are in the <xref147 linkend='intro-welcome-changelog'/>.</para>146 packages that have been upgraded or added are in the 147 <xref linkend='changelog'/>.</para> 148 148 149 149 <para>One major accomplishment in this -
introduction/important/beyond.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-important-beyond">8 <sect1 id="beyond" xreflabel="Going Beyond BLFS"> 9 9 <?dbhtml filename="beyond.html"?> 10 10 … … 42 42 <para>Add <filename class='directory'>$PREFIX/lib</filename> 43 43 to <filename>/etc/ld.so.conf</filename> or expand 44 <envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter option, 45 check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. If you 46 modify <filename>/etc/ld.so.conf</filename>, remember to update 47 <filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command> 48 as the <systemitem class="username">root</systemitem> user.</para> 44 <envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter 45 option, check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. 46 If you modify <filename>/etc/ld.so.conf</filename>, remember to update 47 <filename>/etc/ld.so.cache</filename> by executing 48 <command>ldconfig</command> as the 49 <systemitem class="username">root</systemitem> user.</para> 49 50 </listitem> 50 51 <listitem> 51 52 <para>Add <filename class='directory'>$PREFIX/man</filename> 52 to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para> 53 to <filename>/etc/man.conf</filename> or expand 54 <envar>MANPATH</envar>.</para> 53 55 </listitem> 54 56 <listitem> … … 57 59 </listitem> 58 60 <listitem> 59 <para>Add <filename 60 class='directory'>$PREFIX/lib/pkgconfig</filename> to 61 <envar>PKG_CONFIG_PATH</envar>.</para> 61 <para>Add <filename class='directory'>$PREFIX/lib/pkgconfig</filename> 62 to <envar>PKG_CONFIG_PATH</envar>. Some packages are now installing 63 <filename class='extension'>.pc</filename> files in 64 <filename class='directory'>$PREFIX/share/pkgconfig</filename>, so you may 65 have to include this directory also.</para> 62 66 </listitem> 63 67 <listitem> … … 69 73 70 74 <para>If you are in search of a package that is not in the book, the following 71 are different ways you can search for the concerned package.</para>75 are different ways you can search for the desired package.</para> 72 76 73 77 <itemizedlist> … … 75 79 <para>If you know the name of the package, then search FreshMeat for 76 80 it at <ulink url="http://freshmeat.net/"/>. Also search Google at 77 <ulink url="http://google.com/"/>. Sometimes a search for the rpm at 78 <ulink url="http://rpmfind.net/"/> or the deb at 79 <ulink url="http://www.debian.org/distrib/packages#search_packages"/> can also 80 lead to a link to the package.</para> 81 <ulink url="http://google.com/"/>. Sometimes a search for the 82 <filename class='extension'>rpm</filename> at 83 <ulink url="http://rpmfind.net/"/> or the 84 <filename class='extension'>deb</filename> at 85 <ulink url="http://www.debian.org/distrib/packages#search_packages"/> can 86 also lead to a link to the package.</para> 81 87 </listitem> 82 88 <listitem> 83 89 <para>If you know the name of the executable, but not the package 84 that the executable belongs to, first try a google search with the name of the85 executable. If the results are overwhelming, try searching for the given86 executable in the Debian repository at87 <ulinkurl="http://www.debian.org/distrib/packages#search_contents"/>.</para>90 that the executable belongs to, first try a Google search with the name 91 of the executable. If the results are overwhelming, try searching for the 92 given executable in the Debian repository at <ulink 93 url="http://www.debian.org/distrib/packages#search_contents"/>.</para> 88 94 </listitem> 89 95 </itemizedlist> … … 101 107 <para>Most of the packages contain documentation on compiling and 102 108 installing the package. Some of the documents are excellent, some not so 103 excellent. Check out the homepage of the package for any additional and updated104 hints for compiling and configuring the package.</para>109 excellent. Check out the homepage of the package for any additional and 110 updated hints for compiling and configuring the package.</para> 105 111 </listitem> 106 112 <listitem> 107 113 <para>If you are having a problem compiling the package, try 108 searching the lfs archives at <ulink url="http://search.linuxfromscratch.org/"/> 109 for the error or if that fails try searching Google. If everything else fails, 110 try the blfs-support mailing-list/news-group.</para> 114 searching the LFS archives at 115 <ulink url="http://search.linuxfromscratch.org/"/> for the error or if 116 that fails, try searching Google. If everything else fails, 117 try the blfs-support mailing-list.</para> 111 118 </listitem> 112 119 </itemizedlist> 113 120 114 121 <tip> 115 <para>If you have found a package that is only available in .deb or .rpm 122 <para>If you have found a package that is only available in 123 <filename class='extension'>.deb</filename> or 124 <filename class='extension'>.rpm</filename> 116 125 format, there are two small scripts, <command>rpm2targz</command> and 117 126 <command>deb2targz</command> that are available at -
introduction/important/patches.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-important-patches">8 <sect1 id="patches"> 9 9 <?dbhtml filename="patches.html"?> 10 10 -
introduction/important/pkgmgt.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-important-pkgmgt">8 <sect1 id="pkgmgt"> 9 9 <?dbhtml filename="pkgmgt.html"?> 10 10 … … 43 43 <para>There are some hints written on the topic of package management. Visit 44 44 the <ulink url="&hints-root;">Hints subproject</ulink> 45 to findif one of them fits your need.</para>45 and see if one of them fits your need.</para> 46 46 47 47 <sect2> … … 86 86 <para>If you are upgrading a running system, be on the lookout for packages 87 87 that use <command>cp</command> instead of <command>install</command> 88 to install files. The latter command is usually safer if the executable or library89 is already loaded in memory.</para>88 to install files. The latter command is usually safer if the executable 89 or library is already loaded in memory.</para> 90 90 </listitem> 91 91 </itemizedlist> … … 114 114 <title>Install in Separate Directories</title> 115 115 116 <para>This is a simplistic package management that does not need any extra package117 to manage the installations. Each package is installed in a separate directory.118 For example, package foo-1.1 is installed in116 <para>This is a simplistic package management that does not need any 117 extra package to manage the installations. Each package is installed in a 118 separate directory. For example, package foo-1.1 is installed in 119 119 <filename class='directory'>/usr/pkg/foo-1.1</filename> 120 120 and a symlink is made from <filename>/usr/pkg/foo</filename> to … … 125 125 126 126 <para>The environment variables such as those mentioned in 127 < xref linkend="intro-important-beyond"/> need to be expanded to127 <quote><xref linkend="beyond"/></quote> need to be expanded to 128 128 include <filename>/usr/pkg/foo</filename>. For more than a few packages, 129 129 this scheme becomes unmanageable.</para> -
introduction/important/position.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-important-position">8 <sect1 id="position"> 9 9 <?dbhtml filename="position.html"?> 10 10 … … 22 22 LFS based system.</para> 23 23 24 <para>In traditional Unix systems, <filename>/usr</filename> usually 25 contains files that come with the system distribution, and the <filename> 26 /usr/local</filename> tree is free for the local administrator to manage. 27 The only really hard and fast rule is that Unix distributions should not 28 touch <filename>/usr/local</filename>, except perhaps to create the basic 29 directories within it.</para> 24 <para>In traditional Unix systems, 25 <filename class='directory'>/usr</filename> usually contains files that come 26 with the system distribution, and the 27 <filename class='directory'>/usr/local</filename> tree is free for the local 28 administrator to manage. The only really hard and fast rule is that Unix 29 distributions should not touch 30 <filename class='directory'>/usr/local</filename>, except perhaps to create 31 the basic directories within it.</para> 30 32 31 <para>With Linux distributions, like Red Hat, Debian etc. a possible rule is 32 that <filename>/usr</filename> is managed by the distribution's 33 package system and <filename>/usr/local</filename> is not. This way the 33 <para>With Linux distributions like Red Hat, Debian, etc., a possible rule is 34 that <filename class='directory'>/usr</filename> is managed by the 35 distribution's package system and 36 <filename class='directory'>/usr/local</filename> is not. This way the 34 37 package manager's database knows about every file within 35 <filename >/usr</filename>.</para>38 <filename class='directory'>/usr</filename>.</para> 36 39 37 40 <para>LFS users build their own system and so deciding where 38 41 the system ends and local files begin is not straightforward. So the choice 39 should be made in order to make things easier to administer. There are several 40 reasons for dividing files between <filename>/usr</filename> and 41 <filename>/usr/local</filename>.</para> 42 should be made in order to make things easier to administer. There are 43 several reasons for dividing files between 44 <filename class='directory'>/usr</filename> and 45 <filename class='directory'>/usr/local</filename>.</para> 42 46 43 47 <itemizedlist> 44 48 <listitem> 45 <para>On a network of several machines all running LFS, 46 o r mixed LFS and other Linux distributions,47 <filename >/usr/local</filename> could be used to hold packages48 that are common between all the computers in the network. It can be49 NFS mounted or mirrored from a single server. Here local50 indicateslocal to the site.</para>49 <para>On a network of several machines all running LFS, or mixed LFS and 50 other Linux distributions, 51 <filename class='directory'>/usr/local</filename> could be used to hold 52 packages that are common between all the computers in the network. It can 53 be NFS mounted or mirrored from a single server. Here local indicates 54 local to the site.</para> 51 55 </listitem> 52 56 <listitem> 53 57 <para>On a network of several computers all running an identical 54 LFS system <filename>/usr/local</filename> could hold55 packages that are different between the machines. In this case local refers56 to the individual computers.</para>58 LFS system, <filename class='directory'>/usr/local</filename> could hold 59 packages that are different between the machines. In this case local 60 refers to the individual computers.</para> 57 61 </listitem> 58 62 <listitem> 59 <para>Even on a single computer <filename>/usr/local</filename> can 60 be useful if you have several distributions installed simultaneously, and want 63 <para>Even on a single computer, 64 <filename class='directory'>/usr/local</filename> can be useful if you 65 have several distributions installed simultaneously, and want 61 66 a place to put packages that will be the same on all of them.</para> 62 67 </listitem> 63 68 <listitem> 64 69 <para>Or you might regularly rebuild your LFS, but 65 want a place to put files that you don't want to rebuild each time. This way66 you can wipe the LFS file system and start from a clean70 want a place to put files that you don't want to rebuild each time. This 71 way you can wipe the LFS file system and start from a clean 67 72 partition every time without losing everything.</para> 68 73 </listitem> 69 74 </itemizedlist> 70 75 71 <para>Some people ask why not use your own directory tree, e.g., <filename> 72 /usr/site</filename>, rather than <filename>/usr/local</filename>?</para> 76 <para>Some people ask why not use your own directory tree, e.g., 77 <filename class='directory'>/usr/site</filename>, rather than 78 <filename class='directory'>/usr/local</filename>?</para> 73 79 74 80 <para>There is nothing stopping you, many sites do make their own trees, 75 81 however it makes installing new software more difficult. Automatic installers 76 often look for dependencies in <filename>/usr</filename> and 77 <filename>/usr/local</filename>, and if the file it is looking 78 for is in <filename>/usr/site</filename> instead, the installer will 79 probably fail unless you specifically tell it where to look.</para> 82 often look for dependencies in 83 <filename class='directory'>/usr</filename> and 84 <filename class='directory'>/usr/local</filename>, and if the file it is 85 looking for is in <filename class='directory'>/usr/site</filename> instead, 86 the installer will probably fail unless you specifically tell it where to 87 look.</para> 80 88 81 89 <para><emphasis>What is the BLFS position on this?</emphasis></para> 82 90 83 91 <para>All of the BLFS instructions install programs in 84 <filename>/usr</filename> with optional instructions to install into 85 <filename>/opt</filename> for some specific packages.</para> 92 <filename class='directory'>/usr</filename> with optional instructions to 93 install into <filename class='directory'>/opt</filename> for some specific 94 packages.</para> 86 95 87 96 </sect1> -
introduction/important/unpacking.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-important-unpacking">8 <sect1 id="unpacking"> 9 9 <?dbhtml filename="unpacking.html"?> 10 10 … … 16 16 <title>Notes on Building Software</title> 17 17 18 <para>Those people who have built an LFS system willbe aware18 <para>Those people who have built an LFS system may be aware 19 19 of the general principles of downloading and unpacking software. We will 20 20 however repeat some of that information here for those new to building … … 34 34 <para>We can not emphasize strongly enough that you should start from a 35 35 <emphasis>clean source tree</emphasis> each time. This means that if 36 you have had an error, it's usually best to delete the source tree and 36 you have had an error during configuration or compilation, it's usually 37 best to delete the source tree and 37 38 re-unpack it <emphasis>before</emphasis> trying again. This obviously 38 39 doesn't apply if you're an advanced user used to hacking … … 143 144 <itemizedlist> 144 145 <listitem> 145 <para><emphasis>Required</emphasis> means 146 that the target package cannot be correctly built without147 the dependency having first beeninstalled.</para>146 <para><emphasis>Required</emphasis> means that the target package 147 cannot be correctly built without the dependency having first been 148 installed.</para> 148 149 </listitem> 149 150 <listitem> 150 <para><emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is 151 installed first for a clean and trouble-free build, that won't have 152 issues either during the build process, or at run-time.</para> 151 <para><emphasis>Recommended</emphasis> means that BLFS strongly 152 suggests this package is installed first for a clean and trouble-free 153 build, that won't have issues either during the build process, or at 154 run-time.</para> 153 155 </listitem> 154 156 <listitem> 155 <para><emphasis>Optional</emphasis> means that this package might be installed for added156 functionality. Often BLFS will qualify the dependency to explainthe157 157 <para><emphasis>Optional</emphasis> means that this package might be 158 installed for added functionality. Often BLFS will describe the 159 dependency to explain the added functionality that will result.</para> 158 160 </listitem> 159 161 </itemizedlist> -
introduction/introduction.xml
r17be8c3 r4afc2603 11 11 <title>Introduction</title> 12 12 13 <chapter id="intro-welcome"> 14 <?dbhtml filename="welcome.html"?> 15 16 <title>Welcome to BLFS</title> 17 18 <para>The Beyond Linux From Scratch book is designed to carry on from 19 where the LFS book leaves off. But unlike the LFS book, it isn't designed to 20 be followed straight through. Reading the <xref 21 linkend="intro-welcome-whichsections"/> part of this chapter should help 22 guide you through the book.</para> 23 24 <para>Please read most of this part of the book carefully as it explains 25 quite a few of the conventions we use throughout the book.</para> 26 27 28 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/acknowledgments.xml"/> 29 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/credits.xml"/> 30 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/which.xml"/> 31 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/conventions.xml"/> 32 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/version.xml"/> 33 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/mirrors.xml"/> 34 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/packages.xml"/> 35 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/changelog.xml"/> 36 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/maillists.xml"/> 37 <!-- <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/newsserver.xml"/> --> 38 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/askhelp.xml"/> 39 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/contact.xml"/> 40 41 </chapter> 42 43 <chapter id="intro-important"> 44 <?dbhtml filename="important.html"?> 45 46 <title>Important Information</title> 47 48 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/pkgmgt.xml"/> 49 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/unpacking.xml"/> 50 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/position.xml"/> 51 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/patches.xml"/> 52 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/bootscripts.xml"/> 53 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/beyond.xml"/> 54 55 </chapter> 13 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/welcome.xml"/> 14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/important.xml"/> 56 15 57 16 </part> -
introduction/welcome/acknowledgments.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-acknowledgments">8 <sect1 id="acknowledgments"> 9 9 <?dbhtml filename="acknowledgments.html"?> 10 10 … … 71 71 72 72 </sect1> 73 -
introduction/welcome/askhelp.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-askhelp">8 <sect1 id="askhelp"> 9 9 <?dbhtml filename="askhelp.html"?> 10 10 … … 20 20 you will find that most of the people on Internet Relay Chat (IRC) and on the 21 21 mailing lists are willing to help you. An overview of the LFS mailing 22 lists can be found in <xref linkend=" intro-welcome-maillists"/>. To assist us22 lists can be found in <xref linkend="maillists"/>. To assist us 23 23 in diagnosing and solving your problem, include as much relevant information 24 24 as possible in your request for help.</para> … … 36 36 been loaded? You should use <command>lsmod</command> as the 37 37 <systemitem class='username'>root</systemitem> user to see if it's 38 loaded. Check the <filename>syslog.log</filename> or run38 loaded. Check the <filename>syslog.log</filename> file or run 39 39 <command>modprobe <replaceable>[driver]</replaceable></command> to 40 40 review any error message. If it loads properly, you may need to add … … 57 57 PATH=$PATH:/opt/kde/bin). In most cases, the package instructions will 58 58 walk you through the changes, but some will not. The section called 59 <quote>< ulink url="beyond.html">Going Beyond BLFS</ulink></quote> is59 <quote><xref linkend="beyond"/></quote> is 60 60 available to help you check.</para> 61 61 </listitem> -
introduction/welcome/changelog.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-changelog" xreflabel='Change Log'>8 <sect1 id="changelog" xreflabel='Change Log'> 9 9 <?dbhtml filename="changelog.html"?> 10 10 … … 18 18 <para>Please note that the Change Log only lists which editor was 19 19 responsible for putting the changes into SVN; please read the 20 <xref linkend=" intro-welcome-credits"/> page in Chapter 1 for details on20 <xref linkend="credits"/> page in Chapter 1 for details on 21 21 who wrote what.</para> 22 22 -
introduction/welcome/contact.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-contactinfo">8 <sect1 id="contactinfo"> 9 9 <?dbhtml filename="contactinfo.html"?> 10 10 … … 17 17 18 18 <para>Please direct your emails to one of the BLFS mailing lists. See 19 <xref linkend=" intro-welcome-maillists"/> for more information on19 <xref linkend="maillists"/> for more information on 20 20 the available mailing lists.</para> 21 21 … … 25 25 26 26 </sect1> 27 -
introduction/welcome/conventions.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-conventions">8 <sect1 id="conventions"> 9 9 <?dbhtml filename="conventions.html"?> 10 10 … … 32 32 <blockquote> 33 33 <para>This form of text (fixed width text) is showing screen 34 output, probably a s the result of commands issued andis also used to34 output, probably a result from issuing a command. It is also used to 35 35 show filenames such as <filename>/boot/grub/grub.conf</filename></para> 36 36 </blockquote> … … 48 48 <blockquote> 49 49 <para>This form of text is used for hypertext links external to 50 the book such as HowTo 's, download locations, websites, etc.</para>50 the book such as HowTos, download locations, websites, etc.</para> 51 51 </blockquote> 52 52 … … 84 84 85 85 <blockquote> 86 <para>This form of text is used to show a specific system user reference87 in the instructions.</para>86 <para>This form of text is used to show a specific system user or group 87 reference in the instructions.</para> 88 88 </blockquote> 89 89 -
introduction/welcome/credits.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-credits" xreflabel="Credits">8 <sect1 id="credits" xreflabel="Credits"> 9 9 <?dbhtml filename="credits.html"?> 10 10 -
introduction/welcome/maillists.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-maillists" xreflabel="Mailing lists">8 <sect1 id="maillists" xreflabel="Mailing lists"> 9 9 <?dbhtml filename="maillists.html"?> 10 10 … … 21 21 22 22 <para>For more information regarding which lists are available, how to 23 subscribe to them, archive locations, etc. visit <ulink24 url="http://www.linuxfromscratch.org/mail.html"/>.</para>23 subscribe to them, archive locations, etc., visit 24 <ulink url="http://www.linuxfromscratch.org/mail.html"/>.</para> 25 25 26 26 </sect1> -
introduction/welcome/mirrors.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-mirrors" xreflabel="Mirrors">8 <sect1 id="mirrors" xreflabel="Mirrors"> 9 9 <?dbhtml filename="mirrors.html"?> 10 10 … … 16 16 <title>Mirror Sites</title> 17 17 18 <para>The BLFS project has a number of mirrors set up world-wide to make it19 easier and more convenient for you to access the website. 18 <para>The BLFS project has a number of mirrors set up world-wide to make it 19 easier and more convenient for you to access the website. Please visit the 20 20 <ulink url="http://www.linuxfromscratch.org/mirrors.html"/> website for the 21 21 list of current mirrors.</para> 22 22 23 23 </sect1> 24 25 -
introduction/welcome/packages.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-packages" xreflabel="Getting the Source Packages">8 <sect1 id="packages" xreflabel="Getting the Source Packages"> 9 9 <?dbhtml filename="packages.html"?> 10 10 -
introduction/welcome/version.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-version" xreflabel="Book Version">8 <sect1 id="version" xreflabel="Book Version"> 9 9 <?dbhtml filename="version.html"?> 10 10 … … 18 18 <para>This is BLFS-BOOK version &version; dated &releasedate;. 19 19 If this version is older than a month, a newer version is probably already 20 available for download. Check one of the mirror sites below for updated 20 available for download. Check one of the mirror sites at 21 <ulink url="http://www.linuxfromscratch.org/mirrors.html"/> for updated 21 22 versions.</para> 22 23 23 24 </sect1> 24 -
introduction/welcome/which.xml
r17be8c3 r4afc2603 6 6 ]> 7 7 8 <sect1 id=" intro-welcome-whichsections" xreflabel="Which sections of the book?">8 <sect1 id="whichsections" xreflabel="Which sections of the book?"> 9 9 <?dbhtml filename="which.html"?> 10 10 … … 17 17 18 18 <para>Unlike the Linux From Scratch book, BLFS isn't designed to be 19 followed in a linear manner. This is because LFSprovides instructions19 followed in a linear manner. This is because LFS provides instructions 20 20 on how to create a base system which is capable of turning into anything 21 from a web server to a multimedia desktop system. 21 from a web server to a multimedia desktop system. BLFS is where we try 22 22 to guide you in the process of going from the base system to your intended 23 23 destination. Choice is very much involved.</para> 24 24 25 25 <para>Everyone who reads the book will want to read certain sections. The 26 <xref linkend="introduction"/> part –which you are currently27 reading–contains generic information. Especially take note of the28 information in Important Information (<xref linkend="intro-important"/>), as29 this contains comments about how to unpack software and various other aspects30 which apply throughout the book.</para>26 <xref linkend="introduction"/> part, which you are currently reading, 27 contains generic information. Especially take note of the information in 28 <xref linkend="important"/>, as this contains comments about how to 29 unpack software, issues related to using different locales and various other 30 aspects which apply throughout the book.</para> 31 31 32 32 <para>The part on <xref linkend="postlfs"/> is where most people will want … … 39 39 system.</para> 40 40 41 <para>Following these basic items, most people will want to at least browse41 <para>Following these basic items, most people will want to at least browse 42 42 through the <xref linkend="general"/> part of the book. This part contains 43 43 information on many items which are prerequisites for other sections of the 44 book as well as some items (such as Programming (<xref linkend="general-prog"/>)44 book as well as some items (such as <xref linkend="general-prog"/>) 45 45 which are useful in their own right. Note that you don't have to install all 46 46 of these libraries and packages found in this part to start with, each 47 BLFS install procedure tells you which packages47 BLFS installation procedure tells you which packages 48 48 it depends upon so you can choose the program you want to install and see 49 49 what it needs.</para> … … 61 61 more advanced network services. These are dealt with in the <xref 62 62 linkend="server"/> part of the book. Those wanting to build servers 63 should find a good starting point there. Note that <xref linkend="server"/>63 should find a good starting point there. Note that this section 64 64 also contains information on various database packages.</para> 65 65 66 66 <para>The next parts of the book principally deal with desktop systems. This 67 portion of the book starts with a part talking about <xref linkend="x"/>. 67 portion of the book starts with a part talking about <xref linkend="x"/>. This 68 68 part also deals with some generic X-based libraries (<xref linkend="x-lib"/>). 69 69 After this, <xref linkend="kde"/> and <xref linkend="gnome"/> are given their … … 83 83 84 84 </sect1> 85
Note:
See TracChangeset
for help on using the changeset viewer.