> in finish-install /e/n/i will never be properly populated for a wireless > installation without network-manager, although I think ifupdown would be > capable to do this (not tested, but have a look at > https://anonscm.debian.org/cgit/d-i/netcfg.git/tree/write_interface.c). > I guess the justification is that people using wireless usually would > want a GUI to roam between networks, and a interface stanza would > prevent even a (later installed) network-manager from touching the > interface.
That makes sense. Maybe it could still output commented-out configuration into /e/n/i, to make it easier in case people do end up editing the file to set up their network, for whatever reason. > a) go for Cyril's suggestion and just install rdnssd in finish-install > if network-manager is not getting installed there (but honestly I have > no idea of the netcfg code base) > b) drop the Conflicts and make the rdnssd merge-hook a no-op if > network-manager is installed/running. I think trying to manage this conflict between two basic packages is asking for trouble. rdnssd doesn't depend on /usr, I think in some cases it can still be beneficial for bootstrap when network-manager might not be available. There is already a distro-specific patch for /etc/rdnssd/merge-hook to add a resolvconf by-pass, another one could be added checking if network-manager is installed/available/running/in charge of /etc/resolv.conf. I've never used network-manager personally so I wouldn't quite know what's best to check exactly. -- Pierre Ynard "Une âme dans un corps, c'est comme un dessin sur une feuille de papier."
