No, I don't agree with you here. Allowing a large group of people to all have root access is simply asking for trouble.
Not a large number of people - just the core admin team ... but I actually agree with you ... (see later).
The admin team would have access to whichever files it turns out to be necessary to have access to on more than a one-off basis. /etc/named.conf, for example, is *not* such a file: it needs to be set up only once, not changed regularly.
I am just trying to clarify things - remember you initial statement was that is was key to be able to "install and run arbitrary programs" - I am just trying to see how a structure can be enforced so that such things are possible.
From what you are saying is that you propose to install all the bits we would require for OSE for us, setup apache and DNS as required, and then let the admin team get on with the mechanics of the site. So you would naturally retain control over your server, but would be open to suggestions for its configuration ? Is this a fair summary ?
If so, then it all sounds great to me - but I am just trying to clarify exactly how you see it working, and what level of access could be possible (or even needed) for OSE to function.
Why is this a problem?
It is not a problem. I am just trying to clarify what needs to be done and what options are available, and to see how this could fit in with your proposal for a shared server. Thanks for explaining. Kevin.