From owner-freebsd-questions@FreeBSD.ORG Thu Jul 18 22:34:03 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DA80DDBF for ; Thu, 18 Jul 2013 22:34:03 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-gh0-f173.google.com (mail-gh0-f173.google.com [209.85.160.173]) by mx1.freebsd.org (Postfix) with ESMTP id 9E576CF7 for ; Thu, 18 Jul 2013 22:34:03 +0000 (UTC) Received: by mail-gh0-f173.google.com with SMTP id g16so1115795ghb.32 for ; Thu, 18 Jul 2013 15:34:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=i2m9jUptM53xsryle0FnJb7HtcovU5hoe9+qHl6CIbE=; b=M+4jbX89SwTbq9RXf2kHZx5+OkLXaPRfcNCKHDx/2gnrGTLUvsyUa5KpInESFCrltv b9psQqhv+dwU1aNxbN3oaUtXQmXeboq07Bz/cidylE15mADpO5TtCa+oiuNNQhdOx3jx jdognEa657TqX6/nUHEJs0e9YGrL5WQuXe1xaXeSOlPmr+OZ65zagoKWmurdI8UeO0Ir LQIYA0SESjCYMP10Syl9EDTHsyqsUs3MqLgxB0w5WpYD86yNWlk6J6aVy7Z+n3OIrnM+ OOIRnn3wPyszv7PlFyp2pjhHfafAhKDvR9LD+svNMnWQ2pFl7ymQe+7SJX8dERnKbPUn NsnA== X-Received: by 10.236.92.7 with SMTP id i7mr6458545yhf.240.1374171839270; Thu, 18 Jul 2013 11:23:59 -0700 (PDT) Received: from mbp1.kraus-haus.org (mail.thecreativeadvantage.com. [96.236.16.109]) by mx.google.com with ESMTPSA id m63sm16257114yhb.10.2013.07.18.11.23.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 11:23:58 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: OT: rsync on Mac OSX From: Paul Kraus In-Reply-To: <20130712185701.GA10084@neutralgood.org> Date: Thu, 18 Jul 2013 14:23:57 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <67um8rd2r07ipc.fsf@saturn.laptop> <67um8r61wsei8l.fsf@saturn.laptop> <6EC7DF61-0243-4BB3-904B-7289F574B256@lafn.org> <20130712185701.GA10084@neutralgood.org> To: "freebsd-questions@freebsd.org FreeBSD" X-Mailer: Apple Mail (2.1508) X-Gm-Message-State: ALoCoQlm2i07gMTiTnFGaG0bJ9Amfly3SZS0W4t9uSsDBIr8nQs3+GzARf0CEqj+3e1gAeFggAig X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 22:34:03 -0000 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 ._ 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