1a8cd5ff9d
Initially, we were creating tmpfiles entries in the sysinit runlevel and again in the boot runlevel. Systemd runs the --create and --remove options in one service called systemd-tmpfiles-setup after the local file systems are mounted. Now we have a service called tmpfiles.setup which emulates this. This also closes the bug mentioned below, since we were originally writing to files that were on read-only file systems and that were not available. Reported-by: <devurandom@gmx.net> X-Gentoo-Bug: 439012 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=439012
27 lines
525 B
Makefile
27 lines
525 B
Makefile
DIR= ${CONFDIR}
|
|
CONF= bootmisc fsck hostname localmount netmount urandom tmpfiles \
|
|
${CONF-${OS}}
|
|
|
|
ifeq (${MKNET},)
|
|
CONF+= network staticroute
|
|
TARGETS+= network staticroute
|
|
CLEANFILES+= network staticroute
|
|
endif
|
|
|
|
MK= ../mk
|
|
include ${MK}/os.mk
|
|
|
|
CONF-FreeBSD= ipfw moused powerd rarpd savecore syscons
|
|
|
|
CONF-Linux= consolefont dmesg hwclock keymaps killprocs modules
|
|
|
|
CONF-NetBSD= moused rarpd savecore
|
|
|
|
include ${MK}/scripts.mk
|
|
|
|
network: network.in network${SFX}
|
|
cat $^ > $@
|
|
|
|
staticroute: staticroute${SFX}
|
|
cp $@${SFX} $@
|