Difference between revisions of "Symlink Applications"
Jump to navigation
Jump to search
Hopspitfire (talk | contribs) |
Hopspitfire (talk | contribs) |
||
Line 28: | Line 28: | ||
An app with an internal symlink will not be able to be stored in /media/internal at this time, since it is a vfat filesystem. | An app with an internal symlink will not be able to be stored in /media/internal at this time, since it is a vfat filesystem. | ||
− | === | + | === Alternatively=== |
The same effect can be had by modifying /etc/palm/luna.conf by appending the **ApplicationPath** with the new location. | The same effect can be had by modifying /etc/palm/luna.conf by appending the **ApplicationPath** with the new location. | ||
Revision as of 17:09, 22 July 2009
It is possible to place applications in alternate locations (eg /media/internal) and symlink them to the appropriate application folder (eg /usr/palm/applications or /var/usr/palm/applications).
symlink creation from the command-line
ln -s [application directory] [symbolic link to directory]
For example:
ln -s /media/internal/apps/com.pregame.app.flashlight/ /var/usr/palm/applications/com.pregame.app.flashlight
symlink deletion from the command-line
rm [link]
For example:
rm /var/usr/palm/applications/com.pregame.app.flashlight
This will only delete the link, not the symlinked files.
Notes
An app with an internal symlink will not be able to be stored in /media/internal at this time, since it is a vfat filesystem.
Alternatively
The same effect can be had by modifying /etc/palm/luna.conf by appending the **ApplicationPath** with the new location.
For example:
ApplicationPath=/usr/lib/luna/applications:/var/luna/applications:/var/usr/lib/luna/applications:/usr/palm/applications:/var/usr/palm/applications:/media/internal/apps