Pau,
"Pau-Chen Cheng (862-3945)" <[EMAIL PROTECTED]> writes:
> 1. Is it an absolute requirement to put all volumes under
> a single, big subtree ?
On an AFS client, you run the afsd daemon. The daemon mounts a given
AFS volume on a given directory and handles any future references to
that directory. In the default case, "root.afs" is mounted on "/afs".
Only one directory can be mounted per afsd, and the afsd can only be
started once per system boot. (And, yes, a restartable afsd is on our
list of top requests.) That means that for any single client, the AFS
storage must be represented as a tree.
You could, however, have a wide variety of trees available on
different clients. You might make the normal /afs directory available
on one machine and /usr/good-stuff available on another. Perhaps
/usr/good-stuff would be a mount point for the volume root.good-stuff.
This alternate arrangement could be made by using the appropriate afsd
command-line switches to specify the volume and directory names.
I should mention that this isn't an official Product Support response.
I've never actually tried this, and there's a chance that I'm glossing
over some important details!
Joe Jackson,
AFS Product Support,
Transarc Corp.
