From: barebox+mailing@cookiesoft.de
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: lock path in barebox-state
Date: Wed, 10 Feb 2021 09:36:29 +0100 (CET) [thread overview]
Message-ID: <315301163.215482.1612946189188@office.mailbox.org> (raw)
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.
Greetings,
Marcel
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2021-02-10 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 8:36 barebox+mailing [this message]
2021-02-10 8:51 ` Rouven Czerwinski
2021-02-10 8:59 ` Ahmad Fatoum
2021-02-10 9:04 ` barebox+mailing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=315301163.215482.1612946189188@office.mailbox.org \
--to=barebox+mailing@cookiesoft.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox