Maybe have an 'openafs' command, which has all the other commands as sub-commands. Similar to the openssl command. That command would just be a front-end to the other excutables, and then those executables could use whatever naming convention which works best for installation, whether that be openafs-backup, afsbackup, or backup.openafs.
An 'openafs' command implies that all the commands would be under it, including 'fs', 'pts' etc. If that isn't a path we want to go down, then have the command be 'afsutil' or 'afstools'. I do think there is an advantage to having all of these findable via a single command. How many afs users even know that the 'up' command exists, for instance? It wouldn't surprise me too much if I'm the only one at RPI. -- Garance Alistair Drosehn Senior Systems Programmer Rensselaer Polytechnic Institute; Troy NY _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
