Xi Ruoyao 58ad7bcaa6 bluez: for systemd, create /var/lib/bluetooth at installation ... In the systemd unit file of bluez-5.64, there is: ProtectSystem=full ReadWritePaths=/var/lib/bluetooth The combination of these two options make systemd to bind mount / recursively and read-only to /run/systemd/unit-root in a new mount namespace, then bind mount /var/lib/bluetooth to /run/systemd/unit-root/var/lib/bluetooth, then run bluez in the chroot at /run/systemd/unit-root in the separate namespace. This helps to reduce the potential damage if a bluez security vulnerability is exposed. But, if /var/lib/bluetooth does not exist, systemd will fail to bind mount it and complain: bluetooth.service: bluetooth.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/bluetooth: No such file or directory As a simple workaround, just create this directory at installation. A more elegant solution will be shipped in bluez-5.65: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=0905a06 Q: Why -m700? A: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=edc69d2		2022-07-15 23:59:17 +08:00
..
genlib	Package Updates:	2022-07-13 19:46:02 -05:00
genutils	Package updates:	2022-07-13 21:43:31 -05:00
graphlib	ffmpeg5 update: Fix building gegl with ffmpeg-5.x.	2022-07-11 21:22:19 -05:00
prog	Spelling	2022-07-14 17:14:20 -05:00
sysutils	bluez: for systemd, create /var/lib/bluetooth at installation	2022-07-15 23:59:17 +08:00
general.xml	more SVN prop clean up	2021-04-20 19:12:02 +08:00