This bug still exists in Jaunty, but now adding to interfaces:
auto eth0
iface eth0 inet dhcp
doesn't fix it.....
I first tried adding eth0 to my /etc/network/interfaces file ....and that did nothing, then I tried messing with the boot order (in /etc/rc5.d I noticed that mediatomb was K20 and that NM was later, so I switched mediatomb to K55) but that did nothing ......put everything back to normal and just start it manually each reboot
So the question here is.....what changed in Jaunty, what is the actual process that starts networking before the gui, and where do I find it ......mediatomb is a really great app....this really seems like it should be easy to fix (apart from the network before gui things of course) ......maybe the easy solution is to have it start after the gui starts??
This bug still exists in Jaunty, but now adding to interfaces:
auto eth0
iface eth0 inet dhcp
doesn't fix it..... interfaces file ....and that did nothing, then I tried messing with the boot order (in /etc/rc5.d I noticed that mediatomb was K20 and that NM was later, so I switched mediatomb to K55) but that did nothing ......put everything back to normal and just start it manually each reboot
I first tried adding eth0 to my /etc/network/
So the question here is.....what changed in Jaunty, what is the actual process that starts networking before the gui, and where do I find it ......mediatomb is a really great app....this really seems like it should be easy to fix (apart from the network before gui things of course) ......maybe the easy solution is to have it start after the gui starts??