No, /srv should exist, but otherwise be empty from the vendor's
POV
(e.g. no package should own/place anything beneath /srv). We should
neither impose /srv/<service>, nor /srv/<service>/<domain>, nor
/srv/<domain>/<service> methods.
Well, let me point out that SE Linux policy needs to know what is going in that
location so that "the right thing" happens. We do need to impose some kind of
order so that people don't bump into MAC problems and turn SE Linux off.
-Steve
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com