Changeset 4afc2603 for introduction/important/position.xml

Timestamp:

12/29/2005 01:24:51 AM (18 years ago)

Author:

Randy McMurchy <randy@…>

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

Message:

Changes to the Introduction section; standardized the file structure layout, standardized the id tags (except bootscripts) and some minor textual modifications

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@5496 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• introduction/important/position.xml (modified) (2 diffs)

introduction/important/position.xml

@@ -6 +6 @@
 ]>
 
-<sect1 id="intro-important-position">
+<sect1 id="position">
   <?dbhtml filename="position.html"?>
 
@@ -22 +22 @@
   LFS based system.</para>
 
-  <para>In traditional Unix systems, <filename>/usr</filename> usually
-  contains files that come with the system distribution, and the <filename>
-  /usr/local</filename> tree is free for the local administrator to manage.
-  The only really hard and fast rule is that Unix distributions should not
-  touch <filename>/usr/local</filename>, except perhaps to create the basic
-  directories within it.</para>
+  <para>In traditional Unix systems,
+  <filename class='directory'>/usr</filename> usually contains files that come
+  with the system distribution, and the
+  <filename class='directory'>/usr/local</filename> tree is free for the local
+  administrator to manage. The only really hard and fast rule is that Unix
+  distributions should not touch
+  <filename class='directory'>/usr/local</filename>, except perhaps to create
+  the basic directories within it.</para>
 
-  <para>With Linux distributions, like Red Hat, Debian etc. a possible rule is
-  that <filename>/usr</filename> is managed by the distribution's
-  package system and <filename>/usr/local</filename> is not.  This way the
+  <para>With Linux distributions like Red Hat, Debian, etc., a possible rule is
+  that <filename class='directory'>/usr</filename> is managed by the
+  distribution's package system and
+  <filename class='directory'>/usr/local</filename> is not. This way the
   package manager's database knows about every file within
-  <filename>/usr</filename>.</para>
+  <filename class='directory'>/usr</filename>.</para>
 
   <para>LFS users build their own system and so deciding where
   the system ends and local files begin is not straightforward.  So the choice
-  should be made in order to make things easier to administer.  There are several
-  reasons for dividing files between <filename>/usr</filename> and
-  <filename>/usr/local</filename>.</para>
+  should be made in order to make things easier to administer.  There are
+  several reasons for dividing files between
+  <filename class='directory'>/usr</filename> and
+  <filename class='directory'>/usr/local</filename>.</para>
 
   <itemizedlist>
     <listitem>
-      <para>On a network of several machines all running LFS,
-      or mixed LFS and other Linux distributions,
-      <filename>/usr/local</filename> could be used to hold packages
-      that are common between all the computers in the network.  It can be
-      NFS mounted or mirrored from a single server.  Here local
-      indicates local to the site.</para>
+      <para>On a network of several machines all running LFS, or mixed LFS and
+      other Linux distributions,
+      <filename class='directory'>/usr/local</filename> could be used to hold
+      packages that are common between all the computers in the network. It can
+      be NFS mounted or mirrored from a single server. Here local indicates
+      local to the site.</para>
     </listitem>
     <listitem>
       <para>On a network of several computers all running an identical
-      LFS system <filename>/usr/local</filename> could hold
-      packages that are different between the machines.  In this case local refers
-      to the individual computers.</para>
+      LFS system, <filename class='directory'>/usr/local</filename> could hold
+      packages that are different between the machines. In this case local
+      refers to the individual computers.</para>
     </listitem>
     <listitem>
-      <para>Even on a single computer <filename>/usr/local</filename> can
-      be useful if you have several distributions installed simultaneously, and want
+      <para>Even on a single computer,
+      <filename class='directory'>/usr/local</filename> can be useful if you
+      have several distributions installed simultaneously, and want
       a place to put packages that will be the same on all of them.</para>
     </listitem>
     <listitem>
       <para>Or you might regularly rebuild your LFS, but
-      want a place to put files that you don't want to rebuild each time.  This way
-      you can wipe the LFS file system and start from a clean
+      want a place to put files that you don't want to rebuild each time.  This
+      way you can wipe the LFS file system and start from a clean
       partition every time without losing everything.</para>
     </listitem>
   </itemizedlist>
 
-  <para>Some people ask why not use your own directory tree, e.g., <filename>
-  /usr/site</filename>, rather than <filename>/usr/local</filename>?</para>
+  <para>Some people ask why not use your own directory tree, e.g.,
+  <filename class='directory'>/usr/site</filename>, rather than
+  <filename class='directory'>/usr/local</filename>?</para>
 
   <para>There is nothing stopping you, many sites do make their own trees,
   however it makes installing new software more difficult.  Automatic installers
-  often look for dependencies in <filename>/usr</filename> and
-  <filename>/usr/local</filename>, and if the file it is looking
-  for is in <filename>/usr/site</filename> instead, the installer will
-  probably fail unless you specifically tell it where to look.</para>
+  often look for dependencies in
+  <filename class='directory'>/usr</filename> and
+  <filename class='directory'>/usr/local</filename>, and if the file it is
+  looking for is in <filename class='directory'>/usr/site</filename> instead,
+  the installer will probably fail unless you specifically tell it where to
+  look.</para>
 
   <para><emphasis>What is the BLFS position on this?</emphasis></para>
 
   <para>All of the BLFS instructions install programs in
-  <filename>/usr</filename> with optional instructions to install into
-  <filename>/opt</filename> for some specific packages.</para>
+  <filename class='directory'>/usr</filename> with optional instructions to
+  install into <filename class='directory'>/opt</filename> for some specific
+  packages.</para>
 
 </sect1>