<br><br><div class="gmail_quote">On Sat, Nov 17, 2012 at 11:34 AM, Darethehair <span dir="ltr"><<a href="mailto:darethehair@gmail.com" target="_blank">darethehair@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 16/11/12 03:45 PM, Jonatan Lindblad wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Do you actually need network-manager? Is it possible for you to configure your interface in /etc/network/interfaces and instead depend on $network in your mythtv-backend init script?<br>
<br>
-- <br>
Jonatan<br>
</blockquote></div>
Yes, that probably would be another option -- but as you say it still looks like adding a dependency into 'mythtv-backend' for networking (either '$network' or 'network-manager') for Debian users. At that point, either having a delay (like I did), or hard-coded wireless network parms in '/etc/network/interfaces' would do the trick :)<br>
<br>
I remain puzzled, though, that other Debian users have not encountered the same challenge (?).<br>
<br></blockquote><div><br>I think you are waiting on a wireless connection? Not many people run their backend on wireless. <br></div></div>