#162 Issue closed: Fedora18: udevd replaced by systemd-udevd¶
Labels: enhancement, waiting for info
gdha opened issue at 2012-09-20 13:00:¶
Status rear-1.14: boots on fedora18 Alpha (Sept. 2012), however, no
network available because the following executables
/usr/lib/systemd/systemd-udevd and /usr/lib/systemd/systemd-journald
are missing in the rear boot image. And, of course, also the required
systemd config/service files are missing.
This is a place holder to fix this in the next couple of weeks.
gdha commented at 2012-11-06 12:35:¶
Pushed the required updates. Still needs some serious testing. Will keep it open 'till Fedora18 is official released as systemd might undergo some changes under way (like with fedora17).
gdha commented at 2012-11-15 11:25:¶
OpenSuse also works with the latest modifications.
gdha commented at 2012-11-19 10:37:¶
latest modifications in issue #162 and #167 do not break Fedora 17,
OpenSuse 12.x and Arch. Keep fingers crossed.
All feedback is welcome.
gdha commented at 2013-01-21 12:28:¶
Tests on Fedora 18 reveals the following:
[ 284.774238] systemd[1]: Failed to start udev Kernel Device Manager.
[ 284.774257] systemd[1]: Unit udev.service entered failed state
[ 284.774314] systemd[1]: udev.service changed failed -> auto-restart
[ 284.774325] systemd[1]: Incoming traffic on udev-kernel.socket
[ 284.774331] systemd[1]: udev-kernel.socket changed listening -> running
[ 284.774335] systemd[1]: Incoming traffic on udev-control.socket
[ 284.774338] systemd[1]: udev-control.socket changed listening -> running
[ 284.776864] systemd[1]: Accepted connection on private bus.
[ 284.778840] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 284.778908] systemd[1]: udev.service: cgroup is empty
[ 284.778957] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 284.874343] systemd[1]: udev.service holdoff time over, scheduling restart.
[ 284.874353] systemd[1]: Trying to enqueue job udev.service/restart/fail
[ 284.874382] systemd[1]: Installed new job udev.service/restart as 11608596
[ 284.874399] systemd[1]: Enqueued job udev.service/restart as 11608596
[ 284.874404] systemd[1]: udev.service scheduled restart job.
[ 284.874423] systemd[1]: Stopping udev Kernel Device Manager...
[ 284.874449] systemd[1]: udev-kernel.socket got notified about service death (failed permanently: no)
[ 284.874460] systemd[1]: udev-kernel.socket changed running -> listening
[ 284.874470] systemd[1]: udev-control.socket got notified about service death (failed permanently: no)
[ 284.874478] systemd[1]: udev-control.socket changed running -> listening
[ 284.874484] systemd[1]: udev.service changed auto-restart -> dead
[ 284.874557] systemd[1]: Job udev.service/restart finished, result=done
[ 284.874565] systemd[1]: Converting job udev.service/restart -> udev.service/start
[ 284.874707] systemd[1]: Starting udev Kernel Device Manager...
[ 284.874771] systemd[1]: About to execute /sbin/udevd
[ 284.875228] systemd[1]: Forked /sbin/udevd as 652
[ 284.875544] systemd[1]: udev.service changed dead -> start
[ 284.875559] systemd[1]: Incoming traffic on udev-kernel.socket
[ 284.875703] systemd[1]: udev-kernel.socket changed listening -> running
[ 284.875718] systemd[1]: Incoming traffic on udev-control.socket
[ 284.875740] systemd[1]: udev-control.socket changed listening -> running
[ 284.876470] systemd[652]: Failed at step EXEC spawning /sbin/udevd: No such file or directory
[ 284.876978] systemd[1]: Received SIGCHLD from PID 652 ((udevd)).
[ 284.877016] systemd[1]: Got SIGCHLD for process 652 ((udevd))
[ 284.877064] systemd[1]: Child 652 died (code=exited, status=203/EXEC)
[ 284.877068] systemd[1]: Child 652 belongs to udev.service
[ 284.877077] systemd[1]: udev.service: main process exited, code=exited, status=203/EXEC
[ 284.877272] systemd[1]: udev-kernel.socket got notified about service death (failed permanently: no)
[ 284.877281] systemd[1]: udev-kernel.socket changed running -> listening
[ 284.877290] systemd[1]: udev-control.socket got notified about service death (failed permanently: no)
[ 284.877297] systemd[1]: udev-control.socket changed running -> listening
[ 284.877303] systemd[1]: udev.service changed start -> failed
[ 284.877415] systemd[1]: Job udev.service/start finished, result=failed
[ 284.877429] systemd[1]: Failed to start udev Kernel Device Manager.
[ 284.877445] systemd[1]: Unit udev.service entered failed state
[ 284.877503] systemd[1]: udev.service changed failed -> auto-restart
[ 284.877516] systemd[1]: Incoming traffic on udev-kernel.socket
[ 284.877523] systemd[1]: udev-kernel.socket changed listening -> running
[ 284.877530] systemd[1]: Incoming traffic on udev-control.socket
[ 284.877536] systemd[1]: udev-control.socket changed listening -> running
in short the obsolete udev systemd rules (of previous Fedora distros) are trying to start in Fedora 18 too, but returns too many errors (is harmless, but very annoying). Somehow, must remove the older udev services from Fedora 16, 17 concerning udev.
gdha commented at 2013-01-25 12:39:¶
commit https://github.com/rear/rear/commit/cb1208d56dd25de70a7dd61f9ffd185eeeaf09d1 resolved the annoying messages.
[Export of Github issue for rear/rear.]