For the mv shell command
The default action is to overwrite
the -n option ( --no-clobber ) prevents the overwrite
Fedora linux does not give any further advice
For the Apple / BSD world the man page suggests that the -n flag should never
be used in a script
openBSD/netBSD who normally
>
> the old rexxutil code had a test for the new and the old files resolving
> to the same target
>
The intent was to follow the behavior of mv (not rename), and mv doesn't
allow this
SysFileMove() function fails if the target file exists, but on Linux, the
> rename() function appears to work on t
This has always been a philosophical minefield. Unless you want to
convene a huge (and mortally contentious) Standards Committee to
resolve exactly what it means to "move" a file in all possible
filesystems, the only defensible solution is to make the function a
wrapper that simply punts the i
Greetings Rick,
Rick McGuire wrote:
the rename() function appears to work on the rename, which was unexpected. The
docs for the rename() function aren't really clear about that situation. Is
that expected?
Yes, unfortunately.
Known difference between Windows and *nix.
Even on Windows, bet
Starting to run my new unit tests on Linux and I've hit an interesting
difference between Windows and Linux. On Windows, the SysFileMove()
function fails if the target file exists, but on Linux, the rename()
function appears to work on the rename, which was unexpected. The docs for
the rename() fun
