Skip to contentSkip to conversation

Please pull xen-unstable-docs

PATCH In review Robb Romans 5 participants 8 messages Nov 10, 2005

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Please pull xen-unstable-docs

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori. This is also for testing that I have done things correctly in using the separate doc tree.

Please pull from http://xenbits.xensource.com/ext/xen-unstable-docs.hg

diffstat

b/docs/src/user/securing_xen.tex |   85 ++++++++++++++++++++
docs/src/user.tex                |  114 ++++++++++++++-------------
docs/src/user/installation.tex   |  164 ++++++++++++++++-----------------------
docs/src/user/introduction.tex   |   79 +++++++++---------
docs/src/user/start_addl_dom.tex |   21 ++--
5 files changed, 264 insertions(+), 199 deletions(-)

Regards,
Robb

- --
Robb Romans (512) 838-0419
Linux Commando T/L 678-0419
ARS NA5TT
.-- - ..-. ..--..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDc3wldoW/RCLrCx0RAqEgAJ9ekuPE5/QN+dbPz/C7EGTUYwPGWwCeOB4y LAFEg+knMFHOs+7tQb0NnPU=
=zAV8
-----END PGP SIGNATURE-----

#1 lore raw

+1 from me.

Cheers,
Mark

Quoted 20 lines · Robb Romans

Hi,

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori. This is also for testing that I have done things correctly in using the separate doc tree.

Please pull from http://xenbits.xensource.com/ext/xen-unstable-docs.hg

diffstat

b/docs/src/user/securing_xen.tex |   85 ++++++++++++++++++++
docs/src/user.tex                |  114 ++++++++++++++-------------
docs/src/user/installation.tex   |  164
++++++++++++++++----------------------- docs/src/user/introduction.tex   | 
 79 +++++++++---------
docs/src/user/start_addl_dom.tex |   21 ++--
5 files changed, 264 insertions(+), 199 deletions(-)

Regards,
Robb

#2 lore raw
In reply to Robb Romans
Quoted 2 lines · Robb Romans

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori.

Who is this guy Anthony Liguori and why is he so dangerous? :-)

Signature · 4 lines
Tired of having to defend against Malware?
You know: trojans, viruses, SPYWARE, ADWARE, 
KEYLOGGERS, rootkits, worms and popups.
Then Switch to OpenBSD with a KDE desktop!!!
#3 lore raw
Quoted 7 lines · Dave Feustel
Quoted 2 lines · Robb Romans

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori.

Who is this guy Anthony Liguori and why is he so dangerous? :-)

how much time do you have??

:) :)

thanks,
Nivedita

#4 lore raw
In reply to Robb Romans
Quoted 5 lines · Robb Romans

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori. This is also for testing that I have done things correctly in using the separate doc tree.

Please pull from http://xenbits.xensource.com/ext/xen-unstable-docs.hg

