Summary: | sys-fs/eudev conflicts with kmod static-nodes tmpfiles creation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
Component: | Current packages | Assignee: | eudev team <eudev> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | qnikst |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=477856 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Samuli Suominen (RETIRED)
2013-07-23 10:37:10 UTC
This has been address. Take a look at https://github.com/gentoo/eudev/commit/aa417a4d83999f6d7f092161d5c411b8cbce9977 I'll be testing it with eudev-9999 (which I still need to dep on >=kmod-14) and then I'll push out eudev-1.2. I actually reverted blueness' commit, because there is no conflict in a proper configuration: #1 - kmod+tmpfiles must be executed before udevd starts, no matter what flavour of udev is being used. #2 - sys-fs/eudev (and older sys-fs/udev for that matter) only create static devnodes if they don't already exist. Otherwise they just silently update mtime and do nothing. Because of #1 , this means eudev will not conflict with kmod+tmpfiles operation The fact that sys-fs/eudev will create static nodes if a user chooses not to include the kmod+tmpfiles commands in openrc (or their favourite rc system) is desired behaviour for our package and not something we want to disable just because systemd decided to. Once kmod+tmpfiles starts in sysinit, prior to udev-init-scripts, there will be no conflict. |