On Mon, Dec 7, 2009 at 7:27 PM, Matt McCutchen wrote:
> On Mon, 2009-12-07 at 19:21 -0800, Parke Bostrom wrote:
>> Why is rsync with --link-dest not working as I expect it to in the
>> following example?
>
>> rsync -a --link-dest=a a/ b/
>
> >From the man page:
>
> --link-dest=DIR
> [...] If DIR i
On Mon, 2009-12-07 at 19:21 -0800, Parke Bostrom wrote:
> Why is rsync with --link-dest not working as I expect it to in the
> following example?
> rsync -a --link-dest=a a/ b/
>From the man page:
--link-dest=DIR
[...] If DIR is a relative path, it is relative to the destination
directory.
So y
Hi,
Why is rsync with --link-dest not working as I expect it to in the
following example?
rm -r a b
mkdir a
mkdir b
echo 'line one' > a/c.txt
rsync -a --link-dest=a a/ b/
stat -c %i a/c.txt b/c.txt
echo 'line two' >> a/c.txt
cat b/c.txt
echo
# compare:
rm b/c.txt
ln a/c.txt b/c.txt
stat -c
> "Charles" == Charles Marcus writes:
Charles> On 12/6/2009, Louise Hoffman (louise.hoff...@gmail.com) wrote:
>> The way I read that, it's not something rsync-specific. It sounds
>> like btrfs would allow the generation of a list of files, which rsync
>> (or tar, or zip, or w
On Sun, 2009-12-06 at 15:30 -0500, Benjamin R. Haskell wrote:
> Huh. Cool. This might not be all that difficult. I downloaded
> inotify-tools from inotify-tools.sf.net and the following test (monitor
> all changes to my home directory) seems to be producing interesting
> results:
>
> find /h
