Changeset 919683dc for introduction/important
- Timestamp:
- 07/30/2005 06:14:25 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:
- bfb7882
- Parents:
- a05dbe6
- Location:
- introduction/important
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/bootscripts.xml
ra05dbe6 r919683dc 26 26 <para>The BLFS Bootscripts package contains the init 27 27 scripts that are used throughout the book. It is assumed that you will be 28 using the BLFS Bootscripts package in conju ction with a compatible28 using the BLFS Bootscripts package in conjunction with a compatible 29 29 LFS-Bootscripts package. Refer to 30 30 <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more … … 40 40 <para>The BLFS Bootscripts package will be used throughout the BLFS book 41 41 for startup scripts. Unlike LFS, each init script has a separate install target 42 in the BLFS Bootscripts package. It is recom ended you keep the package source42 in the BLFS Bootscripts package. It is recommended you keep the package source 43 43 directory around until completion of your BLFS system. When a script is 44 44 requested from BLFS Bootscripts, simply change to the directory and as the … … 46 46 <command>make install-<replaceable>[init-script]</replaceable></command> 47 47 command. This command installs the init script to its proper location (along 48 with any auxil lary configuration scripts) and also creates the appropriate48 with any auxiliary 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/pkgmgt.xml
ra05dbe6 r919683dc 36 36 <listitem> 37 37 <para>There are multiple solutions for package management, each having 38 its strengths and drawbacks. Including one that sati fies all audiences is38 its strengths and drawbacks. Including one that satisfies all audiences is 39 39 difficult.</para> 40 40 </listitem> … … 58 58 (<application>Glibc</application>, <application>GCC</application> or 59 59 <application>Binutils</application>) needs to be upgraded to a newer 60 minor ve sion, it is safer to rebuild LFS. Though you60 minor version, it is safer to rebuild LFS. Though you 61 61 <emphasis>may</emphasis> be able to get by rebuilding all the packages 62 62 in their dependency order, we do not recommend it. For example, if … … 200 200 <command>install</command>, <command>mv</command> and tracking the system 201 201 calls that modify the filesystem. For this approach to work, all the executables 202 need to be dy manically linked without the suid or sgid bit. Preloading the202 need to be dynamically linked without the suid or sgid bit. Preloading the 203 203 library may cause some unwanted side-effects during installation. Therefore, 204 204 do perform some tests to ensure that the package manager does not break -
introduction/important/unpacking.xml
ra05dbe6 r919683dc 42 42 43 43 <para>The golden rule of Unix System Administration is to use your 44 superpowers only when nec cessary. Hence, BLFS recommends that you44 superpowers only when necessary. Hence, BLFS recommends that you 45 45 build software as an unprivileged user and only become the 46 46 <systemitem class='username'>root</systemitem> user when installing the
Note:
See TracChangeset
for help on using the changeset viewer.