Files
systemd/hwdb.d
Zbigniew Jędrzejewski-Szmek 9282a85ed7 hwdb: say that settings can be also set to 0
We recommend that users create overriddes. This creates the problem that there
is no syntax to unset a property. Thus, the user needs to just set the property
to "something else" in the override file. But then the blurb saying that
"VAR=1" (or "VAR=0" in some cases) is the only allowed value can be confusing.
Say that both 0 and 1 can be set, since this documentation is also intended
for end users.

In our files, we generally don't want the override values anywhere. But we
have a test which checks the rvalue, which should be enough.
2025-05-14 18:08:26 +02:00
..
2024-11-15 17:17:47 +00:00
2024-12-10 15:18:39 +00:00
2024-12-10 15:18:39 +00:00
2024-11-27 15:17:23 +00:00
2023-11-14 21:20:45 +00:00
2024-12-10 15:18:39 +00:00
2024-07-03 13:51:52 +02:00
2024-11-01 12:32:06 +00:00
2024-12-10 15:18:39 +00:00
2024-12-10 15:18:39 +00:00
2024-12-10 15:18:39 +00:00
2025-05-13 08:09:55 -05:00
2024-11-27 15:17:23 +00:00
2024-11-15 17:17:47 +00:00
2024-12-10 15:18:39 +00:00

Files in this directory specify a description of hardware devices, in the form
of mappings from modalias-like keys (which identify specific hardware devices)
to udev properties.

Files in this directory are not read by udev directly. Instead,
man:systemd-hwdb(8) compiles them into a binary database.

See man:hwdb(7) for an overview of the configuration file format, and
man:systemd-udevd.service(8) for a description of the udev daemon.

Use 'systemd-analyze cat-config udev/hwdb.d' to display the effective config.