rename and chmod (was: cp -p)
wouter at fizzyflux.nl
Fri Feb 8 11:28:58 UTC 2008
>Now, from a logical point of view, why moving a file into a directory
doesn't fall into the "created into them" case?
Because (if on the same filesystem) you don't create a new file. You
just link the file in the destination dir and unlink the file from the
2008/2/8, Pietro Cerutti <gahr at gahr.ch>:
> Ok, my view is getting clearer ;-)
> my problem in understanding the semantics of mv, cp -p and the rename(2)
> function seems to be related to the terminology used in chmod(1) man page.
> This is the explanation of setuid (the same holds for setgid):
> "Directories with this bit set will force all files and subdirectories
> created in them to be owned by the directory owner and not by the uid of
> the creating process, if the underlying file system supports this feature"
> Now, from a logical point of view, why moving a file into a directory
> doesn't fall into the "created into them" case?
> Pietro Cerutti
> PGP Public Key:
wouter at berenboot.xs4all.nl is binnenkort niet meer,
wouter at fizzyflux.nl is mijn nieuwe email-adres.
More information about the freebsd-questions