Port from rhel6-branch.
Resolves: rhbz#668395
No matter whether it has the new --activate flag set.
For network installs restores common rhel 5 and master behaviour.
For non-network installs it restores master's behaviour
which is to activate the device. Rhel 5 behaviour (don't
bring the device up for non-network installs) will be
restored by following patch.
---
loader/kickstart.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/loader/kickstart.c b/loader/kickstart.c
index 6f9f831..a09970c 100644
--- a/loader/kickstart.c
+++ b/loader/kickstart.c
@@ -854,7 +854,8 @@ static void setKickstartNetwork(struct loaderData_s * loaderData, PyObject *hand
}
attr = getObject(ele, "activate", 0);
- if (isTrue(attr)) {
+ /* Always activate first network command device (RHEL 5 behaviour) */
+ if (isTrue(attr) || !i) {
logMessage(INFO, "activating because --activate flag is set");
activateDevice(loaderData, &iface);
} else {
--
1.7.2
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
