On 2016/04/26 at 17:07, Thomas Haller wrote:
On Mon, 2016-04-25 at 17:47 +0800, Hangbin Liu wrote:
> cc Daniel and network manager development team. They are experts on
> On Mon, Apr 25, 2016 at 04:45:23PM +0800, Baoquan He wrote:
>> Using NetworkManager or not using it can bring us so different
>> behaviours and different /etc/resolv.conf. Could you give
>> suggestion how
>> we can make decision to choose a reasonable one since kdump
>> need to cope with both of them?
Yes, NetworkManager's an initscript's interpretation differs in some
To quote `man nm-settings-ifcfg-rh`:
Semantic change of variables
NetworkManager had to slightly change the semantic for a few
· PEERDNS - initscripts interpret PEERDNS=no to mean "never touch
resolv.conf". NetworkManager interprets it to say "never add
automatic (DHCP, PPP, VPN, etc.) nameservers to resolv.conf".
The behavior you described matches the documentation.
Then dracut follows NetworkManager at this point. But dracut does dhcp after
handling nameservers in "nameserver=" and "ip=" specified by users, I
NetworkManager does dhcp first, then appends DNS1&DNS2 in the ifcfg files.
I happened to spot a dracut DNS bug caused by the above-mentioned order,
I will try to post a patch to see if can fix it to follow NetworkManager.