public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/en: xen-guide.xml
Date: Wed,  2 Mar 2011 09:22:44 +0000 (UTC)	[thread overview]
Message-ID: <20110302092244.7732F20057@flycatcher.gentoo.org> (raw)

nightmorph    11/03/02 09:22:44

  Modified:             xen-guide.xml
  Log:
  remove outdated keywording instructions now that there are stable xen packages

Revision  Changes    Path
1.8                  xml/htdocs/doc/en/xen-guide.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/xen-guide.xml?r1=1.7&r2=1.8

Index: xen-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- xen-guide.xml	14 Nov 2010 15:27:04 -0000	1.7
+++ xen-guide.xml	2 Mar 2011 09:22:44 -0000	1.8
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.7 2010/11/14 15:27:04 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.8 2011/03/02 09:22:44 nightmorph Exp $ -->
 
 <guide>
 <title>Configuring Gentoo with Xen</title>
@@ -20,8 +20,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>3</version>
-<date>2010-11-14</date>
+<version>4</version>
+<date>2011-03-02</date>
 
 <chapter>
 <title>Introduction</title>
@@ -110,19 +110,11 @@
 <body>
 
 <p>
-Xen actually contains many components, so you'll need to install a couple of
-packages. Because it is still <uri
-link="/doc/en/handbook/handbook-x86.xml?part=3&amp;chap=3#doc_chap2">~arch
-masked</uri> you first need to unmask it by adding the necessary lines to
-<path>/etc/portage/package.keywords</path> and then install them.
+Xen actually contains many components, so you'll need to install a few
+packages.
 </p>
 
-<pre caption="Unmasking and Installing Xen">
-~# <i>nano -w /etc/portage/package.keywords</i>
-app-emulation/xen
-app-emulation/xen-tools
-sys-kernel/xen-sources
-
+<pre caption="Installing Xen">
 ~# <i>emerge xen xen-tools xen-sources</i>
 </pre>
 






             reply	other threads:[~2011-03-02  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02  9:22 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-24 18:36 [gentoo-commits] gentoo commit in xml/htdocs/doc/en: xen-guide.xml Sven Vermeulen (swift)
2012-10-07 13:32 Sven Vermeulen (swift)
2011-08-29 10:09 Joshua Saddler (nightmorph)
2011-06-07  9:27 Joshua Saddler (nightmorph)
2010-11-14 15:27 Joshua Saddler (nightmorph)
2010-05-14 21:55 Joshua Saddler (nightmorph)
2008-08-11 16:25 Sven Vermeulen (swift)
2008-04-10 15:01 Camille Huot (cam)
2007-12-10 15:37 Sven Vermeulen (swift)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110302092244.7732F20057@flycatcher.gentoo.org \
    --to=nightmorph@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox