Always happy to help a brother out.

Same for cameras, axes and chainsaws…

Relevant bash manpage section here.

I wasn’t sure, so I tested this. Turns out, only a.txt would be deleted and removal of b.txt fails due to lack of permissions.

It is indeed.

For those unaware: sudo !! if your previous command failed because you forgot sudo.

Lustra - Scotty doesn’t know.

Looks fade, intelligence & character lasts.

I guess it’s implied, but he doesn’t have a solution because for him it’s not a problem, it’s the intended result.

Looks like a very fine dog. <3 Recent loss? I wish you all the best. I don’t want to begin imagining the pain of losing your doggo…

A snuggle, apparently.

And I’m not actually a sloth.

Well, I still have cheese, sooo…

Crap, I was hoping to invent file systems.

Have they ever not been?

Yeah, and we could give that huge file some kind of internal and logical structure to find those chunks, maybe something hierarchical with human readable names!

Yes, that’s what I meant, thanks for the clarification.

Genius!

Damn, I haven’t thought of that! Looks like I have to use a subdirectory of your Homedir from now on.

Not everything needs to be deployed to a cluster of georedundant K8s nodes, not everything needs to be a container, Docker is not always necessary. Just run the damn binary. Just build a .deb package.

(Disclaimer: yes, all those things can have merit and reasons. Doesn’t mean you have to shove them into everything.)

I tend to use /opt/[service]/, like for example /opt/forgejo/. It’s outside of any user’s Homedir and it seems to fit into what the FHS 3.0 (Filesystem Hierarchy Standard) defines.