Re: [OE-core] [PATCH V4 1/2] bluez5: change configuration directory mode

2022-10-07 Thread Ming Liu
Hi, Ross: I think it applies for both systemd and sysvinit, it's bluez5's requirement that /etc/bluetooth should be read-only. //Ming Liu Ross Burton 於 2022年10月6日 週四 下午2:19寫道: > Is this in a build with systemd or sysvinit? Looking at the referenced > commit, that’s when running in a

Re: [OE-core] [PATCH V4 1/2] bluez5: change configuration directory mode

2022-10-06 Thread Ross Burton
Is this in a build with systemd or sysvinit? Looking at the referenced commit, that’s when running in a systemd-managed contained environment. In sysv that isn’t the case, so I’m not convinced this is the correct solution. Ross > On 6 Oct 2022, at 12:27, Ming Liu via lists.openembedded.org

[OE-core] [PATCH V4 1/2] bluez5: change configuration directory mode

2022-10-06 Thread Ming Liu
From: Ming Liu Change configuration directory mode from 0755 to 0555, this fixes a following warning when bluetoothd starts: | ConfigurationDirectory 'bluetooth' already exists but the mode is different. | (File system: 755 ConfigurationDirectoryMode: 555) Reference: