New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 609992 link

Starred by 1 user
Status: WontFix
Owner:
█ printe...@chromium.org
Email to this user bounced
Closed: Jul 19
Cc:
gwendal@chromium.org
vapier@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

udev rules for dev/test packages are not processed

Reported by printe...@chromium.org, May 6 2016 
Because dev/test packages are installed in dev_image and on boot dev_image is mounted at /usr/local, udev rules from such packages end up being located at /usr/local/lib/udev/rules.d.

Udev only reads rules from /etc/udev/rules.d and /lib/udev/rules.d so the rules from such packages (eg. sys-fs/lvm2) are ignored and which may lead to strange/unwanted behavior.

We should find a way to apply udev rules for dev/test packages.

Comment 1 by vapier@chromium.org, May 17 2016

Summary: udev rules for dev/test packages are not processed (was: udev rules for dev/test packages are not installed in the correct location)
they're installed in the right place ... we want everything in /usr/local/.

i don't think there's a way to get udev to read /usr/local w/out patching it.  we could symlink the files either at build_image time or at runtime (into /run/udev/rules.d/) ...

Comment 2 by vapier@chromium.org, Jul 19

Components: -Build Infra>Client>ChromeOS>Build
Status: WontFix (was: Untriaged)
this is largely WAI, albeit a bit surprising

we have a test root package now for files that really need to be in the rootfs

closing out as it doesn't seem to be a big deal, and arguably udev rules shouldn't be different between test & non-test images otherwise it makes our test results less reliable
►

Sign in to add a comment