On 15.04.2012 04:23, Russ Allbery wrote: > I'd like us to consider switching to /var/lib/www for FHS compliance. > This does have the significant drawback of breaking backward compatibility > to at least some extent, but it's FHS-compliant (or at least is as good as > we're going to get for a default).
I do not think /var/lib would be any better than /var/www in respect to FHS compatibility. Note, /var/lib is defined as directory which holds "state information pertaining to an application or the system. State information is data that programs modify while they run, and that pertains to one specific host. Users must never need to modify files in /var/lib to configure a package's operation" [1]. This does not really qualify for documents served through HTTP which are neither vital or relevant to the web server itself, nor would it add any state to a running web server. On the other hand that may well be data which is to be modified (or even supplied) by the user. Likewise I find the data directory used by MySQL for example (/var/lib/mysql) wrong - but I personally do not intend to address that, too. I have no strong opinion on any particular directory, but I do not see why /var/lib/www would be better than /var/www/. Please let me know if I missed something here. [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
