Mac Symbolic Link App
- Mac Os Symbolic Link
- Mac Create Symbolic Link Applications
- Symbolic Link In Mac
- Mac Symbolic Link App Source Code
I've tried three different ways to create a symbolic link to Sublime Text on my Mac and, after restarting terminal each time, it still keeps telling me command not found. I'm using a Mac with Yosemite (OSX Yosemite, 10.10). How can I create a symbolic link so I can open Sublime with the sub command? Symlink Creator is a tiny and portable software application that permits you to seamlessly create symbolic and hard links. A symbolic link, also known as a symlink or a soft link, is a special type of file that simply points to another file or directory just like shortcuts in Windows. Creating symbolic link is like creating alias to an actual file. If you try to access the symbolic link, you actually access the target file to.
Click here to return to the 'Create symbolic links for all items in a folder' hint |
Can you not just create a symbolic link at /Applications, to /path/to/apps?
# ln -s /Applications /path/to/apps
That's the method I use. Once in a while a dumb installer/updated will remove the sym-link and create another /Applications folder. I then have to move the installed/updated app to my real Apps folder, and recreate the sym-link. Sigh. Still, it's worth it!
Other way around. It's like making a copy, only your copy is a reference.
ln -s /path/to/apps /Applications
The problem I had with this approach is that an update from Apple (don't remember if it was the 10.5.3 or 10.5.4) blew away the alias and overwrote it with a new applications folder in order to install updates to some of the apps in Utilities.
In response to the comments about just throwing in a bigger drive, I'm on a laptop with a 60G drive and I partition the drive in a way that makes my backups easy to do, but the catch is it makes my system partition smaller than I'd really like. If you've never replaced the hard drive in an iBook, look up the instructions online. It is decidedly non-trivial.
Creating aliases is easy. Select all, then drag into the other folder holding command and option.
http://en.wikipedia.org/wiki/Alias_(Mac_OS)
'Mac aliases' sound better in principle since they keep track if items move, even across disks. However they don't work with unix scripts, updaters and installers can use scripts to set files and folders up correctly. Symbolic links are a better option if you expect to be needing to run updates on the linked files etc, just don't move them around.
Moving all your applications to regain disk space is inefficient and usually unnecessary. Why not uninstall infrequently used applications, move older documents, or archive the iTunes songs you never play?
Another approach for regaining disk space is to remove the unneeded parts of universal binary applications and to remove the unneeded language and localization files. Numerous utlities can safely 'slim' applications.
I don't think you can say it's unnecessary or inefficient unless you know the workflow in use here.
If someone wants to do this because it is the way they work, and/or makes the most sense to them, I do not think anyone is qualified to tell them otherwise.
IMHO
When you see someone fumbling around potentially causing future problems for themselves, I think it's perfectly fine to tell someone to stop it.
My advice? Buy a bigger disk. There's really no excuse at today's prices. Heck, buy two and an external case and get a copy of Carbon Copy Cloner (and donate while you're at it). Throw money and hardware at the problem. It'll save you headaches later on.
I keep folders of apps elsewhere because I like them organized by purpose. For example, I have all my font apps in one folder, etc. The reason for not doing this in the Applications folder is because that folder is already cluttered. In my case, I have over 100 items in /Applications, and about 300 apps altogether.
I tend to do things the other way around: I put aliases to the apps that are in my /Applications folder, in the folders that are sorted by category.
I install in default locations, because often (I'm sure you've found) Applications are so poorly written they don't work if they live anywhere else.
But like you, I like things grouped by purpose. So I have a Games folder inside Applications, containing Finder Aliases to the Games. I have a Fonts folder for font-manipulation programs. I have one called Graphics, another called Browsers, then Music and Movie.
Using aliases this way means I can have VLC appear in both Music and Movie.
It's the 'Gmail' approach to applications. Tag, don't file.
I've never had an app not work because I've installed it somewhere other than the default Applications folder. (But I should add that apps which have installers, I always use with the default install location. But the vast majority of apps are drag-and-drop install.)
That depends on what apps you use, and what apps I use. They differ, of course. Many of the apps I use insist on the /Applications folder. Many of them are not drag-and-drop installs. I wish all of them were drag-and-drop, and could run from any folder I choose. I prefer that and appreciate it as a useful, important feature. It's one of the things that tips the balance for me when comparing apps.
cd /Applications
sudo chflags hidden iTunes.app
Then create a subdirectory, such as /Applications/Digitial Media, and make a symbolic link, eg:
ln -s /Applications/iTunes.app /Applications/Digital Media/.
Then the icon shows up in the finder in the subdirectory but not the main directory, and will be unaffected by updates. (I would slightly prefer to make a symbolic link in the other direction, and make the symbolic link itself invisible, but that doesn't seem to work -- but it does work for Mac-style aliases, which may or may not be problematic).
The spaces need to be escaped or to have quotes around them. The escapes I added disappeared.
It works in Linux just fine.
Yeah, I came back to this post to ask why it doesn't work in Linux. Or maybe just what exactly doesn't work.
I have symlinked whole folders of files before. I have symlinked applications a bunch. Not sure what the real problem is here.
AppFresh scans all the drives on my computer, with no links needed.
Several tools are available for Macintosh System Administrators, mostly in the form of command-line shell scripts to be run from the Terminal application. Please read the comments in each script for descriptions and directions.
Running BOINC as a daemon or system service
Make_BOINC_Service.sh is a command-line shell script to set up the BOINC Client to run as a daemon at system startup. It can be used with either full GUI installations (BOINC Manager) or the stand-alone BOINC Client. (If you don't use the boinc daemon that came with the GUI installation, you should check the /Library/LaunchDaemons/edu.berkeley.boinc file that the Make_BOINC_Service.sh script generates for double slashes (//) and remove them if necessary.)
When run as a daemon:
- The BOINC Client always runs even when no user is logged in. However, it still observes the Activity settings as set by the Manager or the boinc_cmd application (Run always, Run based on preferences, Suspend, Snooze; Network activity always available, Network activity based on preferences, Network activity suspended.)
- Quitting the BOINC Manager will not cause the Client to exit.
- Most projects have upgraded their graphics to version 6 and will display graphics properly on BOINC version 6.2 and later even when running as a daemon. However, older style (version 5) application graphics (including screen saver graphics) are not available when the Client runs as a daemon.
- The BOINC Client may not successfully detect the presence of a GPU, so BOINC Project applications may not be able to use the GPU.
- The following apply to the full GUI installation (BOINC Manager):
- You may need BOINC version 6.2 or later to work properly as a daemon.
- Normally, BOINC Manager starts up automatically when each user logs in. You can change this as explained below.
- If you wish to block some users from using BOINC Manager, move it out of the /Applications directory into a directory with restricted permissions. Due to the Manager's internal permissions, you can move it but cannot copy it. See Client security and sandboxing for more information.
Disabling auto-launch of BOINC Manager
By default, BOINC Manager starts up automatically when each user logs in. You can override this behavior by removing the BOINC Manager Login Item for selected users, either via the Accounts System Preferences panel or by creating a nologinitems.txt file in the BOINC Data folder. This should be a plain text file containing a list of users to be excluded from auto-launch, one user name per line.
An easy way to create this file is to type the following in terminal, then edit the file to remove unwanted entries:
After creating this file, run the installer. The installer will delete the Login Item for each user listed in the file. Entries which are not names of actual users are ignored (e.g., Shared, Deleted Users.)
Using BOINC's security features with the stand-alone BOINC Client
Beginning with version 5.5.4, the Macintosh BOINC Manager Installer implements additional security to protect your computer data from potential theft or accidental or malicious damage by limiting BOINC projects' access to your system and data, as described in Client security and sandboxing. We recommend that stand-alone BOINC Client installations also take advantage of this protection. You can do this by running the Mac_SA_Secure.sh command-line shell script after installing the stand-alone Client, and again any time you upgrade the Client.
Although we don't recommend it, you can remove these protections by running the Mac_SA_Insecure.sh script.
Moving BOINC Manager or BOINC Data Folder to a Different Drive
It is possible to run BOINC on the Mac with the BOINC Manager application or the BOINC Data folder on a drive other than the boot drive. This is complicated a bit by the need to set up the special permissions for BOINC's sandbox security, but it can be done. These instructions are provided with no warranty; use them at your own risk.
Mac Os Symbolic Link
Here are instructions for moving both the application and the data (you can move either or both):
Shortcut: instead of typing a path in the Terminal application, you can drag a folder or file from a Finder window onto the Terminal window. If you do this, omit the quotation marks around the path!
[1] Quit BOINC.
[2] If you only want to move the BOINC Manager application, skip to step [4].
Mac Create Symbolic Link Applications
Copy the BOINC Data directory from the '/Library/Application Support/' directory to the desired drive. Rename the original BOINC Data directory or move it to a different directory on your boot drive as a backup safety measure. In any case, you must now not have a '/Library/Application Support/BOINC Data' directory before the next step.
Brytewave app for mac. With the new Destiny Quest mobile app, students can search and access library resources in a way like never before-from their iOS or Android mobile devices. Which means they can now find learning resources they need anytime, even after the school day ends. Plus it gives media specialists and teachers access to navigate the library and plan lessons, assignments and activities.
[3] Create a symbolic link to the new BOINC Data directory in place of the old one. Enter the following in the Terminal application:
Substituting your new path for {newDataPath}; for example: '/Volumes/newDrive/myData'.
[4] If you only want to move the BOINC Data, skip to step [5].
Copy BOINCManager.app from '/Applications/BOINCManager.app' to the desired drive, and move the original into the trash. (The Finder may not show the filename extension '.app').
Create a symbolic link to the new copy in place of the old one. Enter the following in the Terminal application:
Symbolic Link In Mac
Substituting your new path for {newAppPath}; for example: '/Volumes/newDrive/myApps'
[5] IMPORTANT: you must create symbolic links. Macintosh aliases created with the Finder will not work!
Run the script Mac_SA_Secure.sh to set up proper permissions at the new locations. Enter the following in the Terminal application:
where {newDataPath} is as above and {path} is the path to the Mac_SA_Secure.sh script. (As before, you can drag the Mac_SA_Secure.sh file from a Finder window onto the Terminal window instead of typing its path.)
[6] Relaunch BOINC.
IMPORTANT: Each time you run the installer, you will need to repeat this. You may also need to repeat it after upgrading to a new version of Mac OSX. The installer will replace the symbolic link to the Manager with the new Manager, and will replace the symbolic link to the BOINC Data directory with a new initialized BOINC Data directory with no projects attached. You must:
- cancel out of the 'Attach to Project' dialog
- quit BOINC
- move that new initialized BOINC Data directory to the trash
- repeat steps [2] through [4].
Note: according to this discussion, the target drive must have 'Owners Enabled' set.
For safety, always make a backup copy of your BOINC Data before performing these steps.
Selecting which users may run BOINC Manager
Due to new restrictions imposed by OS 10.6 Snow Leopard, there has been a change in BOINC's security implementation. Non-administrative users can no longer run BOINC Manager unless they are added to group boinc_master.
As of BOINC 6.10.5, the BOINC installer asks whether or not you wish to add all non-admin users to group boinc_master. (As before, the installer automatically adds all users with administrative privileges [i.e., users who are members of group admin] to group boinc_master.)
If you need more selective control over which users should be in group boinc_master, you can use the command-line tool AddRemoveUser.
To access the information, hold down the Option (Alt) key on the keyboard and click the Apple logo in the menu bar at top of the screen. Then select System Information. In the new window, click on Applications under Software in the left sidebar. Click the 'Finder' icon in the Dock. Step 2 Select 'Applications' from the Favorites section in the Finder window that opened automatically. Alternatively, select the 'Go' menu and choose 'Applications' from the drop-down list. How to find list of apps on mac desktop.
To add user1, user2 and user3 to group boinc_master, enter the following in the Terminal application:
where {path} is the path to the AddRemoveUser application.This also sets a login item for each specified user so that BOINC Manager will start automatically when that user logs in.
You can also use:
This is the same as the -a option and also sets BOINC as the screensaver for the specified users.
To remove user1, user2 and user3 from group boinc_master, enter the following in the Terminal application:
This also removes the BOINCManager login item for each specified user. If any of the specified users had BOINC set as their screensaver, it will change their screensaver to Flurry.
Installing BOINC on a Mac using the command line
In some situations, such as remote or automated installs, it is more convenient to install BOINC Manager via the command line instead of the GUI. But there is no way to respond to dialogs during a command-line install.
Apple's command-line installer sets the following environment variable:
The postinstall script, postupgrade script, and this Postinstall.app detect this environment variable and do the following:
- Redirect the Postinstall.app log output to a file /tmp/BOINCInstallLog.txt.
- Suppress the 2 dialogs (asking whether to allow non-admin users to manage BOINC and whether to use the BOINC screensaver.)
- test for the existence of a file /tmp/nonadminusersok.txt; if the file exists, allow non-administrative users to run BOINC Manager.
- test for the existence of a file /tmp/setboincsaver.txt; if the file exists, set BOINC as the screensaver for all BOINC users.
The BOINC installer package to be used for command line installs can be found embedded inside the GUI BOINC Installer application at:
Example: To install on a remote Mac from the command line, allowing non-admin users to run the BOINC Manager and setting BOINC as the screensaver:First SCP the 'BOINC.pkg' to the remote Mac's /tmp directory, then SSh into the remote Mac and enter the following: