The Georgraphy dept has GIS experts
The Advanced Visualization Lab are Viz experts
The ME dept have CAD experts
...skipping a large list of volumes...
The EE dept have VLSI experts.
( Yep we love the idea of groups within groups !
My only other concern is a rumor that if username == groupname bad things
can happen, and there are no good checks currently )
Others want to use the software they maintain. We like to
work together, shareing our expertice. They often own their
own fileservers, with open labs that all can share.
I set up RW volumes on their serves with a local RO and remote RO('s)
(repliacated) volumes. I set the quota, and ownership. And let them have
at it. Where the difficulty comes is when these folks want to update their
volumes. It seems pretty stupid to have to keep someone availiable at all
times (with AFS god status) to do what to me should be configureable on a
volume by volume basis. i.e let the owner of the volume do here/his own
vos release.
Has anyone implemented this? (have source will travel) We surely do not
intend to give all vos rights to every software maintainer in town.
Any thought, tricks, or ideas would be appreciated. I already do
the hidden passwd on trusted server trick to cron out the automated account
registration, where I can lock everything in place before I punt, but
these software volumes have random release requirements, and the
trust level may not be as high on some of those fileservers.
I assume these thoughts are being considered by those with one hand on the
DFS keyboard also.
Thanks,
Randall
