metafork

Members
  • Posts

    4
  • Joined

  • Last visited

metafork's Achievements

New User

New User (1/3)

  1. I can totally accept the situation that Btsync won't support full filesystem features, but it's not an option for me then. But it should be still noted on a prominent place, at least the FAQ, that those features are ignored (and files synchronized incompletely).
  2. Sagdusmir: Yes, you're right, but to my knowledge both extended attributes and forks are implemented with the same filesystem features in current HFS+. .AppleDouble files are history, current tools (like rsync and cp) use different suffixes. Are you experiencing the same, i.e. that resource forks are not synced and therefore the files destroyed with BitTorrent Sync?
  3. Rusl, thanks a lot for your answer. As far as I'm informed about the implementation of certain features of Mac OS X both resource forks and Finder labels (implemented as Extended Attributes AFAIK) are implemented as HFS+ metadata features. They are stored in .DS_Store files and ._ressource files only on non-HFS+ filesystems. Both information is lost in the synchronisation process. While loosing finder labels could be acceptable, loosing resource forks isn't, as for certain file types (so called Text Clips or URL dropped to a Finder window e.g.) they contain the data, while the file itself is empty (this is what I mean with destructive). A Mac OS X-compatible synchronisation system needs to support those advanced filesystem features and if not should IMHO display a strong warning that it doesn't. In the meantime I found another thread answering my question negatively (http://forum.bittorrent.com/topic/18036-extended-attributes/). That's a pity. Thanks again for trying to help. Bye.
  4. Hi, basically BitTorrent Sync is an absolutely great thing. But: I just made an experiment trying to sync a folder between two macs, and filesystem metadata and resource forks are not being synced, meaning that BitTorrent Sync behaves destructive (I've installed 1.1.48 on both computers). Is this intended behaviour or am I missing something? I also think that this is an important question and it should be part of the main FAQ. Thanks