Blame SOURCES/0122-new_dhcp_next_server-is-really-new_next_server.patch

a56a5e
From 99ed45c2181819be473ae275bbf88df556cdff1c Mon Sep 17 00:00:00 2001
966cef
From: "Brian C. Lane" <bcl@redhat.com>
966cef
Date: Wed, 5 Feb 2014 12:10:39 -0800
966cef
Subject: [PATCH] new_dhcp_next_server is really new_next_server
966cef
966cef
The variable that dhclient sets doesn't have dhcp in the name. This
966cef
could cause problems with setups where the server is not the same as the
966cef
dhcp server.
966cef
---
966cef
 modules.d/95nfs/nfs-lib.sh | 2 +-
966cef
 1 file changed, 1 insertion(+), 1 deletion(-)
966cef
966cef
diff --git a/modules.d/95nfs/nfs-lib.sh b/modules.d/95nfs/nfs-lib.sh
1755ca
index f5fc56d7..9ced2e69 100755
966cef
--- a/modules.d/95nfs/nfs-lib.sh
966cef
+++ b/modules.d/95nfs/nfs-lib.sh
966cef
@@ -97,7 +97,7 @@ nfsroot_from_dhcp() {
966cef
     [ -z "$path" ] && [ "$(getarg root=)" == "/dev/nfs" ] && path=/tftpboot/%s
966cef
     [ -z "$server" ] && server=$srv
966cef
     [ -z "$server" ] && server=$new_dhcp_server_identifier
966cef
-    [ -z "$server" ] && server=$new_dhcp_next_server
966cef
+    [ -z "$server" ] && server=$new_next_server
966cef
     [ -z "$server" ] && server=${new_root_path%%:*}
966cef
 }
966cef