[OpenAFS-devel] long volume names (was IPV6)

[Derrick J Brashear]

On Wed, 10 Sep 2003, Jenkins, Steven wrote:

>
> Some larger sites automatically generate volume names, which means there
> may actually be some places with x3xlkj8 (or whatever) as a volume name.

Sure, but as long as you always hand a translated name to clients, clients
don't get to (or need to) care. The namespace stays coherent even if
the names are nonsensical, because aside from the root volume (and
you'd need to ensure root.afs still worked, presumably) clients don't
typically know anything about names of volumes.

You have to upgrade your volume management tools, and if you're unwilling
or unable to do it, you don't get to use this extension.

> Most of the places I know of that auto-generate have some kind of naming
> conventions in place (eg, 'u' as the first char for user volumes, 's'
> for system components, etc), but I think it would be a good idea to put
> together a design doc and float it around openafs-info.

I'm in no danger of implementing this; If you want to spec it, (even if
you also have no time to implement it) go ahead.