|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-changelog] vnet-xend.txt, user.tex, README:
ChangeSet 1.1159.258.159, 2005/05/31 14:14:42+01:00, cl349@xxxxxxxxxxxxxxxxxxxx
vnet-xend.txt, user.tex, README:
Update the Linux kernel version number from 2.6.9 to 2.6 or 2.6.11
in several places in documentation.
Original patch provided by Andrew Thompson <andrewkt@xxxxxxxxxxx>
Signed-off-by: Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
README | 8 ++++----
docs/src/user.tex | 30 +++++++++++++++---------------
tools/vnet/doc/vnet-xend.txt | 4 ++--
3 files changed, 21 insertions(+), 21 deletions(-)
diff -Nru a/README b/README
--- a/README 2005-05-31 12:03:02 -04:00
+++ b/README 2005-05-31 12:03:02 -04:00
@@ -50,16 +50,16 @@
alternatives such as LILO are *not* supported. You can most likely
find your GRUB menu file at /boot/grub/menu.lst: edit this file to
include an entry like the following:
- # title Xen 2.0 / XenLinux 2.6.9
- # kernel /boot/xen.gz dom0_mem=<mem-kb> console=vga
- # module /boot/vmlinuz-2.6.9-xen0 root=<root-dev> ro console=tty0
+ # title Xen 2.0 / XenLinux 2.6
+ # kernel /boot/xen-2.0.gz dom0_mem=<mem-kb> console=vga
+ # module /boot/vmlinuz-2.6-xen0 root=<root-dev> ro console=tty0
For <mem-kb> you should specify the amount of memory, in kilobytes,
to allocate for use by your initial XenLinux virtual machine. Note
that Xen itself reserves about 32MB memory for internal use, which
is not available for allocation to virtual machines.
For <root-dev>, specify your usual root partition (e.g., /dev/hda1).
-3. Reboot your system and select the "Xen 2.0 / XenLinux 2.6.9" menu
+3. Reboot your system and select the "Xen 2.0 / XenLinux 2.6" menu
option. After booting Xen, XenLinux will start and your
initialisation scripts should execute in the usual way.
diff -Nru a/docs/src/user.tex b/docs/src/user.tex
--- a/docs/src/user.tex 2005-05-31 12:03:02 -04:00
+++ b/docs/src/user.tex 2005-05-31 12:03:02 -04:00
@@ -376,7 +376,7 @@
%% it will then add the Xen architecture files. You can tell the
%% makefile the location of the appropriate Linux compressed tar file by
%% setting the LINUX\_SRC environment variable, e.g. \\
-%% \verb!# LINUX_SRC=/tmp/linux-2.6.9.tar.bz2 make world! \\ or by
+%% \verb!# LINUX_SRC=/tmp/linux-2.6.11.tar.bz2 make world! \\ or by
%% placing the tar file somewhere in the search path of {\tt
%% LINUX\_SRC\_PATH} which defaults to `{\tt .:..}'. If the makefile
%% can't find a suitable kernel tar file it attempts to download it from
@@ -407,7 +407,7 @@
architecture being built for is \path{xen}, e.g:
\begin{quote}
\begin{verbatim}
-# cd linux-2.6.9-xen0
+# cd linux-2.6.11-xen0
# make ARCH=xen xconfig
# cd ..
# make
@@ -415,7 +415,7 @@
\end{quote}
You can also copy an existing Linux configuration (\path{.config})
-into \path{linux-2.6.9-xen0} and execute:
+into \path{linux-2.6.11-xen0} and execute:
\begin{quote}
\begin{verbatim}
# make ARCH=xen oldconfig
@@ -453,15 +453,15 @@
%% Files in \path{install/boot/} include:
%% \begin{itemize}
-%% \item \path{install/boot/xen.gz} The Xen 'kernel'
-%% \item \path{install/boot/vmlinuz-2.6.9-xen0} Domain 0 XenLinux kernel
-%% \item \path{install/boot/vmlinuz-2.6.9-xenU} Unprivileged XenLinux kernel
+%% \item \path{install/boot/xen-2.0.gz} Link to the Xen 'kernel'
+%% \item \path{install/boot/vmlinuz-2.6-xen0} Link to domain 0 XenLinux kernel
+%% \item \path{install/boot/vmlinuz-2.6-xenU} Link to unprivileged XenLinux
kernel
%% \end{itemize}
The \path{dist/install/boot} directory will also contain the config files
used for building the XenLinux kernels, and also versions of Xen and
-XenLinux kernels that contain debug symbols (\path{xen-syms} and
-\path{vmlinux-syms-2.6.9-xen0}) which are essential for interpreting crash
+XenLinux kernels that contain debug symbols (\path{xen-syms-2.0.6} and
+\path{vmlinux-syms-2.6.11.11-xen0}) which are essential for interpreting crash
dumps. Retain these files as the developers may wish to see them if
you post on the mailing list.
@@ -483,9 +483,9 @@
{\small
\begin{verbatim}
-title Xen 2.0 / XenLinux 2.6.9
- kernel /boot/xen.gz dom0_mem=131072
- module /boot/vmlinuz-2.6.9-xen0 root=/dev/sda4 ro console=tty0
+title Xen 2.0 / XenLinux 2.6
+ kernel /boot/xen-2.0.gz dom0_mem=131072
+ module /boot/vmlinuz-2.6-xen0 root=/dev/sda4 ro console=tty0
\end{verbatim}
}
@@ -524,8 +524,8 @@
\subsection{Serial Console (optional)}
-%% kernel /boot/xen.gz dom0_mem=131072 com1=115200,8n1
-%% module /boot/vmlinuz-2.6.9-xen0 root=/dev/sda4 ro
+%% kernel /boot/xen-2.0.gz dom0_mem=131072 com1=115200,8n1
+%% module /boot/vmlinuz-2.6-xen0 root=/dev/sda4 ro
In order to configure Xen serial console output, it is necessary to add
@@ -654,7 +654,7 @@
\begin{quote}
\begin{description}
\item[kernel] Set this to the path of the kernel you compiled for use
- with Xen (e.g.\ \path{kernel = '/boot/vmlinuz-2.6.9-xenU'})
+ with Xen (e.g.\ \path{kernel = '/boot/vmlinuz-2.6-xenU'})
\item[memory] Set this to the size of the domain's memory in
megabytes (e.g.\ \path{memory = 64})
\item[disk] Set the first entry in this list to calculate the offset
@@ -717,7 +717,7 @@
\path{http://sf.net/projects/xen/}).
\item Create a configuration file like the following:
\begin{verbatim}
-kernel = "/boot/vmlinuz-2.6.9-xenU"
+kernel = "/boot/vmlinuz-2.6-xenU"
memory = 64
name = "ttylinux"
nics = 1
diff -Nru a/tools/vnet/doc/vnet-xend.txt b/tools/vnet/doc/vnet-xend.txt
--- a/tools/vnet/doc/vnet-xend.txt 2005-05-31 12:03:02 -04:00
+++ b/tools/vnet/doc/vnet-xend.txt 2005-05-31 12:03:02 -04:00
@@ -102,7 +102,7 @@
(console '8502')
(image
(linux
- (kernel /boot/vmlinuz-2.6.9-xenU)
+ (kernel /boot/vmlinuz-2.6-xenU)
(ip 10.0.0.12:1.2.3.4::::eth0:off)
(root /dev/hda1)
(args 'rw fastboot 4')
@@ -121,7 +121,7 @@
(console '8501')
(image
(linux
- (kernel /boot/vmlinuz-2.6.9-xenU)
+ (kernel /boot/vmlinuz-2.6-xenU)
(ip 10.0.0.11:1.2.3.4::::eth0:off)
(root /dev/hda1)
(args 'rw fastboot 4')
_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |