Comment 12 for bug 246322

You're missing the point with laptops and so on: these are use cases that are already supported and can be broken by a poor DHCP implementation. This is especially the case if your preferred implementation with overwriting the configuration file were done - the user configuration would be unconditionally deleted if they connected to the wrong network.

Adding a "DO NOT EDIT THIS FILE" note doesn't really address the problem: it's not really compliant with policy (users should be able to do static configuration) and means that it becomes impossible to set any configuration which is not offered over DHCP. You should do something like have the DHCP configuration go in a separate file and source that from the main configuration file.