@mcc There is a new `--update none` option to get the...

There is a new `--update none` option to get the old noclobber behavior, if you want it.

tbh I'm surprised 1) they made what could be a breaking change and 2) to my knowledge there has been no "you broke my scripts" outcry. Although probably the second can be found if I look hard enough.

Also, apparently posix only specifies -i and -f. Because, sure.

Like 30 June at 16:34 | Wall-to-wall | Open on hachyderm.io

8 comments

Matthew Miller

@mcc

IMHO good for the coreutils maintainers for making some of this stuff make more sense after all of these years.

But I'll wait for the "they hate Unix!" crowd to show up.

30 June at 16:36 | Open on hachyderm.io

lj·rk

@mattdm @mcc Unfortunately `-n` doesn't seem to be race-free though :/

https://unix.stackexchange.com/questions/248544/mv-move-file-only-if-destination-does-not-exist/248547?noredirect=1#comment428238_248547

With that in mind (if still true), I don't see any worth in a `-n` flag (invoking the "it's not UNIX" meme here :D). Then again, while there are many very bad options added by the GNU project if you ask me (GNU/tar's --checkpoint-action flag springs to mind), but this'd be a really useful flag in principle.

30 June at 16:46 | Open on todon.eu

Matthew Miller

@ljrk @mcc

Haven't tested, but I believe that's been fixed sometime after 2015. From the release notes for 8.30 (2018):

``` 'mv -n A B' no longer suffers from a race condition that can
overwrite a simultaneously-created B. This bug fix requires
platform support for the renameat2 or renameatx_np syscalls, found
in recent Linux and macOS kernels. As a side effect, 'mv -n A A'
now silently does nothing if A exists.
[bug introduced with coreutils-7.1]
```