|
From: | Paul Eggert |
Subject: | bug#61050: mv: add support for --one-file-system |
Date: | Wed, 25 Jan 2023 01:07:48 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
On 2023-01-24 17:20, Mike Frysinger wrote:
i'd like to require that the mv be atomic when relocating a directory, and if it isn't, fallback to other logic
Calling the new option "--one-file-system" sounds a bit wrong, as --one-file-system is for programs like 'du' and 'cp' and causes them to not cross a file system boundary when recursing - something that 'mv' could also do (when it falls back on copying), but which is a different thing than what you're asking for.
How about if we call the new option --no-copy instead? Something like the attached incomplete patch, say. (It needs more documentation and ideally a test case.)
no-copy.diff
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |