Hi, o1bigtenor via Dng writes:
> On Wed, May 26, 2021 at 1:26 AM Didier Kryn <k...@in2p3.fr> wrote: >> >> Le 25/05/2021 à 21:43, Mason Loring Bliss a écrit : >> > I've been managing network connections on my laptop by hand, and I was just >> > thinking that I'd like it to bring up its NICs automatically if it's >> > plugged in, but I didn't want to use ifplugd for various reasons, and >> > anyway, I like ifupdown and I want to stick with it. >> >> There's no contradiction between ifupdown and ifplugd; they work >> well together. I have been using both for decades. What I exclude is >> network-manager. >> > Hmmmmmm - - - - - why exclude network-manager? > > (just wanting to understand.) That's a good thing, wanting to understand. For me, network-manager (and wicd as well) just got in my way. They did not want to play by *my* rules. On top of that, it/they bloat my system with additional dependencies. I have found that the combination of ifupdown, netplug and wpasupplicant and a bit of tinkering with /etc/network/interfaces and a configuration file for wpa_supplicant satisfies my needs. If using network-manager (or wicd) satisfies your needs, that's fine but you may want to look into using something less "My way, or the highway!" and less bloated. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng