system/xen: Updated for Slackware 14.1

Signed-off-by: Robby Workman <rworkman@slackbuilds.org>

system/xen/README

@@ -12,9 +12,5 @@ mbootpack is an optional dependency.  Since booting a Xen kernel with LILO
 is not supported by default we have to use GRUB; alternatively, you can use
 mbootpack to create a LILO compatible kernel.
 
-GRUB may be installed from Slackware's extra repository. The GRUB package
-is not available from the Slackware x86_64 distribution, but the source and
-a SlackBuild may be found in its extra/source repository.
-
 See README.SLACKWARE (which is also installed with the package docs) for
 setup, configuration, and usage hints.

system/xen/README.SLACKWARE

@@ -2,12 +2,11 @@ After installing this package, in addition to the /usr/doc/xen-*/README file;
 the Xen User Manual is installed as /usr/doc/xen-*/html.
 
 Before Xen can be used, xenstored, xenconsoled and xenbackendd services must
-be started, wich must be done with rc.xencommons script.
-The rc.xend script is no longer needed if you are going to use 'xl' instead
-of 'xm'. As a matter of fact, 'xm' is marked as deprecated since Xen 4.2.
-Future versions of Xen will no longer support 'xm'.
-You may wish to add these lines to /etc/rc.d/rc.local to start this service
-after booting from your Xen kernel:
+be started, which must be done with rc.xencommons script. The rc.xend script
+is no longer needed if you are going to use 'xl' instead of 'xm'. As a matter
+of fact, 'xm' is marked as deprecated since Xen 4.2. Future versions of Xen
+will no longer support 'xm'. You may wish to add these lines to
+/etc/rc.d/rc.local to start this service after booting from your Xen kernel:
 
 if [ -d /proc/xen ]; then
   if [ -x /etc/rc.d/rc.xencommons ]; then

system/xen/dom0/README.dom0

@@ -1,21 +1,22 @@
 kernel-xen.sh: This script builds the Linux Kernel for a Xen Hypervisor.
 
 The configuration files included here are based on generic Slackware configs.
-For 32bit systems, SMP based config was used. You can run "make menuconfig"
-before compiling a Xen kernel by passing the "MENUCONFIG=yes" to the script.
+For 32bit systems, SMP based config was used. To run "make menuconfig" before
+compiling a Xen kernel, use "MENUCONFIG=yes" variable.
 
-Originaly, booting a Xen kernel with LILO bootloader is not supported, so GRUB
-has to be used. Since some of us still preffer LILO over GRUB, there is a way
-to accomplish this with mbootpack. Basicaly mbootpack takes Linux kernel, initrd
-and Xen VMM, and packages them up as a single file that looks like a bzImage
+Originally, booting a Xen kernel with LILO bootloader is not supported, so GRUB
+has to be used. Because some might preffer LILO over GRUB, there is a way to
+accomplish this with mbootpack. Basicaly, mbootpack takes Linux kernel, initrd
+and Xen VMM, and packages them up into a single file that looks like a bzImage
 Linux kernel. To select how kernel is packed use "BOOTLOADER=" variable. Valid
-options are "lilo" and "grub".
+options are "lilo" and "grub". Because generic kernel requires an initrd image,
+there are aditional variables that can be used; ROOTMOD (takes a list of
+colon-delimited modules to build into initrd), ROOTFS (takes a name of a module
+to use for root filesystem) and ROOTDEV (takes a name of root filesystem
+device).
 
-Since generic kernel requires an initrd image, there are aditional variables that
-can be used, such as ROOTMOD (list of root filesystem modules), ROOTFS (name of a
-module to use) and ROOTDEV (name of root filesystem device).
-
-After a new kernel image is created, add something like the folowing to lilo.conf:
+After a new kernel image is created, and if bootloader of choice is LILO,
+include these lines in /etc/lilo.conf:
 
 image = /boot/vmlinuz-xen
   root = /dev/sda2
@@ -26,17 +27,9 @@ image = /boot/vmlinuz-xen
 Note: everything before "--" is passed to Xen, and everything after "--" is
 passed to the Linux kernel.
 
-If for some reason LILO is not good enough, you can always use GRUB.
-GRUB may be installed from Slackware's extra repository. The GRUB package
-is not available from the Slackware x86_64 distribution, but the source
-and a SlackBuild may be found in its extra/source repository.
+For GRUB, for example, include these lines in /boot/grub/menu.lst:
 
-grubconfig that comes with Slackware's GRUB package may give a starting point
-to configure GRUB. Moreover, the Xen User Manual and its README file installed
-with the Xen package include details on which parameters to include in the GRUB
-configuration file. For example, include these lines in /boot/grub/menu.lst:
-
-title Slackware XenLinux 14.0
+title Slackware XenLinux 14.1
          root (hd0,0)
          kernel /boot/xen.gz dom0_mem=524288 console=vga
          module /boot/vmlinuz-xen root=/dev/sda2 ro console=tty0 nomodeset
@@ -44,12 +37,12 @@ title Slackware XenLinux 14.0
 
 Note that dom0_mem parameter is critical for a 32bit install.
 
-If your dom0 kernel crashes or freezes at boot, either with an automatic reboot
-or with the blank screen, here are some things to try:
+Here are some notes/guidances if your dom0 crashes, freezes or maybe the
+screen goes blank on boot:
 - Specify an out of range number to "fbcon" to disable framebuffer altogether,
-  for an example append fbcon=map:9 to the Linux kernel.
-  (To see a list of available devices in your system: cat /proc/fb)
+  which, for example, is done by appending fbcon=map:9 to the Linux kernel (To
+  see a list of available devices in your system check /proc/fb).
 - Blacklist framebuffer module from loading. This one requires a bit of
   digging arround in dmesg/lsmod to find out wich module is in use.
 - Disable framebuffer devices by setting CONFIG_FB=n in kernel config.
-- Try another VGA card (sorry).
+- Try booting with another VGA card (sorry).

system/xen/dom0/kernel-xen.sh

@@ -3,10 +3,10 @@
 # Xem dom0 kernel installation script
 
 # Written by Chris Abela <chris.abela@maltats.com>, 20100515
-# Updated by mario <mario@slackverse.org>, 2010-2013
+# Modified by Mario Preksavec <mario@slackware.hr>
 
-KERNEL=${KERNEL:-3.2.45}
-XEN=${XEN:-4.3.0}
+KERNEL=${KERNEL:-3.10.17}
+XEN=${XEN:-4.3.1}
 BOOTLOADER=${BOOTLOADER:-lilo}
 
 ROOTMOD=${ROOTMOD:-ext4}

system/xen/domU/domU.sh

@@ -3,11 +3,11 @@
 # Although it might work correctly, this script is intended as a template, so
 # simplicity is the priority here.
 # Written by Chris Abela <chris.abela@maltats.com>, 20100308
-# Updated by mario <mario@slackverse.org>, 2010-2012
+# Modified by Mario Preksavec <mario@slackware.hr>
 
 set -e
 
-KERNEL=${KERNEL:-3.2.29}
+KERNEL=${KERNEL:-3.10.17}
 
 # Build an image for the root file system and another for the swap
 # Default values : 8GB and 500MB resepectively.

system/xen/xen.SlackBuild

@@ -71,11 +71,11 @@ rm -rf $PRGNAM-$VERSION
 tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
 cd $PRGNAM-$VERSION
 chown -R root:root .
-find . \
+find -L . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
- \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
- -exec chmod 644 {} \;
+ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
+ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
 # Fix some stupid things
 patch -p1 <$CWD/patches/configuration_goes_to_system_etc.diff