Some larger sites automatically generate volume names, which means there may actually be some places with x3xlkj8 (or whatever) as a volume name. 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.
Steven -----Original Message----- ... Old clients get some sort of hash of the volume name, and we pray the hashes don't collide. ... _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
