Jump to content
10 posts in this topic

Recommended Posts

BEWARE: storing apps is very different to storing files. Apps often rely on software libraries located elsewhere in the filesystem tree. Provided you specify the right flags when you compile the apps you should be okay. If you don't, your apps may not run.

 

For example, suppose an app needs the library 'libcss' in /usr/lib/. It will look for it in /usr/lib/ but won't find it because it's actually in /name_of_directory_containing_HFS+_mount/usr/lib/.

 

You can fix this, of course, by making a link in /usr/lib (ie. /usr/lib/libcss) to /name_of_directory_containing_HFS+_mount/usr/lib/libcss. Depending upon how may situations like this occur, you may have a few links to make or many links to make to get the app working. This can be avoided, of course, if you compile the app with the appropriate directory 'flags' in the first place.

 

Alternatively, you could chroot your user into /name_of_directory_containing_HFS+_mount but then you're trapped from there on in. Depending upon what app you're running this may not be a problem, but if you want to run other apps which are located on your linux drive, you're snookered.

 

SAMBA, NFS, SSHFS, etc. are usually used just for file serving and rarely for serving up apps.

 

Just some things to consider. :(

You may want to consider buying a file server. Linksys and others make them. They are about the size of a router and connect to your network. You can easly access them from all your computers.

×
×
  • Create New...