Thanks! It would be more convenient to send small numbers of patches to the list, rather than pulling them from an external tree. I end up having to clone the tree, re-merge and do a diff to check what has actually been changed (since hg doesn't have good visualisation tools). It's worth it for trees that see plenty of activity like xen-unstable-ia64 -- it doesn't currently seem worthwhile for docuementation unless activity is going to ramp up significantly.

-- Keir

#5 lore raw
Quoted 11 lines · Keir Fraser
Quoted 5 lines · Robb Romans

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori. This is also for testing that I have done things correctly in using the separate doc tree.

Please pull from http://xenbits.xensource.com/ext/xen-unstable-docs.hg

Thanks! It would be more convenient to send small numbers of patches to the list, rather than pulling them from an external tree. I end up having to clone the tree, re-merge and do a diff to check what has actually been changed (since hg doesn't have good visualisation tools). It's worth it for trees that see plenty of activity like xen-unstable-ia64 -- it doesn't currently seem worthwhile for docuementation unless activity is going to ramp up significantly.

Hi Keir,

We had talked a bit with Ian about this much earlier, and he had preferred a hg tree. We can always just push patches out, too..We're going to start ramping up, and hope to put out a steady stream of stuff over the next week, but it won't be that kind of volume.

Let us know if you'd prefer the patches, instead.

thanks,
Nivedita

#6 lore raw
Quoted 7 lines · Nivedita Singhvi

We had talked a bit with Ian about this much earlier, and he had preferred a hg tree. We can always just push patches out, too..We're going to start ramping up, and hope to put out a steady stream of stuff over the next week, but it won't be that kind of volume.

Let us know if you'd prefer the patches, instead.

I would say it is worth using the separate tree if you are producing more than about twenty patches a week. In that case I'm happy to sync an external tree about once a week. Otherwise it is quicker for me to apply emailed patches.

-- Keir

#7 lore raw
In reply to Keir Fraser

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"KF" == Keir Fraser <[email protected]> writes:

Quoted 7 lines · Robb Romans

Here are a few cleanups for the Users' Manual, including adding a chapter on securing Xen from Anthony Liguori. This is also for testing that I have done things correctly in using the separate doc tree.

Please pull from
http://xenbits.xensource.com/ext/xen-unstable-docs.hg

KF> Thanks! It would be more convenient to send small numbers of KF> patches to the list, rather than pulling them from an external KF> tree. I end up having to clone the tree, re-merge and do a diff KF> to check what has actually been changed (since hg doesn't have KF> good visualisation tools). It's worth it for trees that see KF> plenty of activity like xen-unstable-ia64 -- it doesn't KF> currently seem worthwhile for docuementation unless activity is KF> going to ramp up significantly.

OK.

changeset:   7714:79e8991af6b4
user:        Robb Romans <[email protected]>
date:        Thu Nov 10 10:42:58 2005 -0500
summary:     A few doc cleanups. Replace bitkeeper with mercurial.

# HG changeset patch
# User Robb Romans <[email protected]>
# Node ID 79e8991af6b43a85547dccf976cdb5bb161fe005 # Parent 136b2d20dc81db51924aee54c8ec4ce6232defa2 A few doc cleanups. Replace bitkeeper with mercurial.

docs/src/user.tex +56 -55
diff -r 136b2d20dc81 -r 79e8991af6b4 docs/src/user.tex
@@ -7,7 +7,6 @@
 \def\xend{{xend}\xspace}
 
 \latexhtml{\newcommand{\path}[1]{{\small {\tt #1}}}}{\newcommand{\path}[1]{{\tt #1}}}
-
 
 
 \begin{document}
@@ -21,23 +20,23 @@
 \vfill
 \vfill
 \begin{tabular}{l}
-{\Huge \bf Users' manual} \\[4mm]
-{\huge Xen v2.0 for x86} \\[80mm]
-
-{\Large Xen is Copyright (c) 2002-2004, The Xen Team} \\[3mm]
+{\Huge \bf Users' Manual} \\[4mm]
+{\huge Xen v3.0} \\[80mm]
+
+{\Large Xen is Copyright (c) 2002-2005, The Xen Team} \\[3mm]
 {\Large University of Cambridge, UK} \\[20mm]
 \end{tabular}
 \end{center}
 
-{\bf
-DISCLAIMER: This documentation is currently under active development
-and as such there may be mistakes and omissions --- watch out for
-these and please report any you find to the developer's mailing list.
-Contributions of material, suggestions and corrections are welcome.
-}
+{\bf DISCLAIMER: This documentation is currently under active
+  development and as such there may be mistakes and omissions ---
+  watch out for these and please report any you find to the
+  developers' mailing list.  Contributions of material, suggestions
+  and corrections are welcome.}
 
 \vfill
 \cleardoublepage
+
 
 % TABLE OF CONTENTS
 \pagestyle{plain}
@@ -45,6 +44,7 @@
 { \parskip 0pt plus 1pt
   \tableofcontents }
 \cleardoublepage
+
 
 % PREPARE FOR MAIN TEXT
 \pagenumbering{arabic}
@@ -68,7 +68,7 @@
 %% Chapter Installation moved to installation.tex
 \include{src/user/installation}
 
-%% Chapter Starting Additional Domains  moved to start_addl_dom.tex
+%% Chapter Starting Additional Domains moved to start_addl_dom.tex
 \include{src/user/start_addl_dom}
 
 %% Chapter Domain Management Tools moved to domain_mgmt.tex
@@ -99,25 +99,25 @@
 software (or the documentation) should be sent to the Xen developers'
 mailing list (address below).
 
+
 \section{Other Documentation}
 
 For developers interested in porting operating systems to Xen, the
-{\em Xen Interface Manual} is distributed in the \path{docs/}
-directory of the Xen source distribution.  
-
-%Various HOWTOs are available in \path{docs/HOWTOS} but this content is
-%being integrated into this manual.
+\emph{Xen Interface Manual} is distributed in the \path{docs/}
+directory of the Xen source distribution.
+
+% Various HOWTOs are available in \path{docs/HOWTOS} but this content
+% is being integrated into this manual.
 
 
 \section{Online References}
 
 The official Xen web site is found at:
-\begin{quote}
-{\tt http://www.cl.cam.ac.uk/netos/xen/}
+\begin{quote} {\tt http://www.cl.cam.ac.uk/netos/xen/}
 \end{quote}
 
-This contains links to the latest versions of all on-line 
-documentation (including the lateset version of the FAQ). 
+This contains links to the latest versions of all online
+documentation, including the latest version of the FAQ.
 
 
 \section{Mailing Lists}
@@ -126,17 +126,17 @@
 
 \begin{description}
 \item[[email protected]] Used for development
-discussions and bug reports.  Subscribe at: \\
-{\small {\tt http://lists.xensource.com/xen-devel}}
+  discussions and bug reports.  Subscribe at: \\
+  {\small {\tt http://lists.xensource.com/xen-devel}}
 \item[[email protected]] Used for installation and usage
-discussions and requests for help.  Subscribe at: \\
-{\small {\tt http://lists.xensource.com/xen-users}}
+  discussions and requests for help.  Subscribe at: \\
+  {\small {\tt http://lists.xensource.com/xen-users}}
 \item[[email protected]] Used for announcements only.
-Subscribe at: \\
-{\small {\tt http://lists.xensource.com/xen-announce}}
-\item[[email protected]]  Changelog feed
-from the unstable and 2.0 trees - developer oriented.  Subscribe at: \\
-{\small {\tt http://lists.xensource.com/xen-changelog}}
+  Subscribe at: \\
+  {\small {\tt http://lists.xensource.com/xen-announce}}
+\item[[email protected]] Changelog feed
+  from the unstable and 2.0 trees - developer oriented.  Subscribe at: \\
+  {\small {\tt http://lists.xensource.com/xen-changelog}}
 \end{description}
 
 
@@ -149,9 +149,9 @@
 %% Chapter Installing Xen on Red Hat moved to redhat.tex
 \include{src/user/redhat}
 
-
 %% Chapter Glossary of Terms moved to glossary.tex
 \include{src/user/glossary}
+
 
 
 \end{document}
@@ -181,36 +181,35 @@
 %% # import xenctl.utils
 %% # help(xenctl.utils)
 
-%% You can use these modules to write your own custom scripts or you can
-%% customise the scripts supplied in the Xen distribution.
+%% You can use these modules to write your own custom scripts or you
+%% can customise the scripts supplied in the Xen distribution.
 
 
 
 % Explain about AGP GART
 
 
-%% If you're not intending to configure the new domain with an IP address
-%% on your LAN, then you'll probably want to use NAT. The
-%% 'xen_nat_enable' installs a few useful iptables rules into domain0 to
-%% enable NAT. [NB: We plan to support RSIP in future]
-
+%% If you're not intending to configure the new domain with an IP
+%% address on your LAN, then you'll probably want to use NAT. The
+%% 'xen_nat_enable' installs a few useful iptables rules into domain0
+%% to enable NAT. [NB: We plan to support RSIP in future]
 
 
 
 %% Installing the file systems from the CD
 %% =======================================
 
-%% If you haven't got an existing Linux installation onto which you can
-%% just drop down the Xen and Xenlinux images, then the file systems on
-%% the CD provide a quick way of doing an install. However, you would be
-%% better off in the long run doing a proper install of your preferred
-%% distro and installing Xen onto that, rather than just doing the hack
-%% described below:
-
-%% Choose one or two partitions, depending on whether you want a separate
-%% /usr or not. Make file systems on it/them e.g.: 
-%%   mkfs -t ext3 /dev/hda3
-%%   [or mkfs -t ext2 /dev/hda3 && tune2fs -j /dev/hda3 if using an old
+%% If you haven't got an existing Linux installation onto which you
+%% can just drop down the Xen and Xenlinux images, then the file
+%% systems on the CD provide a quick way of doing an install. However,
+%% you would be better off in the long run doing a proper install of
+%% your preferred distro and installing Xen onto that, rather than
+%% just doing the hack described below:
+
+%% Choose one or two partitions, depending on whether you want a
+%% separate /usr or not. Make file systems on it/them e.g.:
+%% mkfs -t ext3 /dev/hda3
+%% [or mkfs -t ext2 /dev/hda3 && tune2fs -j /dev/hda3 if using an old
 %% version of mkfs]
 
 %% Next, mount the file system(s) e.g.:
@@ -224,12 +223,14 @@
 %% configuration. Changing the password file (etc/shadow) is probably a
 %% good idea too.
 
-%% To install the usr file system, copy the file system from CD on /usr,
-%% though leaving out the "XenDemoCD" and "boot" directories:
-%%   cd /usr && cp -a X11R6 etc java libexec root src bin dict kerberos local sbin tmp doc include lib man share /mnt/usr
+%% To install the usr file system, copy the file system from CD on
+%% /usr, though leaving out the "XenDemoCD" and "boot" directories:
+%%   cd /usr && cp -a X11R6 etc java libexec root src bin dict kerberos
+%%    local sbin tmp doc include lib man share /mnt/usr
 
 %% If you intend to boot off these file systems (i.e. use them for
-%% domain 0), then you probably want to copy the /usr/boot directory on
-%% the cd over the top of the current symlink to /boot on your root
-%% filesystem (after deleting the current symlink) i.e.:
+%% domain 0), then you probably want to copy the /usr/boot
+%% directory on the cd over the top of the current symlink to /boot
+%% on your root filesystem (after deleting the current symlink)
+%% i.e.:
 %%   cd /mnt/root ; rm boot ; cp -a /usr/boot .
docs/src/user/installation.tex +69 -95

334 lines not on this page · raw message

docs/src/user/introduction.tex +39 -40

148 lines not on this page · raw message

docs/src/user/start_addl_dom.tex +12 -9
diff -r 136b2d20dc81 -r 79e8991af6b4 docs/src/user/start_addl_dom.tex
@@ -40,8 +40,7 @@
 a starting point:
 \begin{itemize}
 \item \path{/etc/xen/xmexample1} is a simple template configuration
-  file for describing a single VM.
-
+  file for describing a single VM\@.
 \item \path{/etc/xen/xmexample2} file is a template description that
   is intended to be reused for multiple virtual machines.  Setting the
   value of the \path{vmid} variable on the \path{xm} command line
@@ -54,17 +53,17 @@
 \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-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
-  of the domain's root partition, based on the domain ID.  Set the
+  of the domain's root partition, based on the domain ID\@.  Set the
   second to the location of \path{/usr} if you are sharing it between
-  domains (e.g.\ \path{disk = [`phy:your\_hard\_drive\%d,sda1,w' \%
+  domains (e.g.\ \path{disk = ['phy:your\_hard\_drive\%d,sda1,w' \%
     (base\_partition\_number + vmid),
-    `phy:your\_usr\_partition,sda6,r' ]}
+    'phy:your\_usr\_partition,sda6,r' ]}
 \item[dhcp] Uncomment the dhcp variable, so that the domain will
-  receive its IP address from a DHCP server (e.g.\ \path{dhcp=`dhcp'})
+  receive its IP address from a DHCP server (e.g.\ \path{dhcp=``dhcp''})
 \end{description}
 \end{quote}
 
@@ -72,7 +71,7 @@
 the MAC address of the virtual ethernet interface yourself.  For
 example:
 \begin{quote}
-\verb_vif = [`mac=00:06:AA:F6:BB:B3']_
+\verb_vif = ['mac=00:06:AA:F6:BB:B3']_
 \end{quote}
 If you do not set this variable, \xend\ will automatically generate a
 random MAC address from an unused range.
@@ -116,6 +115,7 @@
   section of the project's SourceForge site (see
   \path{http://sf.net/projects/xen/}).
 \item Create a configuration file like the following:
+  \begin{quote}
 \begin{verbatim}
 kernel = "/boot/vmlinuz-2.6-xenU"
 memory = 64
@@ -124,11 +124,14 @@
 ip = "1.2.3.4"
 disk = ['file:/path/to/ttylinux/rootfs,sda1,w']
 root = "/dev/sda1 ro"
-\end{verbatim}
+\end{verbatim}    
+  \end{quote}
 \item Now start the domain and connect to its console:
+  \begin{quote}
 \begin{verbatim}
 xm create configfile -c
 \end{verbatim}
+  \end{quote}
 \item Login as root, password root.
 \end{enumerate}
 
changeset:   7715:f1c07363956b
tag:         tip
user:        Robb Romans <[email protected]>
date:        Thu Nov 10 10:43:24 2005 -0500
summary:     Add "Securing Xen" adapted from Anthony Liguori's Wiki entry.

# HG changeset patch
# User Robb Romans <[email protected]>
# Node ID f1c07363956b06078b33b245dc51811c9a8c5b05 # Parent 79e8991af6b43a85547dccf976cdb5bb161fe005 Add "Securing Xen" adapted from Anthony Liguori's Wiki entry.

docs/src/user.tex +3 -0
diff -r 79e8991af6b4 -r f1c07363956b docs/src/user.tex
@@ -86,6 +86,9 @@
 
 %% Chapter Domain Configuration moved to domain_configuration.tex
 \include{src/user/domain_configuration}
+
+%% Chapter Securing Xen
+\include{src/user/securing_xen}
 
 %% Chapter Build, Boot and Debug Options moved to build.tex
 \include{src/user/build}
docs/src/user/securing_xen.tex new file +85 -0

85 lines not on this page · raw message

Regards,
Robb

- --
Robb Romans (512) 838-0419
Linux Commando T/L 678-0419
ARS NA5TT
.-- - ..-. ..--..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDc4ssdoW/RCLrCx0RAvo2AJ9TlcmLNSRFTiy0xxiChmqLCmpxLwCfUhYg lDwQBOLkmmsi7Y6CuC5+7Gg=
=vwxZ
-----END PGP SIGNATURE-----

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel