[OpenAFS-devel] DRAFT: New sysname standard

[Neulinger, Nathan]

Yep. I figure just have:

fs setvar -name sys -value i386_linux22
fs setvar -name umr_arch -value redhat62

Should be very simple to implement, just need to add an additional
userspace->kernel opcode/pioctl call that takes two arguments. A "setvar"
for a variable that doesn't exist would create it, a setvar with no value
would delete it.

If no one else is already working on this, I'll be happy to work on a
prototype implementation for linux.

-- Nathan

> -----Original Message-----
> From: Todd M. Lewis [mailto:utoddl@email.unc.edu]
> Sent: Monday, May 07, 2001 7:29 AM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] DRAFT: New sysname standard
> 
> 
> 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.
> -- 
>    +------------------------------------------------------------+
>   / Todd_Lewis@unc.edu              http://www.unc.edu/~utoddl /
>  /(919) 962-5273     Official Signature of the New Millennium /
> +------------------------------------------------------------+
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel
>