<p>Hi there</p>
<p>Has mythfs been ported to .23? The version in the ubuntu repository looks to be quite old...</p>
<p>R</p>
<p><blockquote type="cite">On 28 May 2010 19:14, "Raymond Wagner" <<a href="mailto:raymond@wagnerrp.com">raymond@wagnerrp.com</a>> wrote:<br><br><p><font color="#500050">On 05/28/10 13:34, Phil Linttell wrote:<br>
> You have the option of physically moving the file, and lea...</font></p>You shouldn't do this. Recordings should be kept in the recordings<br>
directory and keep the same recording name. If you're going to be<br>
altering the recording, you should also be using the inuseprograms table<br>
to ensure nothing else is currently using it.<br>
<p><font color="#500050"><br>> I hadn't looked at mythfs.py previously, and I admit this method makes<br>> a great deal of sense. ...</font></p><a href="http://mythlink.pl" target="_blank">mythlink.pl</a> and mythfs.py behave identically, except one uses symlinks<br>
and the other uses FuseFS. They both use a user-defined format,<br>
specified on the command line, and work off the guide data in your<br>
database. The latter has the advantage that it can pull files from<br>
remote backends, rather than only being able to use locally accessible<br>
recordings.<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</blockquote></p>