It needs to be dealt with either in the filesystem implementation (kernel
level), or in the library providing the interface to the kernel calls.
If it's done in the application, code duplication will be ridiculous,
and application behaviour will be inconsistent.
If it's done in the library, there'll possibly be an extra cmp+branch
each time someone tries to move a file to a destination that already
exists. It doesn't happen *that* often, so the extra overhead might
be acceptable.
The kernel is kinda equivalent to the library, except it will only
have the extra cmp+branch for bizarre filesystems.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html