Date: Fri, 15 Apr 2011 21:05:54 -0500 From: Daniel Mayfield <dan@3geeks.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: question on extended attributes Message-ID: <380C2890-68F4-4153-9306-965543F622EF@3geeks.org> In-Reply-To: <945861089.125242.1302917134332.JavaMail.root@erie.cs.uoguelph.ca> References: <945861089.125242.1302917134332.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> Oh, I don't know if this might help, but... >=20 > The Mac OS X NFS client will create a bunch of .XXX files to store > the resource forks. So, if you NFS mounted the FreeBSD volume on > your Mac and then copied the subtree to the NFS mount point, Mac OS X > "might" create the fake resource fork files for you? (I'm not sure > which Mac copy programs know about resource forks.) If this works, > you'll see a bunch of stuff in the directories with names that start > with ._ if I recall correctly. Not sure what you can do with them on > FreeBSD though? I've seen that behavior too. My goal is have this work over ssh, as I am of= ten accessing things remotely. I want to be able do work on the freebsd sid= e(read, write, move or delete files) without leaving nfs droppings all over m= y filesystem. Think more along the lines of active/active working hosts than as a backup f= ile repository. I'm looking for least surprise when using the freebsd side.= Daniel=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?380C2890-68F4-4153-9306-965543F622EF>