lock path in barebox-state
r.czerwinski at pengutronix.de
Wed Feb 10 03:51:36 EST 2021
On Wed, 2021-02-10 at 09:36 +0100, barebox+mailing at cookiesoft.de wrote:
> Hey everyone,
> we use barebox-state in conjunction with systemd on our platform.
> We removed all legacy programs and paths (in systemd terms), so is `/var/lock` removed as well.
> Lennart Poettering decribed it in a github issue why /var/lock is bad (and the reason why it's not pupolated per default): https://github.com/systemd/systemd/issues/15668#issuecomment-623069821
> So for now our option is to create /var/lock via tmpfiles so barebox-state can use them.
> I would like to see a upstream fix for this, where barebox uses its own directory, e.g. `/run/barebox/lock` or similar.
> I'm not sure if this breaks anything on older systems, maybe you can think about it for a second.
> Please let me know what you think the best approach would be.
Since barebox-state is part of the dt-utils software suite, questions
should be directed to oss-tools at pengutronix.de Feel free to send
patches changing the locking directory to this address as well.
More information about the barebox