Nathan Neulinger wrote:
> 
> The code to handle @sys looks pretty trivial to me. I think that a
> little effort should be put into making @ variables fully dynamic. If an
> admin decided not to use it, then that's fine, but at least the
> functionality would be there.

Could you be more specific? What do you have in mind when you say "fully
dynamic?" That admins (or even users) could define their own @ variables
on the fly? That's a little more dynamic than I've been hoping for.
(Although, truth to tell, I haven't really considered the
possibilities...)

We live and die by the @sys variable. More functionality, if well
designed, could be a really good thing. The one variable is too
limiting, I'm afraid.
-- 
   +------------------------------------------------------------+
  / [EMAIL PROTECTED]              http://www.unc.edu/~utoddl /
 /(919) 962-5273     Official Signature of the New Millennium /
+------------------------------------------------------------+
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel

Reply via email to