Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

udev rules files installed in /etc/udev/rules.d should follow systemd naming convention

Description

Udev rules files are sorted and processed in lexical order.

When looking at standard rules, we see:

# ls /lib/udev/rules.d 50-firmware.rules 50-udev-default.rules 60-block.rules 60-cdrom_id.rules 60-drm.rules ... 90-vconsole.rules 97-hid2hci.rules 99-systemd.rules

But in /etc/udev/rules.d, there are some files without any prefix:

# ls /etc/udev/rules.d 72-pvr-seat.rules automount.rules lightmediascanner.rules touchscreen.rules udev-smack-default.rules

This leads to unexpected behaviour regarding rules priorities and precedence. The files should have a 2 character prefix to specify priority.

Environment

None

Activity

Show:

Walt Miner 
July 18, 2017 at 1:29 PM

can this now be resolved?

Jan-Simon Moeller 
May 25, 2017 at 8:31 PM

What else is missing ...  is this one solved ?

udev-smack-default.rules

 

Who owns

touchscreen.rules ?

Matt Ranostay 
May 1, 2017 at 1:37 AM

My items automount.sh and lightmediascanner.sh have been merged. Should this bug be assigned to whoever owns the remaining changes?

Stephane Desneux 
April 18, 2017 at 3:01 PM

BTW, naming udev rules 'udev-*' is a bit overkill as they're installed in /etc/udev/rules.d slightly smiling face

So for smack rules, naming them G0-smack-defauilt.rules should be ok (with G0 or any appropriate prefix after system rules where the last ones start with '99-'). Note that some rules packaged with filenames as 'ZZ-*' are to be processed at the end. But this is just a per-distro convention AFAIK.

Jose Bollo 
April 18, 2017 at 11:29 AM

udev-smack-default.rules   comes from   meta-intel-iot-security

So yes

 

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Affects versions

Priority

Created April 14, 2017 at 3:52 PM
Updated July 24, 2017 at 11:45 PM
Resolved July 18, 2017 at 1:58 PM

Flag notifications