Scott Call
2016-Apr-27 17:50 UTC
[Samba] Migration to vfs_fruit with existing AppleDouble files?
(apologies to Ralph, I replied directly to him w/o copying the lists, so here we go again) In my testing that wasn't the case. If I manually copy the apple generated AppleDouble file and it's 0 byte main file to my test system, the correct size (including the resource forks) are shown but the file type is not translated. Using "GetFileInfo" a file copied to the new (vfs_fruit) server using finder will show: type: "tfil" creator: "movr" but the same file with the AppleDouble copied at the unix level (scp) from the old server shows: type: "\0\0\0\0" creator: "\0\0\0\0" So I think the missing piece is com.apple.FinderInfo xattr? Thanks! On Wed, Apr 27, 2016 at 10:29 AM, Ralph Boehme <slow at samba.org> wrote:> On Wed, Apr 27, 2016 at 10:08:46AM -0700, Scott Call wrote: > > Thanks for the response! > > > > This would be really helpful because we use a lot of old adobe type 1 > fonts > > that are 100% resource fork and are rendered unusable without the > > marshalled xattr's in addition to the AFP_ streams. > > resource forks are not xattrs and *are* converted. :) > > Cheerio! > -slow >
Ralph Boehme
2016-Apr-27 20:49 UTC
[Samba] Migration to vfs_fruit with existing AppleDouble files?
On Wed, Apr 27, 2016 at 10:50:12AM -0700, Scott Call wrote:> (apologies to Ralph, I replied directly to him w/o copying the lists, so > here we go again) > > > In my testing that wasn't the case. If I manually copy the apple generated > AppleDouble file and it's 0 byte main file to my test system, the correct > size (including the resource forks) are shown but the file type is not > translated. > > Using "GetFileInfo" a file copied to the new (vfs_fruit) server using > finder will show: > type: "tfil" > creator: "movr" > > but the same file with the AppleDouble copied at the unix level (scp) from > the old server shows: > type: "\0\0\0\0" > creator: "\0\0\0\0" > > So I think the missing piece is com.apple.FinderInfo xattr?hm, not sure if I convert FinderInfo from OS X AppleDouble to vfs_fruit native (depending on fruit:metadata setting either user.org.netatalk.metadata or iirc user.streams.AFP_FinderInfo). I thought I added the code, but I'd have to check. Cheerio! -slow
Scott Call
2016-May-03 19:51 UTC
[Samba] Migration to vfs_fruit with existing AppleDouble files?
If the code to convert FinderInfo is in a version later than 4.3.6 then I can request FreeNAS update their version. Can you let me know? Thanks! -Scott On Wed, Apr 27, 2016 at 1:49 PM, Ralph Boehme <slow at samba.org> wrote:> On Wed, Apr 27, 2016 at 10:50:12AM -0700, Scott Call wrote: > > (apologies to Ralph, I replied directly to him w/o copying the lists, so > > here we go again) > > > > > > In my testing that wasn't the case. If I manually copy the apple > generated > > AppleDouble file and it's 0 byte main file to my test system, the > correct > > size (including the resource forks) are shown but the file type is not > > translated. > > > > Using "GetFileInfo" a file copied to the new (vfs_fruit) server using > > finder will show: > > type: "tfil" > > creator: "movr" > > > > but the same file with the AppleDouble copied at the unix level (scp) > from > > the old server shows: > > type: "\0\0\0\0" > > creator: "\0\0\0\0" > > > > So I think the missing piece is com.apple.FinderInfo xattr? > > hm, not sure if I convert FinderInfo from OS X AppleDouble to > vfs_fruit native (depending on fruit:metadata setting either > user.org.netatalk.metadata or iirc user.streams.AFP_FinderInfo). I > thought I added the code, but I'd have to check. > > Cheerio! > -slow >
Reasonably Related Threads
- Migration to vfs_fruit with existing AppleDouble files?
- Migration to vfs_fruit with existing AppleDouble files?
- Migration to vfs_fruit with existing AppleDouble files?
- vfs_fruit: xattr imcompatible with netatalk
- Migration to vfs_fruit with existing AppleDouble files?