Date: Thu, 18 Jul 2013 14:23:57 -0400 From: Paul Kraus <paul@kraus-haus.org> To: "freebsd-questions@freebsd.org FreeBSD" <freebsd-questions@freebsd.org> Subject: Re: OT: rsync on Mac OSX Message-ID: <C3FA95F1-952C-49A7-B33D-1A2BE8B9202C@kraus-haus.org> In-Reply-To: <20130712185701.GA10084@neutralgood.org> References: <CANnsUMGyULjmK%2BQYeJHggZ6B2082wCPvU-8E_qcyg4j2OMrSWg@mail.gmail.com> <67um8rd2r07ipc.fsf@saturn.laptop> <CANnsUMF8udkQq=qQaUEGPtW9-LXsbrmdx0va_8cd_AhfnGB%2B8A@mail.gmail.com> <67um8r61wsei8l.fsf@saturn.laptop> <CANnsUMFg-dE=txssfSLyX46H1f9CnES%2BJZ9aaZvJCw%2BCxzx-2w@mail.gmail.com> <CANnsUMEqP%2B=HjhBSdWNXqC_CO%2B4Qb%2BVh-FttYdYT_d9u4m%2B2Yw@mail.gmail.com> <6EC7DF61-0243-4BB3-904B-7289F574B256@lafn.org> <20130712185701.GA10084@neutralgood.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 12, 2013, at 2:57 PM, kpneal@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 ._<foo> were plain files that = included the metadata that makes up the resource fork. The ._ file is = not really the resource fork, but a workaround for filesystems that do = not support resource forks. As such, they would be copied by rsync just fine. Now as to the Mac OS X rsync understanding resource forks, that I cannot = speak to, but it should be easy to test. Copy a directory from an HFS+ = volume to a non-Mac OS X volume (NFS for example) using rsync and see if = it creates the ._ files to go with the data. -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C3FA95F1-952C-49A7-B33D-1A2BE8B9202C>