[KLUG Members] FHS postmortem

[Adam Tauno Williams]

> It would seem the REAL value of things like FHS is to provide a framework for 
> partitioning all activity in some useful ways. 

It also helps package maintainers know where given files should go.

> I can understand that putting 
> all things being served (in general) to a general audience is a laudable goal, 
> and moving those things from /var seems lik an improvement for logical pur-
> poses, less so for some of the more pragmatic motives that have been cited. We 
> already have the tools for that.

It may make a little more sense (as I think about it) to think of /srv
in terms of service than served.  Since things like tomcat and other
services run 'out of' /srv but don't really 'serve files'.  /srv is for
servers (that provide services) to use for their work area, not so much
for content that 'is served'.  Since a WAR or PHP file isn't really
"served" to the client,  but the server uses it to provide some
action/functionality/feedback to a client as a service.  PHP is a little
muddy of an example since it may be intermixed in with static content
(and people think of the PHP file as served to them since they see the
name in the URL);  a WAR (Tomcat/JBoss application) is a clearer
example.  [ a PHP script isn't really "served" to the client since your
don't see the PHP script "<?PHP....." but the effect of its being
processed ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://www.kalamazoolinux.org/pipermail/members/attachments/20050326/fe690562/attachment.bin