On Jul 12, 2013, at 2:57 PM, kpn...@pobox.com wrote:
> I thought MacOS X's rsync did handle resource forks if you gave it the
> proper option. The resource fork is reported by rsync in the usual
> convention of having "._" prefixed to the filename.
My understanding was that the files named ._ wer
On Fri, Jul 12, 2013 at 11:25 AM, Chris Maness wrote:
> Thank you for the detailed description of what resource forks are. One
> more clue in this mystery is that appending .mov extension to it fixes the
> problem.
That makes some sense, since without the resource fork some MacOS software
would
On Fri, Jul 12, 2013 at 11:12 AM, Paul Kraus wrote:
> Dropping the list …
>
> On Jul 12, 2013, at 1:49 PM, Chris Maness wrote:
>
> > Checksums are the same. All other files still work however the HUGE
> > rendered Final Cut Pro output, so I guess it is something in .DS_Store.
> > Last time I ju
On 12 July 2013, at 10:49, Chris Maness wrote:
> On Tue, Jul 2, 2013 at 3:11 PM, Chris Maness wrote:
>
>>
>>
>>
>>
>>> Since you are going to wait anyway, why don't you try peeking at some of
>>> the file checksums while this is running?
>>>
>>> MacOS X comes with a shasum utility which i
On Tue, Jul 2, 2013 at 3:11 PM, Chris Maness wrote:
>
>
>
>
>> Since you are going to wait anyway, why don't you try peeking at some of
>> the file checksums while this is running?
>>
>> MacOS X comes with a shasum utility which implements SHA-256 checksums,
>> so you should be able to look at a
> Since you are going to wait anyway, why don't you try peeking at some of
> the file checksums while this is running?
>
> MacOS X comes with a shasum utility which implements SHA-256 checksums,
> so you should be able to look at a few random samples of these files,
> e.g. by running on the source
On Tue, 2 Jul 2013 14:48:03 -0700, Chris Maness wrote:
>On Tue, Jul 2, 2013 at 2:30 PM, Giorgos Keramidas
>wrote:
>>On Tue, 2 Jul 2013 13:35:00 -0700, Chris Maness wrote:
>>> I have been using rsync with Mac OSX with no issues until today. I
>>> generally use it instead of the copy command beca
On Tue, Jul 2, 2013 at 2:30 PM, Giorgos Keramidas
wrote:
> On Tue, 2 Jul 2013 13:35:00 -0700, Chris Maness
> wrote:
> > I have been using rsync with Mac OSX with no issues until today. I
> > generally use it instead of the copy command because if the copy fails
> > on large files, I can pick up
On Tue, 2 Jul 2013 13:35:00 -0700, Chris Maness wrote:
> I have been using rsync with Mac OSX with no issues until today. I
> generally use it instead of the copy command because if the copy fails
> on large files, I can pick up where I left off. I have backed up
> entire Final Cut Pro projects
I have been using rsync with Mac OSX with no issues until today. I
generally use it instead of the copy command because if the copy fails on
large files, I can pick up where I left off. I have backed up entire Final
Cut Pro projects this way with no issues. However, I recently synced a
drive to
10 matches
Mail list logo
