Changeset acfc391 for introduction/important/position.xml
- Timestamp:
- 09/12/2003 03:09:56 AM (21 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 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, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 7891efc
- Parents:
- 1aacd4b5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/position.xml
r1aacd4b5 racfc391 3 3 <title>The /usr versus /usr/local debate</title> 4 4 5 <para><emphasis>Should I install XXX in /usror6 /usr/local?</emphasis></para>5 <para><emphasis>Should I install XXX in <filename>/usr</filename> or 6 <filename>/usr/local</filename>?</emphasis></para> 7 7 8 <para>This is a question without an obvious answer for an LFS based9 system.</para>8 <para>This is a question without an obvious answer for an 9 <acronym>LFS</acronym> based system.</para> 10 10 11 11 <para>In traditional unix systems, <filename>/usr</filename> usually 12 contains files that come 13 with the system distribution, and the <filename>/usr/local</filename> tree 14 is free for the local administrator to add things to. The only 15 really hard and fast 16 rule is that unix distributions should not touch 17 <filename>/usr/local</filename>, except 18 perhaps for creating the basic directories within it.</para> 12 contains files that come with the system distribution, and the <filename> 13 /usr/local</filename> tree is free for the local administrator to add things 14 to. The only really hard and fast rule is that unix distributions should not 15 touch <filename>/usr/local</filename>, except perhaps for creating the basic 16 directories within it.</para> 19 17 20 18 <para>With Linux distributions, like Red Hat, Debian etc. a possible rule is … … 24 22 <filename>/usr</filename>.</para> 25 23 26 <para> LFS users build their own system and so deciding where the system ends27 and local files begin is not straightforward. So the choice should be 28 made in order to make things easier to administer. There are several24 <para><acronym>LFS</acronym> users build their own system and so deciding where 25 the system ends and local files begin is not straightforward. So the choice 26 should be made in order to make things easier to administer. There are several 29 27 reasons for dividing files between <filename>/usr</filename> and 30 28 <filename>/usr/local</filename>.</para> … … 32 30 <itemizedlist> 33 31 34 <listitem><para>On a network of several machines all running LFS, or mixed 35 LFS and 36 other Linux distributions, <filename>/usr/local</filename> could be used to 37 hold packages 32 <listitem><para>On a network of several machines all running <acronym>LFS 33 </acronym>, or mixed <acronym>LFS</acronym> and other Linux distributions, 34 <filename>/usr/local</filename> could be used to hold packages 38 35 that are common between all the computers in the network. It can be 39 NFS mounted or mirrored from a single server. Here local indicates 40 local to the site.</para></listitem>36 <acronym>NFS</acronym> mounted or mirrored from a single server. Here local 37 indicates local to the site.</para></listitem> 41 38 42 39 <listitem><para>On a network of several computers all running an identical 43 LFS system <filename>/usr/local</filename> could hold packages that44 are different between the machines. In this case local refers to45 t he individual computers.</para></listitem>40 <acronym>LFS</acronym> system <filename>/usr/local</filename> could hold 41 packages that are different between the machines. In this case local refers 42 to the individual computers.</para></listitem> 46 43 47 44 <listitem><para>Even on a single computer <filename>/usr/local</filename> can 48 45 be useful if you have several distributions installed simultaneously, and want 49 a place to put packages that will be the same on all of 50 them.</para></listitem> 46 a place to put packages that will be the same on all of them.</para></listitem> 51 47 52 <listitem><para>Or you might regularly rebuild your LFS, but want 53 a place to put files 54 that you don't want to rebuild each time. This way you can wipe the 55 LFS filesystem and start from a clean partition every time without losing 56 everything.</para></listitem> 48 <listitem><para>Or you might regularly rebuild your <acronym>LFS</acronym>, but 49 want a place to put files that you don't want to rebuild each time. This way 50 you can wipe the <acronym>LFS</acronym> filesystem and start from a clean 51 partition every time without losing everything.</para></listitem> 57 52 58 53 </itemizedlist> 59 54 60 <para>Some people ask why not use your own directory tree, e.g. 61 <filename>/usr/site</filename> rather than 62 <filename>/usr/local</filename>?</para> 55 <para>Some people ask why not use your own directory tree, e.g. <filename> 56 /usr/site</filename> rather than <filename>/usr/local</filename>?</para> 63 57 64 <para>There is nothing stopping you, many sites do make their own trees, however65 it makes installing new software more difficult. Automatic installers58 <para>There is nothing stopping you, many sites do make their own trees, 59 however it makes installing new software more difficult. Automatic installers 66 60 often look for dependencies in <filename>/usr</filename> and 67 61 <filename>/usr/local</filename>, and if the file it is looking 68 62 for is in <filename>/usr/site</filename> instead, the installer will 69 probably fail unless 70 you specifically tell it where to look.</para> 63 probably fail unless you specifically tell it where to look.</para> 71 64 72 <para><emphasis>What is the BLFS position on this?</emphasis></para> 65 <para><emphasis>What is the <acronym>BLFS</acronym> position on this?</emphasis> 66 </para> 73 67 74 <para>All of the BLFSinstructions install programs in68 <para>All of the <acronym>BLFS</acronym> instructions install programs in 75 69 <filename>/usr</filename> unless specifically stated otherwise. There 76 70 are examples where some files are placed in the 77 71 <filename>/usr/local</filename> hierarchy but these are documented and 78 72 are generally for a good reason. These exceptions should be well documented 79 in the book. If you think you have 80 found one which isn't please tell us!</para> 73 in the book. If you think you have found one which isn't please tell us!</para> 81 74 82 75 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.