It only occurs during the synchronizing process. So I don't think that the FAT32 formatting of the usb-stick does not support extended attributes created on OS X. This cannot be a problem of the usb-stick format, because there are already aliases on the usb-stick which I copied manually these are working fine, finding the original document immediately. I "opened" the batch: all paths are enumerated, and the last remark is "cannot execute binary file". Anyway, since 8.2 (and still with 8.3) FFS turns every alias of a document from my Computer into a batch (Terminal.app) on the usb-stick. I used to synchronize documents between Mac OS X El Capitain and an usb-stick (formatted FAT32 in order to be used on all kinds of operating systems) and I wasn't aware of the problem at once, because most documents are not aliases. Hi, I am using FFS since July, and I am very pleased with the convenient handling and clear surface.īut now I have a problem with aliases as well. Do you think using hard links would solve my problem? If so, can you recommend a tool for making hard links without having to use the terminal? Using Google, I found some hints about the difference between „normal“ Mac alias files and hard links, however I am not familiar enough with the Mac terminal to try the latter. „*/.DS_Store */._*“ or „*/.DS_Store“ or none), but could not get the desired result. I have also tried several exclude filters (e.g. I have tried the different settings for symbolic link handling, but neither „direct“ (this is what I am intending to do) nor „exclude“ nor „follow“ seem to work. When using FreeFileSync to copy the aliases, they change their file type to either „Ausführbare UNIX-Datei“ or „Dokument“, whereas when copying them manually, they keep the file type „Alias“. they still point to the same relative folder path. OnyX is a multifunction utility that you can use to verify the structure of the system files run miscellaneous maintenance and cleaning tasks configure parameters in the Finder, Dock, Safari, and some Apple applications delete caches remove certain problematic folders and files rebuild various databases and indexes and more. When I copy them manually to the USB stick and from there to the other Mac, they work well, i.e. Normal data files are ok, but I have a lot of „normal" Mac aliases pointing to various folders (created with the cmd+L shortcut), which lose their functionality if copied with FreeFileSync. I use the FreeFileSync Mac OSX version 6.10 on two MacBookPro laptops (both with OSX 10.9 = Mavericks) and an USB stick or external hard disk (formatted with ExFAT or Mac OS Extended Journaled file system) to synchronize my data between them. I really like FreeFileSync, however, since I moved from Windows to Mac, I have a problem when copying Mac aliases and I wonder whether this is a bug or whether I just do not use the proper settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |