View Single Post
Old 01-19-2008, 10:51 PM   #1
wallcraft
reader
wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.wallcraft ought to be getting tired of karma fortunes by now.
 
wallcraft's Avatar
 
Posts: 6,977
Karma: 5183568
Join Date: Mar 2006
Location: Mississippi, USA
Device: Kindle 3, Kobo Glo HD
softlinks via manifest.xml

Last week there was a post to i to i blog about: how to easily access content on the external memory. In internal memory, it involves adding a subdirectory containing just a manifest.xml such as:
Code:
<package>
  <symlink>/mnt/cf/books</symlink>
</package>
The subdirectory then shows up as a standard directory in the contentlister, which will take you to the CF card. If this is all you do, the link shows up in contentlister as "books", rather than "/mnt/cf/books", so this could be confusing if you had several external media types. The post suggests fixing this by adding a manifest.xml to your /mnt/cf/books directory, so that it shows up as "Books on CF card". I would rather have a technique for distinguishing between the symlink and the actual directory, but this does seem to be a viable method for setting up symlinks to directories - providing having them only work in the contentlister is ok.
wallcraft is offline   Reply With Quote