[Xen-devel] [PATCH 1/1] Fix the README to match Xen 3.1

["Ryan Riley" <rileyrd@xxxxxxxxx>]

So, while installing the new Xen 3.1 I noticed that the included README is still setup for Xen 3.0.  Here's a short patch to fix it.  I realize that even more of this file is going out of date with the removal of the sparse tree, but since that feature hasn't migrated out of the staging tree yet I figured that update can probably wait.

Thanks
Ryan

# HG changeset patch
# User Ryan Riley <rileyrd@xxxxxxxxxxxxx>
# Date 1181222817 14400
# Node ID 375da7236d2af331487c6c15fcac1383b7e4227e
# Parent  c0b0974fb055fa226544079847b94493270fd72e
Update README for Xen 3.1

diff -r c0b0974fb055 -r 375da7236d2a README
--- a/README    Fri May 18 16:59:32 2007 +0100
+++ b/README    Thu Jun 07 09:26:57 2007 -0400
@@ -1,9 +1,9 @@
 ################################
- __  __            _____  ___
- \ \/ /___ _ __   |___ / / _ \
-  \  // _ \ '_ \    |_ \| | | |
-  /  \  __/ | | |  ___) | |_| |
- /_/\_\___|_| |_| |____(_)___/
+__  __            _____  _ 
+\ \/ /___ _ __   |___ / / |
+ \  // _ \ '_ \    |_ \ | |
+ /  \  __/ | | |  ___) || |
+/_/\_\___|_| |_| |____(_)_|
 
 ################################
 
@@ -21,7 +21,7 @@ by the original Xen development team to 
 by the original Xen development team to build enterprise products
 around Xen.
 
-The 3.0 release offers excellent performance, hardware support and
+The 3.1 release offers excellent performance, hardware support and
 enterprise-grade features such as x86_32-PAE, x86_64, SMP guests and
 live relocation of VMs. This install tree contains source for a Linux
 2.6 guest; ports to Linux 2.4, NetBSD, FreeBSD and Solaris are
@@ -55,8 +55,8 @@ 2. Configure your bootloader to boot Xen
    /boot/grub/menu.lst: edit this file to include an entry like the
    following:
 
-    title Xen 3.0 / XenLinux 2.6
-       kernel /boot/xen-3.0.gz console=vga
+    title Xen 3.1 / XenLinux 2.6
+       kernel /boot/xen-
3.1.gz console=vga
        module /boot/vmlinuz-2.6-xen root=<root-dev> ro console=tty0
        module /boot/initrd-2.6-xen.img
 
@@ -75,7 +75,7 @@ 2. Configure your bootloader to boot Xen
    32MB memory for internal use, which is not available for allocation
    to virtual machines.
 
-3. Reboot your system and select the "Xen 3.0 / XenLinux 2.6" menu
+3. Reboot your system and select the "Xen 3.1 / XenLinux 2.6" menu
    option. After booting Xen, Linux will start and your initialisation
    scripts should execute in the usual way.
 
@@ -103,8 +103,8 @@ performed with root privileges.]
 
 1. Download and untar the source tarball file. This will be a
    file named xen-unstable-src.tgz, or xen-$version-
src.tgz.
-   You can also pull the current version from the SCMS
-   that is being used (Bitkeeper, scheduled to change shortly).
+   You can also pull the current version from the mercurial
+   repository at 
http://xenbits.xensource.com/
 
     # tar xzf xen-unstable-src.tgz
 
@@ -175,8 +175,13 @@ 5. To rebuild a kernel with a modified c
 
    Depending on your config, you may need to use 'mkinitrd' to create
    an initial ram disk, just like a native system e.g.
-    # depmod 2.6.16-xen
-    # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen
+    # depmod 2.6.18-xen
+    # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.18-xen.img 2.6.18-xen
+
+   Other systems may requires the use of 'mkinitramfs' to create the
+   ram disk.
+    # depmod 2.6.18-xen
+    # mkinitramfs -o initrd-2.6.18-xen.img 2.6.18-xen
 
 
 Python Runtime Libraries

xen31_readme.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel