> That looks pretty different from the above output. Yeah, that's weird. And after a restart, "udevadm info ..." actually shows:
P: /devices/virtual/net/eth0 E: DEVPATH=/devices/virtual/net/eth0 E: ID_NET_NAME_MAC=enx00163e05244e E: ID_OUI_FROM_DATABASE=Xensource, Inc. E: IFINDEX=39 E: INTERFACE=eth0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0 E: TAGS=:systemd: E: USEC_INITIALIZED=212063155183 (But systemd continues to wait for sys-subsystem-net-devices-eth0.device unsuccessfully). ? If you run: > udevadm trigger --action=add > does the above > udevadm info > output change? Running "udevadm trigger --action=add" does not appear to change either the output of the "info" command nor does it result in the dependency working. The complete log output after running "systemctl start dhcpcd@eth0" is: Jan 24 09:54:24 arcadia systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device... Jan 24 09:55:54 arcadia systemd[1]: Job sys-subsystem-net-devices-eth0.device/start timed out. Jan 24 09:55:54 arcadia systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device. Jan 24 09:55:54 arcadia systemd[1]: Dependency failed for dhcpcd on eth0. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
