>>18
The FHS is shit. I don't give three bits a damn about your stupid server needs when I want a sane directory organization for my personal computer. FHS is also hell for hacking around and shit to tell where shit is and should be. Then you have completely confusing and illogical names such as /etc (etcetera, for configuration?), /tmp (temporary, but don't delete or shit will break), /bin for "binaries" (though only executable binaries, not other binary data), /var/lib insanity, /opt bullshit, / vs /usr vs /usr/local stupidity (a popular source of problems), and it's made of boxes of shit. All the shit gets tossed into /usr/bin, talk about order and cleanliness (something perhaps you'd want in a server too). Then you have the obnoxious library version conflicts, and you don't have a way to fix it because "." in LD_LIBRARY_PATH is not the executable directory but the launching directory. The stupidity. Really, all this is so fucked up Mozilla had to use sh scripts to launch Firefox and Thunderbird reliably without relying on 40 stupid libraries of a specific version which you should have. This piece of shit also makes it hard to impossible to have several versions of the same software running if they depend on the same directories. And don't try to remove shit by hand, better leave that to some fucked up, bug-ridden, piss slow package manager. In fact, needing a package manager means something fails. If the system was laid out correctly, cp and rm would be your "package managers". And I can go on and on about the insanity and sheer stupidity of the FHS and all the Unix faggot fanatics that support that piece of shit.