Changeset 24ca7aa
- Timestamp:
- 05/30/2005 09:44:19 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.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:
- a71ee9cb
- Parents:
- cec675bd
- Location:
- introduction/important
- Files:
-
- 5 edited
-
beyond.xml (modified) (6 diffs)
-
bootscripts.xml (modified) (2 diffs)
-
patches.xml (modified) (1 diff)
-
pkgmgt.xml (modified) (4 diffs)
-
position.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/beyond.xml
rcec675bd r24ca7aa 17 17 18 18 <para>The packages that are installed in this book are only the tip of the 19 iceberg. We hope that the experience you gained with the LFS book and 20 the BLFS book will give you the background needed to compile, install 19 iceberg. We hope that the experience you gained with the LFS book and 20 the BLFS book will give you the background needed to compile, install 21 21 and configure packages that are not included in this book.</para> 22 22 23 23 <para>When you want to install a package to a location other than 24 <filename class='directory'>/</filename>, or 24 <filename class='directory'>/</filename>, or 25 25 <filename class='directory'>/usr</filename>, you are installing 26 26 outside the default environment settings on most machines. The following … … 35 35 </listitem> 36 36 <listitem> 37 <para>Expand the <envar>PATH</envar> for 37 <para>Expand the <envar>PATH</envar> for 38 38 <systemitem class="username">root</systemitem> to include 39 39 <filename class='directory'>$PREFIX/sbin</filename>.</para> … … 62 62 </listitem> 63 63 <listitem> 64 <para>Add <filename class='directory'>$PREFIX/include</filename> to 65 <envar>CPPFLAGS</envar> when compiling packages that depend on 64 <para>Add <filename class='directory'>$PREFIX/include</filename> to 65 <envar>CPPFLAGS</envar> when compiling packages that depend on 66 66 the package you installed.</para> 67 67 </listitem> … … 81 81 </listitem> 82 82 <listitem> 83 <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 the 85 executable. If the results are overwhelming, try searching for the given 83 <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 the 85 executable. If the results are overwhelming, try searching for the given 86 86 executable in the Debian repository at 87 87 <ulink url="http://www.debian.org/distrib/packages#search_contents"/>.</para> … … 95 95 <para>Many of the newer packages follow the <command>./configure 96 96 && make && make install</command> process. 97 Help on the options accepted by configure can be obtained via the 97 Help on the options accepted by configure can be obtained via the 98 98 command <command>./configure --help</command>.</para> 99 99 </listitem> … … 114 114 <tip> 115 115 <para>If you have found a package that is only available in .deb or .rpm 116 format, there are two small scripts, <command>rpm2targz</command> and 117 <command>deb2targz</command> that are available at 118 <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and 119 <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives 116 format, there are two small scripts, <command>rpm2targz</command> and 117 <command>deb2targz</command> that are available at 118 <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and 119 <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives 120 120 into a simple <filename>tar.gz</filename> format.</para> 121 121 </tip> -
introduction/important/bootscripts.xml
rcec675bd r24ca7aa 24 24 </indexterm> 25 25 26 <para>The BLFS Bootscripts package contains the init 27 scripts that are used throughout the book. It is assumed that you will be 28 using the blfs-bootscripts package in conjuction with a compatible 29 lfs-bootscripts package. Refer to 30 <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more 26 <para>The BLFS Bootscripts package contains the init 27 scripts that are used throughout the book. It is assumed that you will be 28 using the blfs-bootscripts package in conjuction with a compatible 29 lfs-bootscripts package. Refer to 30 <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more 31 31 information on the lfs-bootscripts package.</para> 32 32 … … 38 38 </itemizedlist> 39 39 40 <para>The blfs-bootscripts package will be used throughout the BLFS book 41 for startup scripts. Unlike LFS, each init script has a separate install target 42 in the blfs-bootscripts package. It is recomended you keep the package source 43 directory around until completion of your BLFS system. When a script is 44 requested from blfs-bootscripts, simply change to the directory and as the 45 <systemitem class="username">root</systemitem> user, execute the given 40 <para>The blfs-bootscripts package will be used throughout the BLFS book 41 for startup scripts. Unlike LFS, each init script has a separate install target 42 in the blfs-bootscripts package. It is recomended you keep the package source 43 directory around until completion of your BLFS system. When a script is 44 requested from blfs-bootscripts, simply change to the directory and as the 45 <systemitem class="username">root</systemitem> user, execute the given 46 46 <command>make install-<replaceable>[init-script]</replaceable></command> 47 command. This command installs the init script to its proper location (along 48 with any auxillary configuration scripts) and also creates the appropriate 47 command. This command installs the init script to its proper location (along 48 with any auxillary configuration scripts) and also creates the appropriate 49 49 symlinks to start and stop the service at the appropriate run-level.</para> 50 50 -
introduction/important/patches.xml
rcec675bd r24ca7aa 33 33 </itemizedlist> 34 34 35 <para>In short, the book only includes patches that are either required or 36 recommended. There is a 35 <para>In short, the book only includes patches that are either required or 36 recommended. There is a 37 37 <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink> 38 which hosts various patches (including the patches referenced in the books) 38 which hosts various patches (including the patches referenced in the books) 39 39 to enable you to configure your LFS the way you like it.</para> 40 40 -
introduction/important/pkgmgt.xml
rcec675bd r24ca7aa 48 48 <title>Upgrade Issues</title> 49 49 50 <para>A Package Manager makes it easy to upgrade to newer versions when 51 they are released. Generally the instructions in the LFS and BLFS Book can be 52 used to upgrade to the newer versions. Here are some points that you should 50 <para>A Package Manager makes it easy to upgrade to newer versions when 51 they are released. Generally the instructions in the LFS and BLFS Book can be 52 used to upgrade to the newer versions. Here are some points that you should 53 53 be aware of when upgrading packages, especially on a running system.</para> 54 54 … … 78 78 </listitem> 79 79 <listitem> 80 <para>If you are upgrading a running system, be on the lookout for packages 80 <para>If you are upgrading a running system, be on the lookout for packages 81 81 that use <command>cp</command> instead of <command>install</command> 82 82 to install files. The latter command is usually safer if the executable or library … … 134 134 135 135 <para>The installation needs to be faked, so that the package thinks that it is 136 installed in <filename class="directory">/usr</filename> though in reality it is 137 installed in <filename class="directory">/usr/pkg</filename> hierarchy. 138 Installing in this manner is not usually a trivial task. For example, consider 139 that you are installing a package libfoo-1.1. The following instructions may 136 installed in <filename class="directory">/usr</filename> though in reality it is 137 installed in <filename class="directory">/usr/pkg</filename> hierarchy. 138 Installing in this manner is not usually a trivial task. For example, consider 139 that you are installing a package libfoo-1.1. The following instructions may 140 140 not install the package properly:</para> 141 141 142 <screen><userinput>./configure --prefix=/usr/pkg/libfoo/1.1 142 <screen><userinput>./configure --prefix=/usr/pkg/libfoo/1.1 143 143 make 144 144 make install</userinput></screen> … … 211 211 <title>User Based Management</title> 212 212 213 <para>This scheme, that is unique to LFS, was devised by Matthias Benkmann, 214 and is available from the <ulink url="http://www.linuxfromscratch.org/hints/">Hints 215 Project</ulink>. In this scheme, each package is installed as a separate user 216 into the standard locations. Files belonging to a package are easily identified 217 by checking the user id. The features and shortcomings of this approach are 213 <para>This scheme, that is unique to LFS, was devised by Matthias Benkmann, 214 and is available from the <ulink url="http://www.linuxfromscratch.org/hints/">Hints 215 Project</ulink>. In this scheme, each package is installed as a separate user 216 into the standard locations. Files belonging to a package are easily identified 217 by checking the user id. The features and shortcomings of this approach are 218 218 too complex to describe in this section. For the details please see the hint at <ulink 219 219 url="http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt"/>.</para> -
introduction/important/position.xml
rcec675bd r24ca7aa 22 22 LFS based system.</para> 23 23 24 <para>In traditional Unix systems, <filename>/usr</filename> usually 24 <para>In traditional Unix systems, <filename>/usr</filename> usually 25 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 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 29 directories within it.</para> 30 30 31 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 32 that <filename>/usr</filename> is managed by the distribution's 33 package system and <filename>/usr/local</filename> is not. This way the 34 34 package manager's database knows about every file within 35 35 <filename>/usr</filename>.</para> 36 36 37 <para>LFS users build their own system and so deciding where 38 the system ends and local files begin is not straightforward. So the choice 37 <para>LFS users build their own system and so deciding where 38 the system ends and local files begin is not straightforward. So the choice 39 39 should be made in order to make things easier to administer. There are several 40 40 reasons for dividing files between <filename>/usr</filename> and … … 43 43 <itemizedlist> 44 44 <listitem> 45 <para>On a network of several machines all running LFS, 46 or mixed LFS and other Linux distributions, 45 <para>On a network of several machines all running LFS, 46 or mixed LFS and other Linux distributions, 47 47 <filename>/usr/local</filename> could be used to hold packages 48 48 that are common between all the computers in the network. It can be 49 NFS mounted or mirrored from a single server. Here local 49 NFS mounted or mirrored from a single server. Here local 50 50 indicates local to the site.</para> 51 51 </listitem> 52 52 <listitem> 53 <para>On a network of several computers all running an identical 54 LFS system <filename>/usr/local</filename> could hold 55 packages that are different between the machines. In this case local refers 53 <para>On a network of several computers all running an identical 54 LFS system <filename>/usr/local</filename> could hold 55 packages that are different between the machines. In this case local refers 56 56 to the individual computers.</para> 57 57 </listitem> 58 58 <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 59 <para>Even on a single computer <filename>/usr/local</filename> can 60 be useful if you have several distributions installed simultaneously, and want 61 61 a place to put packages that will be the same on all of them.</para> 62 62 </listitem> 63 63 <listitem> 64 <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 way 66 you can wipe the LFS file system and start from a clean 64 <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 way 66 you can wipe the LFS file system and start from a clean 67 67 partition every time without losing everything.</para> 68 68 </listitem> … … 72 72 /usr/site</filename>, rather than <filename>/usr/local</filename>?</para> 73 73 74 <para>There is nothing stopping you, many sites do make their own trees, 74 <para>There is nothing stopping you, many sites do make their own trees, 75 75 however it makes installing new software more difficult. Automatic installers 76 76 often look for dependencies in <filename>/usr</filename> and 77 77 <filename>/usr/local</filename>, and if the file it is looking 78 for is in <filename>/usr/site</filename> instead, the installer will 78 for is in <filename>/usr/site</filename> instead, the installer will 79 79 probably fail unless you specifically tell it where to look.</para> 80 80
Note:
See TracChangeset
for help on using the changeset viewer.
