Nimbin[12]?Linux From Scratch / Packagemanager-LFS-PackageUser-System / stacks/bootscripts.conf

Packagemanager-LFS-PackageUser-System git · main

Package-user based package manager for LFS/BLFS

lfs blfs package-manager bash · first commit 2026-08-18 · last commit 2026-10-26 (8 days ago) · synced 8 hours ago · upstream: github.com/nimbin2/Packagemanager-LFS-PackageUser-System

Shell 63.7% Markdown 35.8%
git clone https://git.christianimmanuel.de/linux-from-scratch/Packagemanager-LFS-PackageUser-System.gitwget https://git.christianimmanuel.de/linux-from-scratch/Packagemanager-LFS-PackageUser-System/archive/Packagemanager-LFS-PackageUser-System.tar.gz
stacks/bootscripts.conf 3.1 KB · 44 lines raw
# bootscripts.conf -- which blfs-bootscripts target belongs to which package.
#
# A BLFS package installs a daemon.  What makes that daemon start at boot is
# a SEPARATE tarball, blfs-bootscripts, with one `make install-<target>` per
# service.  Nothing connects the two: install a package from a stack and its
# bootscript is simply not there, and the service silently never runs.
#
# The services stack installs a fixed list of targets, which was right on the
# day it was written -- `install-service-dhcpcd WAS MISSING` is still in the
# comment above it.  This file is the list as a MAPPING instead, so `cfg
# bootscripts` can ask the only question that matters: is the package here,
# and is its bootscript not?
#
#   package | proof it is installed | make targets | what those create
#
#   package   what you would install; for the record, nothing looks it up
#   proof     an absolute path (tested with -e) or a command name (looked up
#             on PATH).  Several, comma separated: ANY of them is enough --
#             a daemon that moved between /sbin and /usr/sbin is still that
#             daemon.  `-` means "no package needed"
#   targets   one or more `make` targets in the blfs-bootscripts tree
#   creates   the file those targets write.  Several, comma separated: any
#             one present means the work is done.  This is what makes the
#             step idempotent, and what it checks AFTERWARDS -- a make that
#             prints no error and installs nothing is the failure to catch
#
# A line whose package is not installed is skipped: an init script for
# something that is not there is a symlink in rc?.d that fails at boot.

package        | proof                                      | targets                | creates
dbus           | dbus-daemon,/usr/bin/dbus-daemon           | install-dbus           | /etc/rc.d/init.d/dbus
alsa-utils     | alsactl,/usr/sbin/alsactl                  | install-alsa           | /etc/rc.d/init.d/alsa
bluez          | /usr/libexec/bluetooth/bluetoothd,bluetoothd | install-bluetooth    | /etc/rc.d/init.d/bluetooth
acpid          | acpid,/usr/sbin/acpid                      | install-acpid          | /etc/rc.d/init.d/acpid
fcron          | fcron,/usr/sbin/fcron                      | install-fcron          | /etc/rc.d/init.d/fcron
iptables       | iptables,/usr/sbin/iptables                | install-iptables       | /etc/rc.d/init.d/iptables
openssh        | sshd,/usr/sbin/sshd                        | install-sshd           | /etc/rc.d/init.d/sshd
wpa_supplicant | wpa_supplicant,/sbin/wpa_supplicant        | install-service-wpa    | /lib/services/wpa,/usr/lib/services/wpa
# dhcpcd ships NO service script of its own and BLFS has no init.d/dhcpcd at
# all: /lib/services/dhcpcd is the whole of it, and it runs only because
# /etc/sysconfig/ifconfig.<iface> says SERVICE="dhcpcd" (see below).
dhcpcd         | dhcpcd,/usr/sbin/dhcpcd,/sbin/dhcpcd       | install-service-dhcpcd | /lib/services/dhcpcd,/usr/lib/services/dhcpcd
# the entropy pool is saved and restored by a script that needs no package
-              | -                                          | install-random         | /etc/rc.d/init.d/random