Summary: | >=sys-fs/udev-183 doesn't copy anything from /lib/udev/devices (since tmpfiles should be used instead) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Łukasz Stelmach <stlman> |
Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
Status: | VERIFIED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Łukasz Stelmach
2011-08-10 09:18:18 UTC
In fact it doesn't copy any files from that directory since udev-156. How about /lib/udev/devices? Does it copy from there? That is the correct place for these files since things in there are not architecture specific. Try putting your named pipes there and let me know if that fixes the issue. $ ls -l /lib lrwxrwxrwx 1 root root 5 05-28 12:30 /lib -> lib64 Nope. Putting anything in /lib/udev/devices doesn't work because no post 151-r4 init-script contains cp -RPp /lib/udev/devices/* /dev 2>/dev/null try grep -r lib/udev/devices /usr/portage/sys-fs/udev/files/1*/*.initd and see yourself. References in 156 and newer are in the stop() function of udev-dev-tarball.init.d. IMHO somebody simply cut too when upgrading to 156. This looks outdated bug. $ ls /lib/udev/devices ls: cannot access /lib/udev/devices: No such file or directory I'm pretty sure this isn't any of problem with >=sys-fs/udev-197-r2 anymore. However, if it is, let us know. (In reply to comment #4) > I'm pretty sure this isn't any of problem with >=sys-fs/udev-197-r2 anymore. > However, if it is, let us know. Verified. Support for /lib/udev/devices stopped in udev-183 and tmpfiles should be used now (OpenRC's tmpfiles, or systemd's tmpfiles) |