SPECS: faqomatic.spec, bb4.spec, bannerfilter.spec - /home/service...

Tomek Orzechowski orzech w pld-linux.org
Śro, 18 Lut 2004, 16:10:41 CET


[18 luty, 2004] andree napisał:

>Author: andree                       Date: Wed Feb 18 14:38:26 2004 GMT
>Module: SPECS                         Tag: HEAD
>---- Log message:
>- /home/services -> /srv (FHS 2.3)

Nie!

http://lists-archive.pld-linux.org/html/pld-devel-pl/2004-02/msg01087.html

I dla przypomnienia:

/srv : Data for services provided by this system

Purpose

/srv contains site-specific data which is served by this system.


    Rationale: This main purpose of specifying this is so that users may find
    the location of the data files for particular service, and so that services
    which require a single tree for readonly data, writable data and scripts
    (such as cgi scripts) can be reasonably placed. Data that is only of
    interest to a specific user should go in that users' home directory.

    The methodology used to name subdirectories of /srv is unspecified as there
    is currently no consensus on how this should be done. One method for
    structuring data under /srv is by protocol, eg. ftp, rsync, www, and cvs.
    On large systems it can be useful to structure /srv by administrative
    context, such as /srv/physics/www, /srv/compsci/cvs, etc. This setup will
    differ from host to host. Therefore, no program should rely on a specific
    subdirectory structure of /srv existing or data necessarily being stored in
    /srv. However /srv should always exist on FHS compliant systems and should
    be used as the default location for such data.

    Distributions must take care not to remove locally placed files in these
    directories without administrator permission. [20]

-- 
  _  _._. _  .|_
 (_)|  /_(/.(.| )
Tomek  Orzechowski
                                       Solitude, mon Dieu, solitude...



Więcej informacji o liście dyskusyjnej pld-devel-pl