[07:16] <dekarl> How about /etc/init/mythtv-backend waiting for net-device-up eth0?
[07:21] <dekarl> when waiting for the loopback device the static ip is up 5 seconds to late to allow the backend to bind to it... (doesn't matter if ifts static dhcp or static manual configuration)
[07:30] <dekarl> tgm4883: I've just verified that waiting for "net-device-up IFACE=eth0" instead of "IFACE=lo" fixes my issues with a dud backend after a system restart.
[14:06] <mrand> qwebirc76614: It's been long enough that I don't remember the steps I had to take.  There were a few, but they were not difficult to figure out.  make sure you have ALSA >= 1.0.24.  There is a ppa if you don't.  Check that alsamixer is unmuted for your device.
[18:26] <tgm4883> So I apparently lost the email from whoever was going to help me with mythbuntu-bare once it got into 11.10. If you were planning on helping me with that please send me a quick email
[18:48] <dekarl> tgm4883: What do you think about letting the backend start after the network?
[18:49] <tgm4883> dekarl, it should do that already?
[18:49] <dekarl> no :( it's waiting for loopback being setup which is 5-10 seconds before eth0 gets up and configured...
[18:50] <dekarl> the master backend can't bind it's ip that way. binding * would work though
[18:50] <tgm4883> dekarl, I thought we waited for networking to finish loading?
[18:50] <tgm4883> superm1, ^
[18:51] <superm1> hm
[18:51] <rhpot1991> I thought it waits for network
[18:51] <superm1> how about instead telling the backend to bind to the new interface as it comes up?
[18:51] <superm1> i thought it did wait thus far though too
[18:51] <dekarl> I'm talking about an up to date 11.04 installation using that upstart and NetworkManager
[18:51] <dekarl> the start script explicitly waits for IFACE=lo
[18:52] <rhpot1991> no he is right
 the start script explicitly waits for IFACE=lo
[18:52] <rhpot1991> grrr
[18:52] <rhpot1991> start on (local-filesystems and net-device-up IFACE=lo and started udev-finish)
[18:52] <superm1> but if we don't make that IFACE=lo what happens if they have a wireless card that doesn't associate?
[18:53] <tgm4883> what it we waited for networking instead of net-device-up
[18:53] <rhpot1991> can't we do something like start on started networking?
[18:53] <tgm4883> networking-finish or something
[18:53] <dekarl> superm1, that's a good question.
[18:53] <superm1> i think it's going to require some additional investigation and or recomendations from upstart folk
[18:54] <rhpot1991> I have start on started networking in a script on my server, but I'm also not convinced it works
[18:54] <tgm4883> superm1, from the cookbook
[18:54] <tgm4883> start on (starting network-interface
[18:54] <tgm4883>           or starting network-manager
[18:54] <tgm4883>           or starting networking)
[18:54] <rhpot1991> tgm4883 wins
[18:54] <superm1>  i don't believe that will win
[18:55] <superm1> because network-manager starting doesn't mean the interface is up
[18:55] <tgm4883> i'm assuming we could also do something like "finished networking"
[18:55] <superm1> what if network-manager comes up first?
[18:55] <tgm4883> superm1, well that was an example, couldn't we do "finished network-interface"
[18:55] <superm1> i'm not sure
[18:55] <superm1> i don't believe i've seen any other jobs doing that
[18:55] <tgm4883> so we are pioneers!
[18:56] <superm1> haha,
[18:56] <tgm4883> I can test that a little later, but I need to eat lunch first
[18:56] <tgm4883> or I'll get grouchy
[18:56] <dekarl> me, my significant other didn't opt in for pioneering upstart and networkmanager ;)
[18:58]  * tgm4883 lunch
[21:47] <mrand> Might get even more interesting if there is more than one network.
[21:47] <mrand> And the one that myth cares about isn't the one that comes up.