Also taking f2fs for a spin.
As far as I have experienced (I didn’t measure this): don’t use that partition for container layers. It might just be my system, but f2fs has slowed my container engine down a bit.
Also taking f2fs for a spin.
As far as I have experienced (I didn’t measure this): don’t use that partition for container layers. It might just be my system, but f2fs has slowed my container engine down a bit.
Because exceptions are old and the new (recycled) kids are much more fun to play with? Or people yearn to implement the low level switch-case pattern error matching mechanism all over again, which try-catch-exceptions were solving.
I think there is no moving on from a paradigm as long as it has a function.
Took me a solid second to get it as well.
That you are a magnificent bastard!!
You are correct. I just have a coworker that has ingrained the philosophy in me to always look for a way to put it in configuration, and not in a script that you have to maintain.
I don’t always agree with that. And I find your solution as valid as mine. It is always a matter of taste and trust. In this case in the script, or the fsdriver. That’s why I always quote the “easier” when comparing solutions to Linux problems.
I am no expert. But I think there is an ‘easier’ way too manage this with an overlay filesystem.
Have an immutable base with all permissions set. When a session is started have it be done in an in-memory overlay. On logout drop the overlay.
This might be easier if you don’t want to rely on cronjobs. But as I have no experience myself setting this up… ‘easier’ should be taken with a grain of salt. I just took inspiration from docker.
Totally accepting it is my system being slow. It is a openwrt router after all.