> In an extreme case, if you would not be able to express some configuration > choice without an elaborated syntax, then you may define an appropriate > syntax and still place this data into a command line argument.
In some way which is arcane and not legible to the user? Why?? > To the contrary, mandating a config file (say, to express certain > "complex" options as you suggest) does create unnecessary constraints. Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
