[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <91c4ada9-5b5d-e93e-0bf6-b0a36b240880@gmail.com>
Date: Wed, 26 Aug 2020 09:31:25 +0200
From: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To: David Howells <dhowells@...hat.com>
Cc: mtk.manpages@...il.com, Alexander Viro <viro@...iv.linux.org.uk>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Christian Brauner <christian.brauner@...ntu.com>,
linux-man <linux-man@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>, Karel Zak <kzak@...hat.com>
Subject: Re: [PATCH 2/5] Add manpages for move_mount(2) and open_tree(2)
On 8/24/20 12:08 PM, David Howells wrote:
> Michael Kerrisk (man-pages) <mtk.manpages@...il.com> wrote:
>
>>> +To access the source mount object or the destination mountpoint, no
>>> +permissions are required on the object itself, but if either pathname is
>>> +supplied, execute (search) permission is required on all of the directories
>>> +specified in
>>> +.IR from_pathname " or " to_pathname .
>>> +.PP
>>> +The caller does, however, require the appropriate capabilities or permission
>>> +to effect a mount.
>>
>> Maybe better: s/effect/create/
>
> The mount has already been created. We're moving/attaching it.
Ahh -- then the verb was wrong.
to effect == to cause, bring about
to affect == to change, have an impact on
> Maybe:
>
> The caller does, however, require the appropriate privilege (Linux:
> the CAP_SYS_ADMIN capability) to move or attach mounts.
Yes, better.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Powered by blists - more mailing lists