system/xen: Updated for version 4.1.1.

Signed-off-by: Niels Horn <niels.horn@slackbuilds.org>
This commit is contained in:
mario 2011-08-09 09:44:28 -03:00 committed by Niels Horn
parent 1f932a0883
commit 7265cfa85a
4 changed files with 7 additions and 7 deletions

View file

@ -34,10 +34,10 @@ and Xen VMM, and packages them up as a single file that looks like a bzImage
Linux kernel. For example this is how mbootpack works:
# cd /boot
# gzip -d -c /boot/xen-4.1.0.gz > /boot/xen-4.1.0
# gzip -d -c /boot/xen-4.1.1.gz > /boot/xen-4.1.1
# gzip -d -c /boot/initrd-xen.gz > /boot/initrd-xen
# mbootpack -o /boot/vmlinuz-2.6.34.7-xen -m /usr/src/linux-2.6.34.7-xen/vmlinux \
-m /boot/initrd-xen /boot/xen-4.1.0
-m /boot/initrd-xen /boot/xen-4.1.1
After a new kernel image is created, add something like the folowing to lilo.conf:

View file

@ -12,7 +12,7 @@ VERSION=${VERSION:-2.6.34.7}
SVERSION=${SVERSION:-2.6.34-6}
# Xen version
XVERSION=${XVERSION:-4.1.0}
XVERSION=${XVERSION:-4.1.1}
BOOTLOADER=${BOOTLOADER:-lilo}

View file

@ -23,7 +23,7 @@
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
PRGNAM=xen
VERSION=${VERSION:-4.1.0}
VERSION=${VERSION:-4.1.1}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}

View file

@ -1,8 +1,8 @@
PRGNAM="xen"
VERSION="4.1.0"
VERSION="4.1.1"
HOMEPAGE="http://www.xen.org/"
DOWNLOAD="http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz"
MD5SUM="db3e1542b7719f375593b2b32b01a177"
DOWNLOAD="http://bits.xensource.com/oss-xen/release/4.1.1/xen-4.1.1.tar.gz"
MD5SUM="fab4bf74d73444ff9b43bced2e4fc5a2"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
MAINTAINER="mario"