\section{/srv}
\begin{frame}
   {/srv}

   \begin{itemize}

      \item
      Site-specific variable data
      \item
      Data, scripts, for servers (http, ftp, etc.)
      \item
      Repositories for version control systems
      \item
      Packages should not place files there on installation

   \end{itemize}
\end{frame}

\cprotect\note{

   According to the \textbf{FHS}:

   \begin{quote}

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

      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.

      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, e.g.. ftp, rsync, www, and cvs.

   \end{quote}

   Some system administrators (and distributions) swear by the
   use of \filelink{/srv}; others ignore it.  There is often
   confusion about what is best to go in \filelink{/var} as
   opposed to \filelink{/srv}.

}
