Chris Knadle <chris.kna...@coredump.us> writes: > - Furthermore my experience has been that disabling NM via modifying the > init script (i.e. the "exit 0" suggestion which came up on [debian-devel], > or making the init script non-executble) only works until NM is upgraded, > whereby the init script is replaced and thus the NM daemon starts again -- > which on Sid happens fairly regularly.
The correct way to disable network-manager, or any other init script in Debian, is: update-rc.d <script-name> disable This will be preserved on upgrades. > - Wishlist bug #685742 [1] suggested a way to disable NM permanently via a > /etc/default/<package> file (like wicd comes with) but was outright > rejected, in favor of instead using "update-rc.d network-manager disable" > -- the latter of which isn't mentioned anywhere in the documentation that > comes with NM. That's understandable since it has nothing specific to do with network-manager; rather, it's a standard interface in Debian for any init script. Most of the /etc/default hacks to disable daemons predate the standardization of the enable/disable interface in update-rc.d, or at least its widespread publication. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org