Hi!
> Giving the O_COW flag to open() will return a special error, if
> IS_COW(inode) and write permissions are expressed or implied. COW-aware
> applications may set this flag and deal with this error according to
> some user defined policy. This will not change the semantics of any
> existing application or affect any kernel user of open_namei(); nor does
> it affect future applications unless they use O_COW. Filesystem level
> code is unimplemented except for an ext2 example.
Can you give us overview how this is used? COW for ext2 seems nice...
Is the plan to allow cp -a --cow linux linux.new ?
Pavel
--
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
