I think it started to happen after upgrading from systemd-206. ~~~~~ { "__CURSOR" : "s=8f818ef0bf1643df9cc6ae78169e6482;i=bf02;b=102b19bf43a144f68b836131498a7482;m=e5bfef;t=4e66f912a189d;x=fe38bbfc27606ab9", "__REALTIME_TIMESTAMP" : "1379266758056093", "__MONOTONIC_TIMESTAMP" : "15056879", "_BOOT_ID" : "102b19bf43a144f68b836131498a7482", "_UID" : "0", "_GID" : "0", "_MACHINE_ID" : "77663d77fe2b88049d5e1d2800000024", "_HOSTNAME" : "kirNote", "SYSLOG_FACILITY" : "3", "SYSLOG_IDENTIFIER" : "systemd", "_TRANSPORT" : "journal", "_CAP_EFFECTIVE" : "1fffffffff", "PRIORITY" : "3", "CODE_FILE" : "/var/tmp/portage/sys-apps/systemd-207/work/systemd-207/src/core/execute.c", "CODE_LINE" : "1545", "CODE_FUNCTION" : "exec_spawn", "MESSAGE_ID" : "641257651c1b4ec9a8624d7a40a9e1e7", "EXECUTABLE" : "/bin/udevadm", "MESSAGE" : "Failed at step EXEC spawning /bin/udevadm: No such file or directory", "ERRNO" : "2", "_PID" : "2142", "_COMM" : "(udevadm)", "_SYSTEMD_CGROUP" : "/", "_SOURCE_REALTIME_TIMESTAMP" : "1379266758055719" } { "__CURSOR" : "s=8f818ef0bf1643df9cc6ae78169e6482;i=bf03;b=102b19bf43a144f68b836131498a7482;m=e5cc7a;t=4e66f912a2528;x=2ab8b8fb23451569", "__REALTIME_TIMESTAMP" : "1379266758059304", "__MONOTONIC_TIMESTAMP" : "15060090", "_BOOT_ID" : "102b19bf43a144f68b836131498a7482", "_UID" : "0", "_GID" : "0", "_MACHINE_ID" : "77663d77fe2b88049d5e1d2800000024", "_HOSTNAME" : "kirNote", "SYSLOG_FACILITY" : "3", "SYSLOG_IDENTIFIER" : "systemd", "_TRANSPORT" : "journal", "_CAP_EFFECTIVE" : "1fffffffff", "PRIORITY" : "3", "CODE_FILE" : "/var/tmp/portage/sys-apps/systemd-207/work/systemd-207/src/core/execute.c", "CODE_LINE" : "1545", "CODE_FUNCTION" : "exec_spawn", "MESSAGE_ID" : "641257651c1b4ec9a8624d7a40a9e1e7", "EXECUTABLE" : "/bin/udevadm", "MESSAGE" : "Failed at step EXEC spawning /bin/udevadm: No such file or directory", "ERRNO" : "2", "_COMM" : "(udevadm)", "_SYSTEMD_CGROUP" : "/", "_PID" : "2144", "_SOURCE_REALTIME_TIMESTAMP" : "1379266758058704" } ~~~~~ `/bin/udevadm` mentioned in `/lib/systemd/system/plymouth-start.service` does not exist.
It seems that udev-207/systemd-207 don't build udevadm at all anymore. It's not getting installed (fresh install): machine@user # /etc/init.d/udev --nodeps restart udev | * Unable to find udev executable.
(In reply to Mattia Rossi from comment #1) > It seems that udev-207/systemd-207 don't build udevadm at all anymore. It's > not getting installed (fresh install): > > machine@user # /etc/init.d/udev --nodeps restart > udev | * Unable to find udev executable. Ok, Have to correct that here: sys-fs/udev-207 doesn't install udevadm, systemd-207 does.
@Kirill: do you have udevadm installed? Can you share where is it? Under /usr/bin maybe? Best would be if you can share the output of which -a udevadm Thanks
Created attachment 359538 [details] plymouth ebuild moving everything to /usr Ok, sorry for the noise. iamben on IRC told me udevadm has been moved to /usr/bin with systemd 207, and I was not aware of that. This ebuild should fix the issue, but I would appreciate some feedback from users running both systemd 207 and plain udev 207 and possible also eudev users just to be sure it is going to work for everyone.
Actually, I've changed the path after filing this bugreport and it's been working fine since then. As a sidenote, even with `--with-system-root-install=no` .service files are installed to /lib/systemd/system instead of /usr/lib/systemd/system…
(In reply to Kirill Elagin from comment #5) > Actually, I've changed the path after filing this bugreport and it's been > working fine since then. > > As a sidenote, even with `--with-system-root-install=no` .service files are > installed to /lib/systemd/system instead of /usr/lib/systemd/system… Well then it moves everything except systemd units. Hopefully upstream will fix this in the next release. For now it works with units there so, that's fine. I would still like some feedback from someone not using systemd if possible. Thanks
Ok I guess I should give up and have this bumped. If this is going to break other udevs we will discover soon, but I'm confident it will not happen. Maxim when you have a chance bump the ebuild I attached. It requires a revbump since it changes installed files. Thank you
Ok anybody else from proxy-maint can bump this please? Thank you
+*plymouth-0.8.8-r2 (11 Oct 2013) + + 11 Oct 2013; Pacho Ramos <pacho@gentoo.org> +plymouth-0.8.8-r2.ebuild: + Move things to /usr (#485034 by Kirill Elagin and fix by Enrico Tagliavini), + this also causes to rhgb-compat-link to be dropped due it pointing to old + location, use readme.gentoo.eclass, move to eapi5, move the openrc vs systemd + blocker behind 'systemd' USE flag to prevent people enabling it globally from + getting systemd blocked. +
