Re: can we (fully) fix/integrate NetworkManager (preferred) or release-goal its decommissioning
- To: Serge <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: can we (fully) fix/integrate NetworkManager (preferred) or release-goal its decommissioning
- From: Wouter Verhelst <firstname.lastname@example.org>
- Date: Sun, 2 Sep 2012 09:33:36 +0200
- Message-id: <[🔎] 20120902073336.GA29563@grep.be>
- In-reply-to: <CAOVenEqgMO76fz-cCrPNC0rmi5hDCy7TkR6qs+h0SsKNXMR8jg@mail.gmail.com>
- References: <email@example.com> <firstname.lastname@example.org> <20120820000453.2ac64f9c@ileemo> <email@example.com> <20120824104411.4ff17b1a@ileemo> <20120830201911.GC14077@grep.be> <CAOVenEqgMO76fz-cCrPNC0rmi5hDCy7TkR6qs+h0SsKNXMR8jg@mail.gmail.com>
On Fri, Aug 31, 2012 at 09:28:11PM +0300, Serge wrote:
> 2012/8/30 Wouter Verhelst wrote:
> >> How do you suppose it's possible to undo arbitrary network
> >> configuration done by arbitrary set of tools when there's no central
> >> place to hold such information (and can't possibly be)?
> > Actually, the kernel holds that information. Any tool can just query the
> > kernel for information, and decide what to do with what's returned.
> Not sure. Will it work for user-space configuration too? I.e. `ifdown`
> may have have to stop `dhclient` and `wpa_supplicanf`. Is it possible
> to detect such cases automatically?
At the very least it's possible to detect that "a" dhclient or wpa supplicant
is running. As to which interface they're dealing with, that may require
tool-specific code (which would be the case anyway, for other reasons).
I'm not sure, I haven't gotten that far yet :-)
The volume of a pizza of thickness a and radius z can be described by
the following formula:
pi zz a