Re^3: Why isn't there a "copy" function?

If I'm not mistaken, in the early days mv was _not_ able to move a file across file system boundaries, because it only implemented a rename. In those days you had to copy the file to the target FS and afterwards rm the leftovers on the source FS. Yes, you could call that ascetic. :-)

Comment on Re^3: Why isn't there a "copy" function?

Replies are listed 'Best First'.
Re^4: Why isn't there a "copy" function? by Eyck (Priest) on Sep 10, 2004 at 07:54 UTC
Actually I got burned few times by this new 'mv' behaviour, you mv something from one dir to another, and suddenly it starts copying without warning. This is very bad behaviour, this hurts ALOT when you're moving 1G file and there's only 700Megs left free on your partition. (especially when you're moving between mount -o bind'ed directory on the same filesystem and mv thinks these are two different filesystems)	[reply]

Replies are listed 'Best First'.

Re^4: Why isn't there a "copy" function?
by Eyck (Priest) on Sep 10, 2004 at 07:54 UTC

This is very bad behaviour, this hurts ALOT when you're moving 1G file and there's only 700Megs left free on your partition.

(especially when you're moving between mount -o bind'ed directory on the same filesystem and mv thinks these are two different filesystems)

[reply]