source: introduction/important/bootscripts.xml@ a7e0ec7

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
   "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../../general.ent">
  %general-entities;
]>

<sect1 id="intro-important-bootscripts" xreflabel="blfs-bootscripts-&blfs-bootscripts-version;">
  <?dbhtml filename="bootscripts.html"?>

  <sect1info>
    <othername>$LastChangedBy$</othername>
    <date>$Date$</date>
  </sect1info>

  <title>BLFS Boot Scripts</title>

  <indexterm zone="intro-important-bootscripts">
    <primary sortas="a-BLFS-Bootscripts">BLFS Bootscripts</primary>
  </indexterm>

  <indexterm zone="intro-important-bootscripts">
    <primary sortas="f-AA-General-Information">General Information</primary>
  </indexterm>

  <para>The BLFS Bootscripts package contains the init
  scripts that are used throughout the book. It is assumed that you will be
  using the blfs-bootscripts package in conjuction with a compatible
  lfs-bootscripts package. Refer to
  <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more
  information on the lfs-bootscripts package.</para>

  <itemizedlist spacing='compact'>
    <title>Package Information</title>
    <listitem>
      <para>Download: <ulink url="&blfs-bootscripts-download;"/></para>
    </listitem>
  </itemizedlist>

  <para>The blfs-bootscripts package will be used throughout the BLFS book
  for startup scripts.  Unlike LFS, each init script has a separate install target
  in the blfs-bootscripts package. It is recomended you keep the package source
  directory around until completion of your BLFS system. When a script is
  requested from blfs-bootscripts, simply change to the directory and as the
  <systemitem class="username">root</systemitem> user, execute the given
  <command>make install-<replaceable>[init-script]</replaceable></command>
  command. This command installs the init script to its proper location (along
  with any auxillary configuration scripts) and also creates the appropriate
  symlinks to start and stop the service at the appropriate run-level.</para>

  <note>
    <para>It is advisable to peruse each bootscript before installation to
    ascertain that it satisfies your need. Also verify that the start and stop
    symlinks it creates match your preferences.</para>
  </note>

</sect1>