mirror of
https://https.git.savannah.gnu.org/git/findutils.git
synced 2026-01-26 07:37:52 +00:00
NEWS: enhance description about the -mount change
* NEWS (Changes in find): Clarify better what is the difference between the -mount and -xdev options including an example. Also move the topic to the top of the section due to its importance.
This commit is contained in:
parent
cd8568758a
commit
6da3a73f73
14
NEWS
14
NEWS
@ -20,6 +20,17 @@ GNU findutils NEWS - User visible changes. -*- outline -*- (allout)
|
||||
|
||||
** Changes in find
|
||||
|
||||
As announced since the release of 4.7.0 (2019) and mandated by POSIX 2024,
|
||||
the behaviour of the -mount option changed: while it was a mere alias for
|
||||
the -xdev option to prevent descending into directories of another device,
|
||||
the -mount option now makes find(1) ignore files on another device, i.e.,
|
||||
'find -mount' will skip the entry of active mount points already.
|
||||
Example, assuming the PROC filesystem is mounted on '/proc':
|
||||
$ find / -mount -path /proc -print
|
||||
$ find / -xdev -path /proc -print
|
||||
/proc
|
||||
[#54745]
|
||||
|
||||
The actions -execdir and -okdir now refuse the '{}' replacement in the zeroth
|
||||
argument of the command to be run. While POSIX allows this for -exec, this is
|
||||
deemed insecure as an attacker could influence which files could be found.
|
||||
@ -28,9 +39,6 @@ GNU findutils NEWS - User visible changes. -*- outline -*- (allout)
|
||||
are passed with a leading dash, e.g. '-!'. Future releases will not accept
|
||||
that any more. Accepting that was rather a bug "since the beginning".
|
||||
|
||||
The -mount option is now POSIX 2024 compliant. Find will ignore files on
|
||||
different devices as opposed to being a mere alias for -xdev. [#54745]
|
||||
|
||||
** Documentation Changes
|
||||
|
||||
The forthcoming Issue 8 of the POSIX standard will standardise "find
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user