Comment 47 for bug 102675

First of all, I can confirm this on Feisty, updated last night, with kernel 2.6.20-14-generic (on x86, of course).

Second of all:

"sudo update-rc.d -f networking remove" == nasty hack.
blanking out /etc/network/interfaces == nasty hack.

These scripts are here for a reason -- so you don't have to manually configure your stuff all the time.

Maybe I'm not understanding how this all works, but here's my /etc/network/interfaces:
[code]
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-conf /etc/wpa_supplicant.conf

auto wlan0
iface wlan0 inet dhcp
[/code]

Now, for people with wired connections running off of dhcp, this hack will work fine. but for people with a little more under the hood, say, atheros madwifi, or static IPs, or several other scenarios, this isn't going to work for obvious reasons -- if i empty out this file, then i'll have to manually configure wifi each time i need it, i.e. every boot. If I remove the networking script, sure, I don't have hang -- because it's not attempting to do anything with networking.

Maybe I'm being naive. I really don't know how this new NetworkManager deal works, and maybe I'm being obtuse and old-fashioned. But this is not a solution.

Steve K.