Jeffrey Hutzelman wrote:
On Tue, 6 May 2008, Jeffrey Altman wrote:
The real problem with this problem is that once the new file server is
deployed and the salvager is run against the volumes the existing MacOS
X clients will fail to be able to read any files in AFS. If anyone has
an idea of how to address the Unicode normalization problem going
forward that doesn't result in an interop failure for existing clients,
please say something.
I believe we discussed this issue when we designed extended directories
way back in... 2005? Old MacOS X clients here need to be treated in the
same way as other legacy clients, getting an old, unmodified directory
structure.
For Extended directories this won't be an issue.
I'm trying to solve the interop problem without extended directories
because we don't have them yet and I want MacOS X and Windows clients
to have interop now.
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel