Skip to contentSkip to conversation

lock path in barebox-state

DISCUSSION [email protected] 3 participants 4 messages Feb 10, 2021

lore
Share & tools
lore
#0 lore 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
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox

#1 lore raw

Hi Marcel

Quoted 7 lines · On Wed, 2021-02-10 at 09:36 +0100, [email protected] 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

Quoted 7 lines

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 [email protected] Feel free to send patches changing the locking directory to this address as well.

Regards,
Rouven Czerwinski

_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox

#2 lore raw
Quoted 14 lines · Rouven Czerwinski

Hi Marcel

Quoted 11 lines · On Wed, 2021-02-10 at 09:36 +0100, [email protected] 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.

Quoted 7 lines
Quoted 3 lines

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 [email protected] Feel free to send patches changing the locking directory to this address as well.

There's already a patch for that:
https://www.mail-archive.com/[email protected]/msg00063.html

Quoted 10 lines

Regards,
Rouven Czerwinski

_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox

Signature · 9 lines
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
#3 lore raw

Hey both of you,

Quoted 1 line

Since barebox-state is part of the dt-utils software suite, questions

should be directed to [email protected]

Sorry for that, but thanks for the hint!

Quoted 2 lines

There's already a patch for that:
https://www.mail-archive.com/[email protected]/msg00063.html

Wow, I haven't found it (maybe because I looked at the wrong mailing list (: )

I will ask both of my questions there again.

Greetings,
Marcel

_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox