source: introduction/important/bootscripts.xml@ 3b96a20

10.0 10.1 11.0 11.1 11.2 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 krejzi/svn lazarus nosym perl-modules plabs/python-mods qt5new systemd-11177 systemd-13485 trunk upgradedb v5_1 xry111/intltool xry111/soup3 xry111/test-20220226
Last change on this file since 3b96a20 was 3b96a20, checked in by Igor Živković <igor@…>, 19 years ago

fixed lfs-bootscripts link

git-svn-id: svn:// af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 1.8 KB
1<sect1 id="intro-important-bootscripts" xreflabel="blfs-bootscripts-&blfs-bootscripts-version;">
2<?dbhtml filename="bootscripts.html"?>
3<title><acronym>BLFS</acronym> Boot Scripts</title>
5<para>The <acronym>BLFS</acronym> Bootscripts package contains the init scripts that are
6used throughout the book. It is assumed that you will be using the blfs-bootscripts
7package in conjuction with a compatible lfs-bootscripts package.
8Refer to
9<ulink url=""/>
11Change the above URL to LFS-testing branch after the 5.1 release.
12<ulink url="&lfs-root;/testing/chapter07/bootscripts.html"/>
14for more
15information on the lfs-bootscripts package.</para>
18<itemizedlist spacing='compact'>
19<title>Package information</title>
20<listitem><para>Download: <ulink url="&blfs-bootscripts-download;"/></para></listitem>
24<para>The blfs-bootscripts package will be used throughout the <acronym>BLFS</acronym>
25book for startup scripts. Unlike <acronym>LFS</acronym>, each init script
26has a separate install target in the blfs-bootscripts package.
27It is recomended you keep the package
28source directory around until completion of your
29<acronym>BLFS</acronym> system. When a script is requested from
30blfs-bootscripts, simply change to the directory and execute the given
31<command>make install-&lt;init-script&gt;</command> command. This command installs the
32init script to its proper location (along with any auxillary configuration
33scripts) and also creates the appropriate symlinks to start and stop the
34service at the appropriate run-level.</para>
36<note><para>It is advisable to peruse each bootscript before installation to
37ascertain that it satisfies your need. Also verify that the start and stop
38symlinks it creates match your preferences.</para></note>
Note: See TracBrowser for help on using the repository browser.