After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728802 - docs: document differences between ifcfg-rh and initscripts sysconfig.txt
docs: document differences between ifcfg-rh and initscripts sysconfig.txt
Status: RESOLVED DUPLICATE of bug 683111
Product: NetworkManager
Classification: Platform
Component: Documentation
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-04-23 15:38 UTC by Dan Williams
Modified: 2014-08-29 10:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dan Williams 2014-04-23 15:38:01 UTC 
We should include some documentation about the differences between the NM interpretation of ifcfg files and how the old RH initscripts interpret them.

PEERDNS is one example; 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".

We should document the additional WiFi and 802.1x keys too.

My suggestion for this would be a docs XML file in src/settings/plugins/ifcfg-rh/ which is pulled in by docs/api/ into a new "settings plugins and configuration" docs section, where we could also put documentation of the 'keyfile' format.
Comment 1 Jiri Klimes 2014-08-29 10:37:52 UTC 
The documentation is handled in bug 683111 that takes care of both 'keyfile' and 'ifcfg-rh' plugins.

*** This bug has been marked as a duplicate of bug 683111 ***