From 33488f19793dc0a86fdee27266c5319b5b78d695 Mon Sep 17 00:00:00 2001 From: Martin Pitt Date: Fri, 17 Oct 2014 15:01:01 +0200 Subject: udev hwdb: Support shipping pre-compiled database in system images In some cases it is preferable to ship system images with a pre-generated binary hwdb database, to avoid having to build it at runtime, avoid shipping the source hwdb files, or avoid storing large binary files in /etc. So if hwdb.bin does not exist in /etc/udev/, fall back to looking for it in UDEVLIBEXECDIR. This keeps the possibility to add files to /etc/udev/hwdb.d/ and re-generating the database which trumps the one in /usr/lib. Add a new --usr flag to "udevadm hwdb --update" which puts the database into UDEVLIBEXECDIR. Adjust systemd-udev-hwdb-update.service to not generate the file in /etc if we already have it in /usr. --- man/udev.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'man/udev.xml') diff --git a/man/udev.xml b/man/udev.xml index d77cbb0e6e..87c16c78ee 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -766,7 +766,9 @@ The content of all hwdb files is read by udevadm8 - and compiled to a binary database located at /etc/udev/hwdb.bin. + and compiled to a binary database located at /etc/udev/hwdb.bin, + or alternatively /usr/lib/udev/hwdb.bin if you want ship the compiled + database in an immutable image. During runtime only the binary database is used. -- cgit v1.2.3-54-g00ecf