On Thu, 10 Mar 2011 09:47:52 -0500 Michael Meffie <[email protected]> wrote:
> It seems to me, the approach would be to fold this back into volinfo, > however I don't see how that could be done without breaking backward > compatibility with the volinfo command line interface, since volinfo > does not have sub-commands. Any suggestions would be appreciated. You can have a tool called 'volscan', and have a symbolic or hard link called 'volinfo' to 'volscan'. In the tool, if you are called as 'volinfo', you interpret arguments in the volinfo-y way; otherwise you interpret them in the volscan-y way. -- Andrew Deason [email protected] _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
