Karmic: stop: Unknown instance

[Tom H]

>> Normally:
>> If you have Network Manager running, networking is of no use to you

>   I had so often problems with Networkmanager (like removing my resolv.conf)
>   that I removed the package...

It removes resolv.conf because you are supposed to enter name servers
in NM's GUI screens and, anyway, if you are using DHCP and not using
NM, your resolv.conf will be overwritten by dhclient (unless you edit
dhcpd.conf).

My one big criticism of NM is that it stores its config in some
"secret" files and directories. The devs may have had their reasons to
choose to do so but I would have preferred for eth0, wlan0, etc to be
configured by NM in /e/n/i, or that editing /e/n/i or /etc/resolv.conf
be reflected in the NM GUI.


>   Anyway, I need networking, as I have to restart the network in some scripts.

I do the same thing.


>> Why the missing stop stanza? No idea but it must be by design because
>> the start stanza in "/etc/init.d/networking" calls
>> "/etc/init/networking.conf" but the stop stanza in
>> "/etc/init.d/networking" calls ifdown.

>   I actually noticed that, but it's rather inconsistent, and that means
>   that /etc/init.d scripts are not really obsolete, as it is claimed
>   elsewhere.

Very inconsistent.