History log of /systemd/units/initrd-parse-etc.service.in
Revision Date Author Comments Expand
f3b8fbb1da6519e14985ea444f8304673d20ad3f 03-Sep-2014 Harald Hoyer <harald@redhat.com>

initrd-parse-etc.service: ignore return code of daemon-reload It seems the return code of systemctl daemon-reload can be !=0 in some circumstances, which causes a failure of the unit and breaks booting in the initrd.

d420282b28f50720e233ccb1c02547c562195653 26-Nov-2013 Lennart Poettering <lennart@poettering.net>

core: replace OnFailureIsolate= setting by a more generic OnFailureJobMode= setting and make use of it where applicable

9e5f0f92915b777308797294c6e103e430957b5d 15-Mar-2013 Harald Hoyer <harald@redhat.com>

Make initrd.target the default target in the initrd First, rename root-fs.target to initrd-root-fs.target to clarify its usage. Mount units with "x-initrd-rootfs.mount" are now ordered before initrd-root-fs.target. As we sometimes construct /sysroot mounts in /etc/fstab in the initrd, we want these to be mounted before the initrd-root-fs.target is active. initrd.target can be the default target in the initrd. (normal startup) : : v basic.target | ______________________/| / | | sysroot.mount | | | v | initrd-root-fs.target | | | v | initrd-parse-etc.service (custom initrd services) | | v | (sysroot-usr.mount and | various mounts marked | with fstab option | x-initrd.mount) | | | v | initrd-fs.target | | \______________________ | \| v initrd.target | v initrd-cleanup.service isolates to initrd-switch-root.target | v ______________________/| / | | initrd-udevadm-cleanup-db.service | | (custom initrd services) | | | \______________________ | \| v initrd-switch-root.target | v initrd-switch-root.service | v switch-root

700e07ffd53083114e91bb4ba646ed26d0463f67 13-Mar-2013 Harald Hoyer <harald@redhat.com>

add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.

7b40ce553f0ec9487077e53f5bdc46580025901c 09-Mar-2013 Michael Biebl <biebl@debian.org>

build-sys: don't hard-code binary paths in initrd-*.service Instead use @bindir@ for udevadm and @rootbindir@ for systemctl.