--- xml/htdocs/proj/en/glep/glep-0020.html 2004/11/11 21:36:01 1.2 +++ xml/htdocs/proj/en/glep/glep-0020.html 2006/10/10 20:25:14 1.3 @@ -8,9 +8,252 @@ --> - + GLEP 20 -- /srv - Services Home Directory Support - + -
- +
@@ -35,7 +277,7 @@ - + @@ -43,7 +285,7 @@ - + @@ -52,8 +294,8 @@
Version:1.2
Last-Modified:2004/11/11 21:35:53
Last-Modified:2004/11/11 21:35:53
Author:Stuart Herbert <stuart at gentoo.org>, Rob Holland <tigger at gentoo.org>
Type:Standards Track
Content-Type:text/x-rst
Content-Type:text/x-rst
Created:09-Feb-2004

-
-

Contents

+
+

Contents

-
-

Thanks To

+
+

Thanks To

Thanks to Robin H. Johnson (robbat2@gentoo.org) for his assistance in writing this GLEP.

-
-

Abstract

+
+

Abstract

This GLEP proposes a new root-level directory - /srv - as an optional home for the data (and sometimes the software too) for software that provides services.

@@ -81,16 +323,16 @@

/srv is defined in FHS 2.3, which is part of the upcoming LSB v2.0 release (http://bugs.freestandards.org/cgi-bin/bugzilla/show_bug.cgi?id=16)

-
-

Motivation

+
+

Motivation

Gentoo currently does not provide sufficiently flexible support for sites which wish to consolidate the data for their service-orientated software under one simple, easy to administer, location.

Adding optional support for the /srv directory structure will give sites increased flexibility on how to layout their machines.

-
-

Specification

+
+

Specification

A new global USE flag - srvdir - will be added to Portage.

Ebuilds that choose to support the srvdir USE flag will configure the package to install and use their data under the /srv directory.

@@ -102,18 +344,18 @@ this breakdown of /srv:

/srv/<fqdn>/<service>/<service-specific tree>
-
+
where
<fqdn> is the fully-qualified domain name <service> is the name of the service <service-specific tree> is unique to the package
-

Ebuilds that install anything into /srv will install into /srv/localhost. +

Ebuilds that install anything into /srv will install into /srv/localhost. /srv/localhost - or any of the <service> directories underneath it - may be symlinks created by the local administrator.

-
-

Examples

+
+

Examples

For example, backup packages which support the srvdir USE flag could save backup data under the /srv/<hostname>/backups directory for each host on the network that they perform backups for.

@@ -129,8 +371,8 @@ recommended default location to use - although /var/localhost may prove a useful alternative.

-
-

Rationale

+
+

Rationale

Introducing optional support for the /srv directory will benefit a number of groups of Gentoo users.

    @@ -162,7 +404,7 @@ requires the user's home directory to be world-readable, which does not promote strong security!

    -
  • Users who wish to store service-orientated files onto a single logical +

  • Users who wish to store service-orientated files onto a single logical volume to support future growth

@@ -170,8 +412,8 @@ highly-configurable meta-distribution. Adding optional support for /srv is very much in keeping with our Philosophy.

-
-

Implementation

+
+

Implementation

A new USE flag - srvdir - will be added to Portage.

Ebuilds and eclasses will choose to support the srvdir USE flag or not on an individual basis.

@@ -180,30 +422,31 @@

There has been some debate about whether the /srv directory should be provided by the basesystem package or not. Because this support is optional, and because different sites will have different storage requirements, we believe -that it should be left to the local Gentoo system administrator to manually +that it should be left to the local Gentoo system administrator to manually create the /srv directory.

If baselayout feels that it must install a /srv, then we propose that baselayout installs /srv as a symlink to /var/srv. This approach will support installations that mount the root filesystem read-only.

-
-

Backwards Compatibility

+
+

Backwards Compatibility

Users who choose not to use the new srvdir USE flag will see little to no change. It is likely that some ebuilds will change their non-srvdir directory layout to reduce the amount of effort required to support both options.

- - +