[systemd-devel] systemd - move /selinux to /sys/fs/selinux - maybe remove /srv ?

[Jasper Boot]

Hi,

2011/4/29 Michał Piotrowski <mkkp4x4 at gmail.com>

> Hi,
>
> By the way, maybe it would be good to think about the meaning of /srv
> existance? For seven years FHS requires that this directory exists
> http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE16A
> but "The methodology used to name subdirectories of /srv is
> unspecified as there is currently no consensus on how this should be
> done" - so even the authors of the standard did not have anything to
> say about how this directory should be used. Is there a rational
> reason for the existence of this directory besides FHS conformance?
>

For years now I've been using /srv to contain the content for the various
(world visible) services my machines run. Instead of having a mix of
/var/www/ /home/apache /home/httpd/ /var/lib/mysql/ /var/named/ and other
directories the different distributions come up with (usually somewhere in
/var), I've standardized on /srv/www /srv/svn /srv/git/ /srv/mysql and
/srv/dns for all machines and distros. Instead of just getting rid of such a
useful directory I'd rather see an effort to come up with a beter
standardization / description.

Because /var already contains a lot of other variable/transient data, e.g.
log, spool and temporary files, I like the fact that I can have another
hierarchy for 'content' data instead of 'variable run/state' data. In /srv
is the really important data I need to backup and restore; /var is just
variable data that is needed in a running system, but isn't that essential
and specific to my system. You could almost say that /srv is the system-wide
/home in my case.

--
Regards,
Jasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20110429/17455ba9/attachment.html>