Help moving Application Support files to external HDD

Hi everyone,


I would like to move some of my application support files in library over to my external hard drive to free up some space (without affecting the application itself).


In particular, I would like to move this folder: /Users/[myname]/Library/Application\ Support/OpenEmu


...into this folder...


/Volumes/G-DRIVE\ mobile/Applications/Support\ Files


The actual app in this case is stored externally at /Volumes/G-DRIVE\ mobile/Applications/OpenEmu.app


I know you can somehow do this via terminal and I've tried to follow some instructions but to no avail. Maybe I'm doing something wrong? Can anyone walk me through it?


I'm running MacOS High Sierra on a Late 2016 Macbook Pro.


Cheers,


D

Posted on Jan 25, 2018 10:09 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 25, 2018 6:26 PM

The problem is that applications want to put and look for stuff in ~/Library/Application Support/app-name folders so if you want to try the following as an experiment let us know how it goes:


cd "~/Library/Application Support/"

---make sure the OpenEmu application is not running before proceeding---

cp -pR OpenEmu "/Volumes/G-DRIVE mobile/Applications Support/OpenEmu"

mv OpenEmu xxx-OpenEmu

ln -s "/Volumes/G-DRIVE mobile/Applications Support/OpenEmu" OpenEmu


Note the consistent naming of "Application Support" as opposed to "Applications/Support Files" in your example to maintain consistent location strategy (not important but less confusing I think). I renamed OpenEmu to xxx-OpenEmu in case there is a problem so you can go back to the way it was if needed (just trash the new "/Volumes/G-DRIVE mobile/Applications Support/OpenEmu" folder if there was a problem as well as the soft link).


Another thing to think about is to simply relocate the entire /Users folder to another volume -- this would let you keep everything together as it was designed to be. Not sure if SIP would allow this or not. I used to do something like this on a Yosemite system, but that was before SIP. In any event you have to make sure the other volume is large enough to store the entire /Users folder before trying to copy it. And you would need to copy it in a special way that maintains permissions, attributes and ownership. And you would want to modify the /etc/fstab file to automatically mount the new volume in place of the /Users folder -- do a "man fstab" and "man vifs" to see how to do that (it has examples).


Is that what you had in mind? By the way is the "G-DRIVE" volume NTFS or HFS+ or ??? -- not sure if this will work if it's not HFS+


Good luck...

4 replies
Question marked as Top-ranking reply

Jan 25, 2018 6:26 PM in response to dscross

The problem is that applications want to put and look for stuff in ~/Library/Application Support/app-name folders so if you want to try the following as an experiment let us know how it goes:


cd "~/Library/Application Support/"

---make sure the OpenEmu application is not running before proceeding---

cp -pR OpenEmu "/Volumes/G-DRIVE mobile/Applications Support/OpenEmu"

mv OpenEmu xxx-OpenEmu

ln -s "/Volumes/G-DRIVE mobile/Applications Support/OpenEmu" OpenEmu


Note the consistent naming of "Application Support" as opposed to "Applications/Support Files" in your example to maintain consistent location strategy (not important but less confusing I think). I renamed OpenEmu to xxx-OpenEmu in case there is a problem so you can go back to the way it was if needed (just trash the new "/Volumes/G-DRIVE mobile/Applications Support/OpenEmu" folder if there was a problem as well as the soft link).


Another thing to think about is to simply relocate the entire /Users folder to another volume -- this would let you keep everything together as it was designed to be. Not sure if SIP would allow this or not. I used to do something like this on a Yosemite system, but that was before SIP. In any event you have to make sure the other volume is large enough to store the entire /Users folder before trying to copy it. And you would need to copy it in a special way that maintains permissions, attributes and ownership. And you would want to modify the /etc/fstab file to automatically mount the new volume in place of the /Users folder -- do a "man fstab" and "man vifs" to see how to do that (it has examples).


Is that what you had in mind? By the way is the "G-DRIVE" volume NTFS or HFS+ or ??? -- not sure if this will work if it's not HFS+


Good luck...

Jan 25, 2018 5:55 PM in response to John Galt

You can't drag and drop application support files in your library folder without affecting the application itself. If I just dragged and dropped it the application (a) wouldn't know where to find the files (and there is no option to change location within the application), and (b) would still would not know where to place new files it saves. I obviously tried the drag and drop method. I was thinking you'd have to do a soft link via terminal or something in order for the application to recognise the files.

Jan 25, 2018 4:50 PM in response to dscross

Is there a reason you don't want to simply drag one folder to another location using the Finder?


Drag and drop items on Mac - Apple Support


"To copy the item instead of moving it, press and hold the Option key while you drag and drop."


If you need to use Terminal use the mv command. Rather than type the lengthy pathnames just type mv followed by a space character. Then, drag the source folder into the Terminal window, then drag the destination's icon into the Terminal window, then press the Return or Enter key. The only keys you have to press are those for mv, space, and Enter. Terminal will provide the fully qualified pathnames.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Help moving Application Support files to external HDD

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.