mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* lock path in barebox-state
@ 2021-02-10  8:36 barebox+mailing
  2021-02-10  8:51 ` Rouven Czerwinski
  0 siblings, 1 reply; 4+ messages in thread
From: barebox+mailing @ 2021-02-10  8:36 UTC (permalink / raw)
  To: barebox

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-02-10  9:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-10  8:36 lock path in barebox-state barebox+mailing
2021-02-10  8:51 ` Rouven Czerwinski
2021-02-10  8:59   ` Ahmad Fatoum
2021-02-10  9:04     ` barebox+mailing

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox