[OpenAFS] MacOS AppleDouble excretions

Derrick Brashear shadow@gmail.com
Mon, 11 Oct 2010 06:21:22 -0400

On Sun, Oct 10, 2010 at 4:02 PM, Thomas Briggs <tbriggs@cs.ship.edu> wrote:
> On Oct 10, 2010, at 3:24 PM, Adam Megacz wrote:
>> The more sophisticated approach would probably be to claim to MacOS that
>> /afs/ supports resource forks, and report permission-denied when an
>> attempt to write a resource fork is made. =A0This has the advantage of n=
>> being filename-based and not breaking programs which access the
>> filesystem through the POSIX APIs.
> Perhaps the better approach would be to extend AFS allow OS dependent att=
ributes to be stored into the file system, to be retrieved in some client s=
pecific way? =A0Examples include OSX resource forks, linux style attributes=
, and access control lists. =A0Allow the client to have an RPC to retrieve =
these instead of embedding them as separate files? =A0OSX gets the worst br=
unt of this (because they use so many of them), but other OS's have them to=
o (including Windows)._______________________________________________

that's the intention, but the RPCs need to be designed, standardized,
and implemented. throwing away information in the meantime? uh, no.