[2260] in Release_Engineering
Re: [Liz_Hines@transarc.com: AFS System Types]
probe@ATHENA.MIT.EDU (probe@ATHENA.MIT.EDU)
Sun Apr 15 23:49:36 1990
I do knot know what you mean by support both. The following is about the
only way I can think of to set the fallbacks reasonably, and I am not
sure that it will be trivial to implement (it may or may not be), but I
certainly don't think it is clean:
1) First try the lookup with the new @sys convention.
2) Try the lookup with the old @sys convention.
3) If both fail, consider the expansion to be the new one.
Do you really want to be replacing @sys multiple times and doing VFS_LOOKUP()
calls each time? I don't think this is a good idea, and I doubt I would
have time to implement it for 7.0.
Also, will this work in all cases; I am not convinced.
One thing is certain, though; the extra VFS_LOOKUP() calls will take time,
and hopefully, you are not traversing into a remote cell when you are doing
this...
My other concern about implementing this is that we are still faced with the
problem of people being lax about changing their directory names until 7.1
and I certainly do not want the breakage to be visible during the Fall term
when AFS is supposedly going to be more widely used.
With regards to jfc's comment about "fs sysname": root can change the @sys
value to anything using the "fs sysname" command. However, as things are
being converted, I am sure that this will cause breakage for those who have
already converted and have dropped the old @sys name.
-Richard
