I think the FHS doesn’t really tell you where. In the end you can out them wherever you want as long there is no conflict with the FHS. Even /mnt/something seems fine. Just not really recommended.
I think the FHS doesn’t really tell you where. In the end you can out them wherever you want as long there is no conflict with the FHS. Even /mnt/something seems fine. Just not really recommended.
Uhh, very nice. I didn’t know about xdg-ninja.
I added icons and corrected some things.
Afaik guix is very similar to nixos in that respect. The store where applications are installed is called /gnu there.
Thanks for the input. Things are complicated: https://askubuntu.com/a/135679 . Apparently it originally meant “user” but then slowly was used for system stuff. So people invented backcronyms.
I unfortunately did it in whimsical.com which is great but also closed if you don’t pay. https://whimsical.com/fhs-L6iL5t8kBtCFzAQywZyP4X is the best I can do.
The better you understand it the less it seems bad.
Added!
Added a black background version.
The legend is a bit broken. Will fix it maybe.
As for the rest, yes, the FHS can be confusing. It’s from a time where mostly professional admins would deal with it and requirements were pretty different from today’s end-user systems. If you want to understand more, I urge you to read the spec. It’s highly readable! https://refspecs.linuxfoundation.org/FHS_3.0/fhs.html
You could invert the colors in GIMP or similar.
There is a lot of work being done on reproducible builds in the guix project and other distros. The idea being that you can be sure that a binary package is bit for bit the same, whoever builds it and on whatever system. This would be the first time you have complete traceability of what goes into your binaries.
On guix, you can for example install substitutes of packages which you could also build manually. Since the build environment and the dependencies are very tightly controlled, you have mathematical proof that the substitute is equivalent to the package built by the maintainer. You can thus be sure that no evil third party injected malware into the substitute binary, unless ot was done at source code level and the package maintainer has put it there (by accident).
The colors are confusing. I meant to mark /home as non-standard since it’s not mandated by the FHS.
The FHS doesn’t specifically mention the config of webservices but /srv seems good to me. Read https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s17.html for more info.
Edit: Changed colors
I’ll have a look but probably not.
I guess the reason it’s not in FHS is that FHS is concerned about system wide things whereas /home is the opposite. It’s the user’s realm.
There is XDG for /home/$user though.
Of course you can, but few people care and do it. There is a saying about docker: “Docker images are like smoothies, you immediately know if you like it but you don’t know what’s inside”. The idea being that there is no good quality control and transparency. People just install random blobs, like in the old days where you would install a cracked game from eMule.
If you care about security, docker is not what you want, they are not reproducible nor transparent nor is it possible to easily update broken shared libraries (eg openssl).
But then again people have different requirements. Some just wanna have things running quickly without the hassle. That’s where docker shines. But it leads us to a world where we hide ugly stuff under the carpet instead of fixing things.
I spent a few hours making it myself. Of course based on the standard document.
But who knows what’s inside?
That doesn’t look good :(