Markus Weich:
> > Great, you found what we want.
> > It must be Yama LSM and
> > /proc/sys/kernel/yama/protected_nonaccess_hardlinks.
> > Write 0 into /proc/.../protected_nonaccess_hardlinks and your rm will
> > succeed.
> Thanks! That solves my problem!
Glad to hear that.
You have another option
> Great, you found what we want.
> It must be Yama LSM and
> /proc/sys/kernel/yama/protected_nonaccess_hardlinks.
> Write 0 into /proc/.../protected_nonaccess_hardlinks and your rm will
> succeed.
Thanks! That solves my problem!
-
Markus Weich:
> Sounds logical, i tried to reconstruct your thinking, been to
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=tree, but
> didn't find the .c/.h file, where I thought I could find the
> information. So I have to believe you. Nervertheless could you give me
> some hi
Am 11.07.2013 02:08, schrieb sf...@users.sourceforge.net:
>
>> faccessat(AT_FDCWD, "d2/f1", W_OK) = 0
>> unlinkat(AT_FDCWD, "d2/f1", 0) = -1 EPERM (Operation not permitted)
>> ...
>> Hence it is unlinkat.
> Ok.
> Reading git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git,
> unlinkeat(2
Markus Weich:
> Here is what I did with strace:
:::
> faccessat(AT_FDCWD, "d2/f1", W_OK) = 0
> unlinkat(AT_FDCWD, "d2/f1", 0) = -1 EPERM (Operation not permitted)
> ...
> Hence it is unlinkat.
Ok.
Reading git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git,
unlinkeat(2) return
Here is what I did with strace:
fred@it1-pc33:~/test$ mkdir d1 d2 home; touch home/f1; sudo mount -t
aufs -o br=d1:home none d2
fred@it1-pc33:~/test$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
...
none on /home2/fred/test/d2 type aufs (rw,relatime,si=deb855b9)
Homedir of fred is ext4
Markus Weich:
> just to sum up again: as user fred2, I did: mkdir d1 d2 home; touch home/f1
> as root, I did: mount -t aufs -o br=d1:home none d2
> root@it1-pc40:$ find d1 d2 home -printf "%h/%f %M %u %g\n"
> ./d1 drwxr-xr-x fred2 users
> d1/.wh..wh.plnk drwx-- root root
> d1/.wh..wh.aufs -r
>>> 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
> bran
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 permi
Have you created the file as root? Then it's probably owned by root, and the
normal user simply lacks permissions to delete it.
On Mon, Jul 8, 2013 at 12:06 AM, Markus Weich <[1]markus.we...@gmx.de>
wrote:
Hi folks,
i want to delete a file as normal user, but i fail to do i
10 matches
Mail list logo