Jeff Hanson: > chown -R administrator:administrator /home/administrator/.wine-Diablo_II
Because you add -R, chown handles all of the specified dir, the files and the sub-dirs under it recursively and unconditionally. But what I suggested is to chown only the file which a user is going to modify. > I don't fully understand how aufs handles ownership and permissions. > From what Mike said it seems it just passes them through from the > branch filesystems. What happens if the same file exists in two ro > branches and they have different ownership? Does the order of the > branches when mounting determine which one gets priority in the mount > point? (from the aufs manual) ---------------------------------------------------------------------- The test for permission bits has two cases. One is for a directory, and the other is for a non-directory. In the case of a directory, aufs checks the permission bits of all existing directories. It means you need the correct privilege for the directories including the lower branches. The test for a non-directory is more simple. It checks only the topmost inode. ---------------------------------------------------------------------- J. R. Okajima ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
