[Pkg-utopia-maintainers] Bug#743138: Bug#743138: Bug#743138: [Needs upstream 0.9.10 release] Please only enable ifupdown plugin when ifupdown installed

[Michael Biebl]

Hi Guus

Am 26.02.19 um 22:10 schrieb Guus Sliepen:
> On Tue, Feb 26, 2019 at 07:24:27PM +0100, Michael Biebl wrote:
> 
>> On Sun, 10 Feb 2019 11:03:55 +0100 Andrej Shadura
>> <andrew.shadura at collabora.co.uk> wrote:
>>
>>>> this is fixed a while ago.
>>>>
>>>> Handling of hostname moved from the settings plugin to NMSettings.
>>>> Also, hostnamed is supported as one of several options.
>>>>
>>>> There were many changes there, so I am not going to hunt down for a particular BZ which fixed this. However, the functionality is now all in https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/nm-settings.c
>>
>> Andrej, I'm fine with dropping ifupdown from the default NM
>> configuration if the ifupdown package is going to ship such a config
>> snippet for NM.
> 
> Are we talking about /etc/NetworkManager/dispatcher.d/01-ifupdown here?
> It seems like a hack to avoid having to update some packages to directly
> support NetworkManager. For the long run, it's probably better if we
> don't have this dependence on scripts written for ifupdown.

No, we are talking about the ifupdown plugin in NM, i.e.
/usr/lib/*/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown.so

which is responsible for parsing /etc/network/interfaces (and depending
on whether managed=true or false, simply ignores interfaces configured
in /e/n/i or tries to apply the configuration set there)

This plugin is currently activated in
/etc/NetworkManager/NetworkManager.conf via

[main]
plugins=ifupdown,keyfile

and also contains

[ifupdown]
managed=false


The suggestion is, to change the NetworkManager.conf to
drop ifupdown from the default config.

The ifupdown package in turn would ship a config snippet
like say /usr/lib/NetworkManager/conf.d/ifupdown.conf which contains

[main]
plugins=ifupdown

There is also this bit in NetworkManager.conf, which is ifupdown plugin
specific

[ifupdown]
managed=false

I'm not sure whether this should be moved to such a ifupdown.conf file.
This is a setting users might actually change, so should be in /etc/

ifupdown could ship the file as /etc/NetworkManager/conf.d/ifupdown.conf
This would have the downside, that the ifupdown plugin would still be
active if the ifupdown package is removed, but not purged.

Another possible approach could be to have both, i.e.
/usr/lib/NetworkManager/conf.d/ifupdown.conf containing

[main]
plugins=ifupdown

and /etc/NetworkManager/conf.d/ifupdown-managed.conf

[ifupdown]
managed=false

Not sure. Thoughts?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-utopia-maintainers/attachments/20190226/94149b1b/attachment.sig>