summaryrefslogtreecommitdiffstats
path: root/loader
diff options
context:
space:
mode:
authorDavid Cantrell <dcantrell@redhat.com>2008-10-10 14:13:21 -1000
committerDavid Cantrell <dcantrell@redhat.com>2008-10-10 14:15:24 -1000
commita5252151d4c13c7218c7a624548635f8408c091b (patch)
tree65c7385321bade616ac33bc1b084296fca1b0400 /loader
parentd8b0572b4f26ee5e07f8b02842022471c8ac8ed4 (diff)
downloadanaconda-a5252151d4c13c7218c7a624548635f8408c091b.tar.gz
anaconda-a5252151d4c13c7218c7a624548635f8408c091b.tar.xz
anaconda-a5252151d4c13c7218c7a624548635f8408c091b.zip
Write NM_CONTROLLED=yes rather than NM_CONTROLLED=
I was told by upstream that NM_CONTROLLED= should be sufficient for nm-system-settings to pick up an interface for control. But the parsing in the ifcfg-fedora plugin for nm-system-settings is a little strange (shvar.c) and what happens when NM_CONTROLLED is empty isn't entirely clear. Set it to yes to avoid any possible problems.
Diffstat (limited to 'loader')
-rw-r--r--loader/net.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/loader/net.c b/loader/net.c
index 8d920a95a..01dfd6f4b 100644
--- a/loader/net.c
+++ b/loader/net.c
@@ -1141,7 +1141,7 @@ int writeEnabledNetInfo(iface_t *iface) {
fprintf(fp, "DEVICE=%s\n", iface->device);
fprintf(fp, "HWADDR=%s\n", iface_mac2str(iface->device));
fprintf(fp, "ONBOOT=yes\n");
- fprintf(fp, "NM_CONTROLLED=\n");
+ fprintf(fp, "NM_CONTROLLED=yes\n");
if (!FL_NOIPV4(flags)) {
if (iface->ipv4method == IPV4_DHCP_METHOD) {