![]() I'm wondering what the best application to manage the transfer of data might be? In Windows environments I've used Robocopy or FTP and the likes but not really familiar on the Mac side of things when it comes to data migrations. We are in the process of planning a large data migration (~18TB) from the mac formatted NAS device, onto a Windows Server (using NetApp as the storage solution / VM datastore) I work for a company that currently stores its files on an OS X Journaled NAS device, connected to a Mac Mini via lightning cable, and the mac connects into the network via ethernet. ![]() I'm pretty sure the Finder (with Automator scripting) could do the same, but I can't help there.Apologies in advance if this has ended up in the wrong section of the forum, hoping someone could point me in the right direction. The Finder will no longer declare the plain files to be Unix executables that would require specific internal data formatting of the file that no self-respecting PC would ever perform, even at random. ![]() File permissions will then be 600 (u=rw). To limit permissions so that only the owner can read/write the files, change the chmod a-x command to chmod u-x,go-rwx. The permissions will look like 666 (ugo=rw). Permissions will still most likely allow anyone to read and write plain files. ![]() When done, every file in the user's home directory and below will have no execute permission. The '-0' tells xargs to expect NULL terminated arguments this allows for embedded spaces in path names and file names. The xargs takes its standard input from the other end of the pipe and applies the command argument (here, chmod a-x) to as many items that can fit on a command line. The '-print0' emits the plain file path, NULL terminated, to standard output (which is fed into the pipe).ģ. The '-type f' filters for plain files only (no folders, devices, sockets, pipes, etc.). The '-x' keeps find from wandering too far afield (away from the drive the home directory is on). The find starts in the current directory (now set to the user's home), and walks the entire tree of files and folders. The cd without argument forces the shell to the user's home directory.Ģ. x -type f -print0 | xargs -0 chmod a-xġ. In Terminal.app, use the find command to locate plain files (not directories) and turn off execute permissions: pdf document.įolders, being directories, use the execute permission to allow/disallow searching by the user (owner), group members, and/or other (everyone else).Īssuming she has no applications in her account, the only entities with execute/search permissions required will be folders. Anyone can read, write, and execute the file, even if it is a. Select a file, do Get Info (fan-I), and look at the permissions. When transferred to Mac (Unix), everything has permissions that declare the file to be executable, by anyone. Does anyone know of some simpler fix? I know there must be thousands of people who've been frustrated by this issue, but googling didn't help me much.Īlso, file permissions in PC-land are : everything is executable. Is there possibly an Applescript or something that could be used to append file extensions to groups of the files all at once? I know there were Finder scripts that could be used for that task in the past, but at least on my Snow Leopard machine, they don't appear to include those anymore. FYI, the files seem to be a mix of Word, Excel, Powerpoint and saved email messages (.eml, I asume, but haven't tested that). I've tried the Finder's "open with"/"change all" trick, but with any of these files, the "change all" button is grayed-out. I've shown her how she can simply drag-and-drop them to application icons in the Dock to open them, but we'd love to find a way to 'fix' the problem. Someone copied over all her files, and a majority of them have no file extension, and thus are seen in the Finder as "unix executables". I have a client who recently moved to a Mac from a PC. I'm sure some of you have experienced this.
0 Comments
Leave a Reply. |