10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/mips64el
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
| Line | |
|---|
| 1 | Purpose of rules file:
|
|---|
| 2 |
|
|---|
| 3 | Most of the rules installed by Udev itself create devices with the correct
|
|---|
| 4 | properties. This file contains rules that have not been merged upstream yet.
|
|---|
| 5 |
|
|---|
| 6 | Description of rules:
|
|---|
| 7 |
|
|---|
| 8 | By default, Udev creates device nodes with UID 0, GID 0, and permissions 0660.
|
|---|
| 9 |
|
|---|
| 10 | ISDN-related devices should be owned by the 'dialout' group, hence the following
|
|---|
| 11 | rule (and similar):
|
|---|
| 12 |
|
|---|
| 13 | KERNEL=="ippp[0-9]*", GROUP="dialout"
|
|---|
| 14 |
|
|---|
| 15 | The RTC-related rules cause the setclock bootscript to be run as soon as the
|
|---|
| 16 | RTC device has been created by Udev, meaning that times in log files, for
|
|---|
| 17 | example, are as accurate as possible as quickly as possible.
|
|---|
| 18 |
|
|---|
| 19 | A final word of caution: Any particular rule must be written on one line, and a
|
|---|
| 20 | comma must separate each part of the rule.
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
