Le mercredi 27 juin 2007 à 20:52 +0200, Axel Thimm a écrit :
On Wed, Jun 27, 2007 at 08:41:43PM +0200, Nicolas Mailhot wrote:
You have file resources, and you have local network policies (which may even be dynamic with dhcp avahi & friends). They never map 1:1. Forcing file layout to reflect domain layout is an exercise in futility.
I agree, which is why you can't this all happen under /srv.
No. That means you partition /srv in an rpm-controlled part, and a free-for-all part. This way you can have sane pre-configured defaults, and people can do something else if they really want to.
The current habit of shunning /srv at all costs results in: — defaults not being pre-configured & installed because the sane place to put them is blacklisted — or defaults that can not serve as examples (because their layout has no relation with the /srv/ users are supposed to use), confuse scripts (again because of the layout mismatch), confuse security policies, etc
You can have a /srv/default and a /srv/local, or a /srv and /local/srv, or whatever but two totally different policies is just shooting ourselves in the foot.