From 415dfd7ea5c419f6d4e11b75ccdc96da03d107c5 Mon Sep 17 00:00:00 2001 From: Victoria Bialas Date: Tue, 25 Oct 2016 10:59:38 -0700 Subject: [PATCH] updated to incorporate Misty's comments Signed-off-by: Victoria Bialas --- docker-for-mac/osxfs.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docker-for-mac/osxfs.md b/docker-for-mac/osxfs.md index a27a0ef636..1e41b2cf17 100644 --- a/docker-for-mac/osxfs.md +++ b/docker-for-mac/osxfs.md @@ -85,11 +85,9 @@ requests for ownership metadata will return the previously set values. Ownership-based permissions are only enforced at the OS X file system level with all accessing processes behaving as the user running Docker. If the user does not have permission to read extended attributes -on an object, e.g. when that object's permissions are `0000`, `osxfs` -will attempt to add an access control list entry allowing the user to -read and write extended attributes. If this is not possible or extended -attribute permissions are still denied, ownership will be reported as -the accessing process until the extended attribute is again readable. +on an object (such as when that object's permissions are `0000`), `osxfs` +will attempt to add an access control list (ACL) entry, which allows the user to +read and write extended attributes. If this attempt fails, the object will appear to be owned by the process accessing it until the extended attribute is readable again. ### File system events