>Much like NFS, at times Unionfs has to perform operations as another user. >... >If the foo is owned by someone else and we don't have write permission to >it, we'll fail to remove the opaque whiteout from foo (.wh.__dir_opaque), >which would in turn prevent us from removing foo itself. If we become a >superuser temporarily, we can remove the whiteout as well as the directory, >and all is well. What you're describing is not a need to perform operations as another user, but a need to perform them with DAC_OVERRIDE capability. In Linux, having uid 0 buys you nothing but access to files owned by uid 0. NFS server code, on the other hand, does have a need to become another user. -- Bryan Henderson IBM Almaden Research Center San Jose CA Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
