Kamil Dudka wrote:
On Friday 24 of July 2009 21:49:35 Julian Bradfield wrote:
This hit me with the RH EL5 package coreutils-5.97-19.el5 .
I also see it in a build from clean coreutils-7.4 GNU release.
Problem: when printing files with the -1U options, and more than one
file is given on the
Hello,
the BTRFS file system, avaiable on Linux since its 2.6.29 version,
supports file cloning. This simple patch adds the support for this
feature to the cp utility.
Is there an easy and quick way to determine which file system is used by
a file? Probably it would be safer to add a guard
Giuseppe Scrivano wrote:
Hello,
the BTRFS file system, avaiable on Linux since its 2.6.29 version,
supports file cloning. This simple patch adds the support for this
feature to the cp utility.
Thanks! I like it.
A few comments:
Doesn't that constant, 1074041865, have a symbolic name?
Jim Meyering j...@meyering.net writes:
Doesn't that constant, 1074041865, have a symbolic name?
Maybe BTRFS_IOC_CLONE?
Yes, it is exactly BTRFS_IOC_CLONE and it is defined in the
fs/btrfs/ioctl.h file.
Is there an easy and quick way to determine which file system is used by
a file?
Giuseppe Scrivano wrote:
Jim Meyering j...@meyering.net writes:
Doesn't that constant, 1074041865, have a symbolic name?
Maybe BTRFS_IOC_CLONE?
Yes, it is exactly BTRFS_IOC_CLONE and it is defined in the
fs/btrfs/ioctl.h file.
Is there an easy and quick way to determine which file system
Hi Jim,
Jim Meyering j...@meyering.net writes:
However, but what about cp's --sparse option?
btrfs supports sparse files, so this new code will have to
honor that. The trouble is that there is currently no option
to say preserve precisely and only whatever holes are present
in src, which
