hooanon...@gmail.com: > Alon Zahavi: > > # When using the aufs copy_up, the driver "copies" it with the capabilities. > > + touch ./aufs-root/_open_shadow > > + getcap -r ./ > > ./dir2/_open_shadow = cap_dac_read_search+eip > > ./aufs-root/_open_shadow = cap_dac_read_search+eip > > ./dirUSB/_open_shadow = cap_dac_read_search+eip > > Yes, it should be.
I think I found one of the big difference between you and me. You are comparing these cases, - 1: rename(2) a file from one filesystem to another mv ./dirUSB/_open_shadow ./dir2/_open_shadow - 2: rename(2) a file within a filesystem mv ./aufs-root/_open_shadow ./aufs-root/_copy_up_open_shadow But that is not a good idea. Note that aufs is a filesystem who tries being an ordinary filesystem. You are quite right in the point of aufs consists of multiple branches, and it internally copy-up the files. But all aufs internal works should be transparent, and aufs tries making it un-noticeable from users' point of view. Try comparing the result of these cases. - mv ./dirUSB/_open_shadow ./dirUSB/_open_shadow2 - mv ./aufs-root/_open_shadow ./aufs-root/_copy_up_open_shadow J. R. Okajima
