G bor Stefanik: > Have you created the file as root? Then it's probably owned by root, and > the normal user simply lacks permissions to delete it.
If you have a write permisstion for the parent dir, you can remove the file even if the file is owned by root or readonly. The point is not the permission of the file. It is the parent dir's permission. This is a generic semantics of unix filesystems. Markus Weich: > > mkdir d1 d2 home; touch home/f1 > > sudo mount -t aufs -o br=d1:home none d2 > > > > everything is fine now, until: > > rm d2/f1 > > --> I get: not possible, operation not permitted (freely translated from > > German) I'd suggest you to check the parent dir's permission bits on every branch. $ ls -ld d1 home d2 Next time you post a mail about the problem, I need these info. (from the aufs README file) 5. Contact ---------------------------------------- When you have any problems or strange behaviour in aufs, please let me know with: - /proc/mounts (instead of the output of mount(8)) - /sys/module/aufs/* - /sys/fs/aufs/* (if you have them) - /debug/aufs/* (if you have them) - linux kernel version if your kernel is not plain, for example modified by distributor, the url where i can download its source is necessary too. - aufs version which was printed at loading the module or booting the system, instead of the date you downloaded. - configuration (define/undefine CONFIG_AUFS_xxx) - kernel configuration or /proc/config.gz (if you have it) - behaviour which you think to be incorrect - actual operation, reproducible one is better - mailto: aufs-users at lists.sourceforge.net J. R. Okajima ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
