On 12/11/05, <b class="gmail_sendername">Jordack</b> <<a href="mailto:jordack@yahoo.com">jordack@yahoo.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I don't remember why. I set it all up a while ago and<br>I think there was a reason. It was only a minor<br>nuisance so I never tried to play with it.<br><br>Guess Ill take another look at it, if I can ever get<br>the girlfriend to stop watching her Buffy recordings
<br><br><br>--- Jake <<a href="mailto:jakeisawake@gmail.com">jakeisawake@gmail.com</a>> wrote:<br><br>> On 12/11/05, Jordack <<a href="mailto:jordack@yahoo.com">jordack@yahoo.com</a>> wrote:<br>> i think samba only supports a 2gig file size. newer
<br>> versions of nfs<br>> should be able to get around the 2gig limit but you<br>> may need a mount<br>> option to force to use nfsv3 i think.<br>><br>> in any case, why are you mounting the recorded stuff
<br>> on the FE? why<br>> not just let myth do what it does best and stream<br>> the files. seems<br>> the easiest solution to me.</blockquote></div><br>
<br>
I have mine mounted so I can use nuvexport on both machines.<br>
<br>
I thought Myth always did it's own streaming, regardless of whether the
backend drive is mounted somehow. Unless there's something I
don't know, the filesize limits shouldn't be an issue, right?<br>
<br>
<br>