4 ms·
This is wrong. Everything not specified in the FHS is the domain of the administrator and is a contract with the OS about what directories it wont touch. Nix,
by Spivak 6y ago
This is wrong. Everything not specified in the FHS is the domain of the administrator and is a contract with the OS about what directories it wont touch.
Nix, operating outside of the FHS, did the literal correct thing because there is no guarantee that the OS won’t install something in /opt/nix but there is a guarantee that it won’t touch /nix.
- mixedCase 6y agoAs a sysadmin you can do anything you want and are free to deal with the breakage you cause yourself. But the FHS pretty clearly establishes what behavior an application such as Nix should have: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03.html#purpose2 https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03.html#p... Quote: "Applications must never create or require special files or subdirectories in the root directory. Other locations in the FHS hierarchy provide more than enough flexibility for any package." They can choose not to abide the FHS, and that's fine if the users are happy with that tradeoff. But OSes observing the FHS are free to break Nix's expectations because they don't align with the FHS.
- Spivak 6y agoBut you’re missing the essential point which is that the FHS a set of rules that only apply to the distribution. > Applications [shipped by the distribution] should not... > Distributions should not create new directories in the root hierarchy without extremely careful consideration of the consequences including for application portability. The OS is free to break 3rd party applications that don’t follow their rules but strict adherence to the FHS is not the justification for doing so.