[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] SUSE has sensible use of ifup nowadays

While wading through the patches made to Xen by OpenSUSE in their
[s]rpm, I found that they have removed various special casing for ifup
on ther distribution.

We should do likewise.  This change should be included in the next
xen-unstable, NOT in 3.2.  By then we hope that SLES et al have also
been updated.

The patch below is not derived directly from the OpenSUSE package,
since the OpenSUSE patch deleted the attempt to cope with Gentoo.


Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

diff -r 2491691e3e69 tools/examples/xen-network-common.sh
--- a/tools/examples/xen-network-common.sh      Sat Dec 29 17:57:47 2007 +0000
+++ b/tools/examples/xen-network-common.sh      Mon Jan 14 15:45:36 2008 +0000
@@ -16,11 +16,6 @@
-# On SuSE it is necessary to run a command before transfering addresses and
-# routes from the physical interface to the virtual.  This command creates a
-# variable $HWD_CONFIG_0 that specifies the appropriate configuration for
-# ifup.
 # Gentoo doesn't have ifup/ifdown, so we define appropriate alternatives.
 # Other platforms just use ifup / ifdown directly.
@@ -32,17 +27,7 @@
 #           that the virtual device will take once the physical device has
 #           been renamed.
-if [ -e /etc/SuSE-release ]
-  preiftransfer()
-  {
-    eval `/sbin/getcfg -d /etc/sysconfig/network/ -f ifcfg- -- $1`
-  }
-  ifup()
-  {
-    /sbin/ifup ${HWD_CONFIG_0} $1
-  }
-elif ! which ifup >/dev/null 2>/dev/null
+if ! which ifup >/dev/null 2>/dev/null
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.