I've been trying to mount an FSKit volume at the location where FileProvider saves files: ~/Library/CloudStorage . I've discovered that FileProvider attempts to call setAttributes in order to assign a value for an access control list (ACL). This call fails, because FSKit does not support this attribute, and causes FileProvider to stop working. FileProvider refuses to continue beyond creating it's domain folder when this occurs. Do you believe this constitutes a valid enhancement request for FSKit and/or FileProvider?
FileProvider & FSKit compatability
I've been trying to mount an FSKit volume at the location where FileProvider saves files: ~/Library/CloudStorage .
Why? What are you actually trying to do here? Setting the specific issue aside, I'm not sure what the consequences of taking over that folder might be, but I'm not surprised that it failed.
I've discovered that FileProvider attempts to call setAttributes in order to assign a value for an access control list (ACL).
This actually has me a bit confused. What were the actual circumstances involved here? ACLs aren't actually stored as xattr's (at least not by the system itself) and, if they were, then I'd expect FSKit to block requests from ever reaching your file system.
Do you believe this constitutes a valid enhancement request for FSKit and/or FileProvider?
It's certainly reasonable to ask for FSKit to support ACLs. However, that doesn't mean FileProvider should allow itself to operate on your mount.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware