HAT | 28 May 2012 16:04
Picon
Gravatar

Why org.netatalk.*

The org.netatalk.ResourceFork on ZFS is the completely same format as
com.apple.ResourceFork on HFS+ .
Why is name org.netatalk.ResourceFork ?
If the name is com.apple.ResourceFork, is there any problem ?

In addition,
Is it possible to save Finder Info as com.apple.FinderInfo ?

--

-- 
HAT

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Frank Lahm | 29 May 2012 10:48

Re: Why org.netatalk.*

2012/5/28 HAT <hat <at> fa2.so-net.ne.jp>:
> The org.netatalk.ResourceFork on ZFS is the completely same format as
> com.apple.ResourceFork on HFS+ .

>From a design perspective that's just a coincidence.

> Why is name org.netatalk.ResourceFork ?

Because it's a Netatalk implementation detail.

> If the name is com.apple.ResourceFork, is there any problem ?

Nothing that I'm aware of, but it might lead to wrong assumptions when
accessing them over eg CIFS.

> In addition,
> Is it possible to save Finder Info as com.apple.FinderInfo ?

No, because we use more AppleDouble entries compared to com.apple.FinderInfo.

-f

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Gmane