* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2005-08-08 11:08 Xavier Neys
0 siblings, 0 replies; 7+ messages in thread
From: Xavier Neys @ 2005-08-08 11:08 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 05/08/08 11:08:24
Modified: xml/htdocs/doc/en vserver-howto.xml
Log:
Removed tabs, shortened links, applied coding style, **No Content Change**
Revision Changes Path
1.2 +72 -61 xml/htdocs/doc/en/vserver-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- vserver-howto.xml 17 Jun 2005 10:06:56 -0000 1.1
+++ vserver-howto.xml 8 Aug 2005 11:08:24 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.1 2005/06/17 10:06:56 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.2 2005/08/08 11:08:24 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -31,7 +31,7 @@
<body>
<p>
-The basic concept of the Linux-VServer solution is to separate the user-space
+The basic concept of the Linux-VServer solution is to separate the user-space
environment into distinct units (sometimes called Virtual Private Servers) in
such a way that each VPS looks and feels like a real server to the processes
contained within.
@@ -50,23 +50,31 @@
</tr>
<tr>
<th>Linux-VServer, VServer</th>
- <ti>Linux-VServer is the official name of the project and used in this Howto
- the same way</ti>
+ <ti>
+ Linux-VServer is the official name of the project and used in this Howto
+ the same way
+ </ti>
</tr>
<tr>
<th>virtual server, vserver, guest system</th>
- <ti>All these are interchangable and refer to one instance of a server (i.e.
- one virtual server)</ti>
+ <ti>
+ All these are interchangable and refer to one instance of a server (i.e.
+ one virtual server)
+ </ti>
</tr>
<tr>
<th>host system, host</th>
- <ti>The physical machine running your Gentoo Linux will host all virtual
- servers</ti>
+ <ti>
+ The physical machine running your Gentoo Linux will host all virtual
+ servers
+ </ti>
</tr>
<tr>
<th>util-vserver, vserver utils</th>
- <ti>The <c>util-vserver</c> package contains all programs necessary for
- maintaining your virtual servers</ti>
+ <ti>
+ The <c>util-vserver</c> package contains all programs necessary for
+ maintaining your virtual servers
+ </ti>
</tr>
</table>
@@ -85,7 +93,7 @@
</pre>
<p>
-After the vserver-sources are installed it's time to configure them using
+After the vserver-sources are installed it's time to configure them using
<c>make menuconfig</c>.
</p>
@@ -97,18 +105,18 @@
<comment>(Required by current utils)</comment>
[*] Enable Legacy Kernel API
<comment>(Do not set!)</comment>
- [ ] Disable Legacy Networking Kernel API
+ [ ] Disable Legacy Networking Kernel API
<comment>(Highly recommended)</comment>
- [*] Enable Proc Security
+ [*] Enable Proc Security
[ ] Enable Hard CPU Limits
- Persistent Inode Context Tagging (UID24/GID24) --->
+ Persistent Inode Context Tagging (UID24/GID24) --->
[ ] Tag NFSD User Auth and Files
[ ] Compile Debugging Code
</pre>
<p>
-After you've built and installed the kernel, update your boot loader and finally
-reboot to see if the kernel boots correctly.
+After you've built and installed the kernel, update your boot loader and
+finally reboot to see if the kernel boots correctly.
</p>
<pre caption="Install the kernel">
@@ -137,12 +145,12 @@
</pre>
<p>
-If you use Proc Security you have to "unhide" certain files in your
-<path>/proc</path> directory in order to make them available in virtual servers.
-There is a script called <c>vprocunhide</c> in
-<path>/usr/lib/util-vserver</path> which unhides files specified in
+If you use Proc Security you have to "unhide" certain files in your
+<path>/proc</path> directory in order to make them available in virtual
+servers. There is a script called <c>vprocunhide</c> in
+<path>/usr/lib/util-vserver</path> which unhides files specified in
<path>/usr/lib/util-vserver/defaults/vprocunhide-files</path>. The util-vserver
-ebuild installed a init-script which uses the <c>vprocunhide</c> command. Add
+ebuild installed a init-script which uses the <c>vprocunhide</c> command. Add
it to your runlevel:
</p>
@@ -152,8 +160,8 @@
</pre>
<p>
-The vshelper script is used to correctly stop and restart virtual servers.
-You have to tell the kernel where the vshelper script is located:
+The vshelper script is used to correctly stop and restart virtual servers. You
+have to tell the kernel where the vshelper script is located:
</p>
<pre caption="vshelper setup">
@@ -168,9 +176,9 @@
<body>
<p>
-You have to create some configuration files and directories to get your
-virtual server up and running. We use the skeleton build mode from the
-util-vserver package to setup our basic configuration.
+You have to create some configuration files and directories to get your virtual
+server up and running. We use the skeleton build mode from the util-vserver
+package to setup our basic configuration.
</p>
<p>
@@ -181,8 +189,8 @@
<p>
There is a new baselayout-vserver ebuild in portage which supports the plain
-init-style, i.e.; you don't have to use the gentoo init style anymore. The
-plain init-style uses <c>init</c> and <path>/etc/inittab</path> to manage
+init-style, i.e.; you don't have to use the gentoo init style anymore. The
+plain init-style uses <c>init</c> and <path>/etc/inittab</path> to manage
runlevels and init scripts (considered more stable and is the default now).
</p>
@@ -202,9 +210,9 @@
</pre>
<impo>
-Per default the virtual server is allowed to set the hostname itself. Be
-sure to change <path>/etc/conf.d/hostname</path> in your virtual server later
-to match the hostname above.
+Per default the virtual server is allowed to set the hostname itself. Be sure
+to change <path>/etc/conf.d/hostname</path> in your virtual server later to
+match the hostname above.
</impo>
</body>
@@ -214,10 +222,10 @@
<body>
<p>
-We are creating a Gentoo template which we can copy later to get
-multiple virtual servers easily. The vserver build-script created
-some basic directories in <path>/vservers/gentoo</path> which
-are installed by a stage anyway, so we remove them first.
+We are creating a Gentoo template which we can copy later to get multiple
+virtual servers easily. The vserver build-script created some basic directories
+in <path>/vservers/gentoo</path> which are installed by a stage anyway, so we
+remove them first.
</p>
<pre caption="Remove skeleton files">
@@ -225,48 +233,51 @@
</pre>
<p>
-You have to install a regular Gentoo system now. You can follow most
-of the Gentoo Handbook with some limitations and additions:
+You have to install a regular Gentoo system now. You can follow most of the
+Gentoo Handbook with some limitations and additions:
</p>
<ul>
- <li>Replace <path>/mnt/gentoo</path> with
- <path>/vservers/gentoo</path>
- </li>
- <li>Choose the <path>vserver/x86</path> profile in
- <uri link="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6#doc_chap1_sect6">chapter 6.a</uri>
- </li>
- <li>Use the vserver stages available
- <uri link="http://dev.gentoo.org/~hollow/vserver/stages/">here</uri>.
- </li>
+ <li>Replace <path>/mnt/gentoo</path> with <path>/vservers/gentoo</path></li>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2005-10-06 16:42 Jan Kundrat
0 siblings, 0 replies; 7+ messages in thread
From: Jan Kundrat @ 2005-10-06 16:42 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/10/06 16:42:48
Modified: xml/htdocs/doc/en vserver-howto.xml
Log:
#108259, "Update vserver howto to reflect latest changes" by hollow
Revision Changes Path
1.3 +66 -129 xml/htdocs/doc/en/vserver-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- vserver-howto.xml 8 Aug 2005 11:08:24 -0000 1.2
+++ vserver-howto.xml 6 Oct 2005 16:42:48 -0000 1.3
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.2 2005/08/08 11:08:24 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.3 2005/10/06 16:42:48 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -21,8 +21,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.0</version>
-<date>2005-06-17</date>
+<version>1.1</version>
+<date>2005-10-06</date>
<chapter>
<title>Introduction</title>
@@ -83,7 +83,7 @@
</chapter>
<chapter>
-<title>Creating a VServer template</title>
+<title>Host configuration</title>
<section>
<title>Install a VServer kernel</title>
<body>
@@ -102,13 +102,12 @@
# <i>make menuconfig</i>
Linux VServer --->
-<comment>(Required by current utils)</comment>
- [*] Enable Legacy Kernel API
+ [ ] Enable Legacy Kernel API
<comment>(Do not set!)</comment>
[ ] Disable Legacy Networking Kernel API
<comment>(Highly recommended)</comment>
[*] Enable Proc Security
- [ ] Enable Hard CPU Limits
+ [*] Enable Hard CPU Limits
Persistent Inode Context Tagging (UID24/GID24) --->
[ ] Tag NFSD User Auth and Files
[ ] Compile Debugging Code
@@ -124,7 +123,7 @@
# <i>make</i>
<comment>(Installing)</comment>
# <i>make modules_install</i>
-# <i>cp arch/i386/boot/bzImage /boot/kernel-<KERNELVERSION>-vs<VSERVERVERSION></i>
+# <i>cp arch/i386/boot/bzImage /boot/kernel-<KERNELVERSION>-vserver-<VSERVERVERSION></i>
<comment>(Edit bootloader config file as required and)</comment>
# <i>reboot</i>
</pre>
@@ -140,23 +139,25 @@
contains all necessary programs and many usefull features.
</p>
+<note>
+The tools and features used in this HowTo require
+<c>>=sys-apps/util-vserver-0.30.208-r3</c>. You may have to keyword it first.
+</note>
+
<pre caption="Install vserver utils">
# <i>emerge util-vserver</i>
</pre>
<p>
-If you use Proc Security you have to "unhide" certain files in your
-<path>/proc</path> directory in order to make them available in virtual
-servers. There is a script called <c>vprocunhide</c> in
-<path>/usr/lib/util-vserver</path> which unhides files specified in
-<path>/usr/lib/util-vserver/defaults/vprocunhide-files</path>. The util-vserver
-ebuild installed a init-script which uses the <c>vprocunhide</c> command. Add
-it to your runlevel:
+You have to run the <c>vprocunhide</c> command after every reboot in order to
+setup <path>/proc</path> permissions correctly for vserver use. An init script has
+been installed by util-vserver. To use it you should add it to a
+runlevel:
</p>
-<pre caption="vprocunhide init script">
-# <i>rc-update add vprocunhide default</i>
-# <i>/etc/init.d/vprocunhide start</i>
+<pre caption="vserver init script">
+# <i>rc-update add vservers default</i>
+# <i>/etc/init.d/vservers start</i>
</pre>
<p>
@@ -171,27 +172,19 @@
</body>
</section>
+</chapter>
+
+<chapter>
+<title>Creating a guest template</title>
<section>
-<title>Basic Skeleton configuration</title>
+<title>Install a vserver stage3</title>
<body>
<p>
-You have to create some configuration files and directories to get your virtual
-server up and running. We use the skeleton build mode from the util-vserver
-package to setup our basic configuration.
-</p>
-
-<p>
-The util-vserver package uses <path>/vservers</path> to store all virtual
-servers by default. You can put your servers somewhere else by specifying
-<c>--rootdir=/path/to/vserver/root</c> to the build command below.
-</p>
-
-<p>
-There is a new baselayout-vserver ebuild in portage which supports the plain
-init-style, i.e.; you don't have to use the gentoo init style anymore. The
-plain init-style uses <c>init</c> and <path>/etc/inittab</path> to manage
-runlevels and init scripts (considered more stable and is the default now).
+We will use <c>vserver-new</c> to create the initial guest. You have to download
+a vserver prepared stage3 from
+<uri>http://dev.gentoo.org/~hollow/vserver/stages</uri> and the script will
+guide you through the creation process.
</p>
<p>
@@ -201,118 +194,63 @@
equivalent to the last two parts of the virtual servers IP).
</p>
-<pre caption="Basic configuration">
-# <i>vserver gentoo build -m skeleton \</i>
+<pre caption="Start stage3 installation">
+# <i>vserver-new gentoo-template \</i>
<i>--hostname gentoo \</i>
- <i>--initstyle plain \</i>
- <i>--context 1253</i>
- <i>--interface gentoo=eth0:192.168.1.253/24</i>
+ <i>--context 1253 \</i>
+ <i>--interface eth0:192.168.1.253/24 \</i>
+ <i>stage3 /path/to/stage3-tarball.tar.bz2</i>
</pre>
-<impo>
-Per default the virtual server is allowed to set the hostname itself. Be sure
-to change <path>/etc/conf.d/hostname</path> in your virtual server later to
-match the hostname above.
-</impo>
-
-</body>
-</section>
-<section>
-<title>Installing Gentoo installation files</title>
-<body>
-
-<p>
-We are creating a Gentoo template which we can copy later to get multiple
-virtual servers easily. The vserver build-script created some basic directories
-in <path>/vservers/gentoo</path> which are installed by a stage anyway, so we
-remove them first.
-</p>
-
-<pre caption="Remove skeleton files">
-# <i>rm -rf /vservers/gentoo/*</i>
-</pre>
-
-<p>
-You have to install a regular Gentoo system now. You can follow most of the
-Gentoo Handbook with some limitations and additions:
-</p>
-
-<ul>
- <li>Replace <path>/mnt/gentoo</path> with <path>/vservers/gentoo</path></li>
- <li>
- Choose the <path>vserver/x86</path> profile in <uri
- link="/doc/en/handbook/handbook-x86.xml?part=1&chap=6#doc_chap1_sect6">chapter
- 6.a</uri>
- </li>
- <li>
- Use the vserver stages available <uri
- link="http://dev.gentoo.org/~hollow/vserver/stages/">here</uri>.
- </li>
-</ul>
-
-<p>
-Now, follow the Gentoo Handbook from <uri
-link="/doc/en/handbook/handbook-x86.xml?part=1&chap=5#doc_chap2"> chapter
-5.b</uri> to chapter 7.a and <uri
-link="/doc/en/handbook/handbook-x86.xml?part=1&chap=8#doc_chap3"> chapter
-8.c</uri> to chapter 9.c
-</p>
-
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2005-12-19 12:09 Jan Kundrat
0 siblings, 0 replies; 7+ messages in thread
From: Jan Kundrat @ 2005-12-19 12:09 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/19 12:09:33
Modified: xml/htdocs/doc/en vserver-howto.xml
Log:
#114193, "reiserfs: mention of attrs option for /vserver mount"
Revision Changes Path
1.4 +23 -3 xml/htdocs/doc/en/vserver-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- vserver-howto.xml 6 Oct 2005 16:42:48 -0000 1.3
+++ vserver-howto.xml 19 Dec 2005 12:09:33 -0000 1.4
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.3 2005/10/06 16:42:48 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.4 2005/12/19 12:09:33 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -21,8 +21,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.1</version>
-<date>2005-10-06</date>
+<version>1.2</version>
+<date>2005-12-19</date>
<chapter>
<title>Introduction</title>
@@ -113,6 +113,26 @@
[ ] Compile Debugging Code
</pre>
+<note>
+If you are using reiserfs as your filesystem, you will need to enable extended
+attributes for reiserfs in your kernel config.
+</note>
+
+<pre caption="Configure reiserfs options">
+File systems --->
+ <*> Reiserfs support
+ [*] ReiserFS extended attributes
+</pre>
+
+<p>
+Additionally, you will need to specify the <c>attrs</c> option in
+<path>/etc/fstab</path> for your vserver partition:
+</p>
+
+<pre caption="Example fstab with extended attributes">
+/dev/hdb /vserver reiserfs noatime,attrs 0 0
+</pre>
+
<p>
After you've built and installed the kernel, update your boot loader and
finally reboot to see if the kernel boots correctly.
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2005-12-19 12:20 Jan Kundrat
0 siblings, 0 replies; 7+ messages in thread
From: Jan Kundrat @ 2005-12-19 12:20 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/19 12:20:59
Modified: xml/htdocs/doc/en vserver-howto.xml
Log:
Replacing ling to Hollow's devspace by link to our mirrors
Revision Changes Path
1.5 +6 -6 xml/htdocs/doc/en/vserver-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- vserver-howto.xml 19 Dec 2005 12:09:33 -0000 1.4
+++ vserver-howto.xml 19 Dec 2005 12:20:59 -0000 1.5
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.4 2005/12/19 12:09:33 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.5 2005/12/19 12:20:59 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -21,7 +21,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.2</version>
+<version>1.3</version>
<date>2005-12-19</date>
<chapter>
@@ -201,10 +201,10 @@
<body>
<p>
-We will use <c>vserver-new</c> to create the initial guest. You have to download
-a vserver prepared stage3 from
-<uri>http://dev.gentoo.org/~hollow/vserver/stages</uri> and the script will
-guide you through the creation process.
+You have to download a vserver prepared stage3 from one of
+<uri link="/main/en/mirrors.xml">our mirrors</uri>. Those stages are located
+under the <path>experimental/<arch>/vserver/</path> directory.
+Then use the <c>vserver-new</c> script to create the initial guest.
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2006-03-13 18:55 Josh Saddler
0 siblings, 0 replies; 7+ messages in thread
From: Josh Saddler @ 2006-03-13 18:55 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/03/13 18:55:37
Modified: vserver-howto.xml
Log:
Fixed code sample/description mismatch for bug 125948
Revision Changes Path
1.6 xml/htdocs/doc/en/vserver-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- vserver-howto.xml 19 Dec 2005 12:20:59 -0000 1.5
+++ vserver-howto.xml 13 Mar 2006 18:55:37 -0000 1.6
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.5 2005/12/19 12:20:59 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.6 2006/03/13 18:55:37 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -21,8 +21,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.3</version>
-<date>2005-12-19</date>
+<version>1.4</version>
+<date>2006-03-13</date>
<chapter>
<title>Introduction</title>
@@ -210,7 +210,7 @@
<p>
You have to choose a context ID for your vserver (dynamic context IDs are
discouraged) as well as the necessary network device information (In this
-example eth0 is configured with 192.168.1.254/24 and the context ID is
+example eth0 is configured with 192.168.1.253/24 and the context ID is
equivalent to the last two parts of the virtual servers IP).
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2006-03-17 10:26 Xavier Neys
0 siblings, 0 replies; 7+ messages in thread
From: Xavier Neys @ 2006-03-17 10:26 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 06/03/17 10:26:33
Modified: vserver-howto.xml
Log:
#Update from #126491
Revision Changes Path
1.7 xml/htdocs/doc/en/vserver-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.7&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml?rev=1.7&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/vserver-howto.xml.diff?r1=1.6&r2=1.7&cvsroot=gentoo
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- vserver-howto.xml 13 Mar 2006 18:55:37 -0000 1.6
+++ vserver-howto.xml 17 Mar 2006 10:26:33 -0000 1.7
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.6 2006/03/13 18:55:37 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.7 2006/03/17 10:26:33 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -21,8 +21,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.4</version>
-<date>2006-03-13</date>
+<version>1.5</version>
+<date>2006-03-17</date>
<chapter>
<title>Introduction</title>
@@ -70,7 +70,7 @@
</ti>
</tr>
<tr>
- <th>util-vserver, vserver utils</th>
+ <th>util-vserver</th>
<ti>
The <c>util-vserver</c> package contains all programs necessary for
maintaining your virtual servers
@@ -103,8 +103,7 @@
Linux VServer --->
[ ] Enable Legacy Kernel API
-<comment>(Do not set!)</comment>
- [ ] Disable Legacy Networking Kernel API
+ [*] Disable Legacy Networking Kernel API
<comment>(Highly recommended)</comment>
[*] Enable Proc Security
[*] Enable Hard CPU Limits
@@ -114,8 +113,10 @@
</pre>
<note>
-If you are using reiserfs as your filesystem, you will need to enable extended
-attributes for reiserfs in your kernel config.
+If you are using reiserfs as filesystem on the partition where guest images are
+stored, you will need to enable extended attributes for reiserfs in your
+kernel config and additionally add the <c>attrs</c> option in
+<path>/etc/fstab</path>.
</note>
<pre caption="Configure reiserfs options">
@@ -124,13 +125,8 @@
[*] ReiserFS extended attributes
</pre>
-<p>
-Additionally, you will need to specify the <c>attrs</c> option in
-<path>/etc/fstab</path> for your vserver partition:
-</p>
-
<pre caption="Example fstab with extended attributes">
-/dev/hdb /vserver reiserfs noatime,attrs 0 0
+/dev/hdb /vservers reiserfs noatime,attrs 0 0
</pre>
<p>
@@ -143,7 +139,7 @@
# <i>make</i>
<comment>(Installing)</comment>
# <i>make modules_install</i>
-# <i>cp arch/i386/boot/bzImage /boot/kernel-<KERNELVERSION>-vserver-<VSERVERVERSION></i>
+# <i>cp arch/<arch>/boot/bzImage /boot/kernel-<KERNELVERSION>-vserver-<VSERVERVERSION></i>
<comment>(Edit bootloader config file as required and)</comment>
# <i>reboot</i>
</pre>
@@ -156,23 +152,26 @@
<p>
To maintain your virtual servers you need the util-vserver package which
-contains all necessary programs and many usefull features.
+contains all necessary programs and many useful features. Be aware that there
+is also a package called <c>vserver-utils</c>. It is a new incarnation of the
+user-space implementation of the VServer kernel API, but not yet usable for
+production use.
</p>
<note>
-The tools and features used in this HowTo require
-<c>>=sys-apps/util-vserver-0.30.208-r3</c>. You may have to keyword it first.
+This version of the howto requires features only available in
+<c>>=sys-apps/util-vserver-0.30.210-r6</c>. You may have to keyword/upgrade
+it first.
</note>
-<pre caption="Install vserver utils">
+<pre caption="Install util-vserver">
# <i>emerge util-vserver</i>
</pre>
<p>
You have to run the <c>vprocunhide</c> command after every reboot in order to
-setup <path>/proc</path> permissions correctly for vserver use. An init script has
-been installed by util-vserver. To use it you should add it to a
-runlevel:
+setup <path>/proc</path> permissions correctly for vserver use. An init script
+has been installed by util-vserver. To use it you should add it to a runlevel:
</p>
<pre caption="vserver init script">
@@ -180,8 +179,13 @@
# <i>/etc/init.d/vservers start</i>
</pre>
+<note>
+This init script will also start your default vservers. Read below for more
+information.
+</note>
+
<p>
-The vshelper script is used to correctly stop and restart virtual servers. You
+The vshelper script is used to restart virtual servers correctly. You
have to tell the kernel where the vshelper script is located:
</p>
@@ -219,7 +223,7 @@
<i>--hostname gentoo \</i>
<i>--context 1253 \</i>
<i>--interface eth0:192.168.1.253/24 \</i>
- <i>stage3 /path/to/stage3-tarball.tar.bz2</i>
+ <i>stage3 /path/to/stage3-<arch>-<date>.tar.bz2 <arch></i>
</pre>
<note>
@@ -247,7 +251,7 @@
<pre caption="Create template tarball">
# <i>cd /vservers/gentoo-template</i>
-# <i>tar cjvpf ../gentoo-template.tar.bz2 ./</i>
+# <i>tar cjvpf ../gentoo-template-<arch>-<date>.tar.bz2 ./</i>
</pre>
<p>
@@ -260,12 +264,12 @@
<i>--hostname myguest \</i>
<i>--context 1252 \</i>
<i>--interface eth0:192.168.1.252/24 \</i>
- <i>template ./gentoo-template.tar.bz2</i>
+ <i>template ./gentoo-template-<arch>-<date>.tar.bz2 <arch></i>
</pre>
<note>
-You should use a shared portage tree for your guests to keep guests small in
-size. Edit <path>/etc/vservers/myguest/fstab</path> and uncomment the entries
+You should use a shared portage tree to keep guests small in size. Edit
+<path>/etc/vservers/myguest/fstab</path> and uncomment the entries
for <path>/usr/portage</path> and <path>/usr/portage/distfiles</path>. Guests
will have read-only access to <path>/usr/portage</path> and read-write access
to <path>/usr/portage/distfiles</path>.
@@ -302,13 +306,140 @@
</body>
</section>
+</chapter>
+
+<chapter>
+<title>Maintenance made easy</title>
+<section>
+<title>Start guests on boot</title>
+<body>
+
+<p>
+You can start certain guests during boot. Each guest can be assigned a MARK.
+Now everything you have to do is configure these MARKs in the guests
+configuration and tell the init script to run all MARKed guests.
+</p>
+
+<pre caption="Configure MARKs for each guest">
+<comment>(Do this for every guest you want to start)</comment>
+# <i>mkdir -p /etc/vservers/myguest/apps/init</i>
+# <i>echo "default" > /etc/vservers/myguest/apps/init/mark</i>
+</pre>
+
+<note>
+Since all guests marked with "default" are started by default, nothing more has
+to be done. If you have different marks you should also update
+<path>/etc/conf.d/vservers</path>.
+</note>
+
+</body>
+</section>
+<section>
+<title>Gentoo goodies</title>
+<body>
+
+<p>
+The util-vserver ebuild has installed some goodies for Gentoo guests. You know
+<c>vserver-new</c> from the previous chapter. In this chapter, you will learn
+how to use <c>vesync</c> and <c>vemerge</c> to keep portage in sync as well as
+<c>vupdateworld</c> and <c>vdispatch-conf</c> to update guests.
+</p>
+
+</body>
+</section>
+<section>
+<title>Keep portage in sync</title>
+<body>
+
+<p>
+The script <c>vesync</c> will help you to keep the metadata cache and overlays
+in sync. <c>vemerge</c> is a simple wrapper for <c>emerge</c> in guests.
+</p>
+
+<pre caption="Examples">
+<comment>(Sync metadata for 'myguest')</comment>
+# <i>vesync myguest</i>
+<comment>(Sync metadata for all guests)</comment>
+# <i>vesync -a</i>
+<comment>(Sync metadata for all guests except 'myguest')</comment>
+# <i>vesync -a -e myguest</i>
+<comment>(Sync 'myoverlay' for all guests)</comment>
+# <i>vesync -a \</i>
+ <i>--overlay /usr/local/overlays/myoverlay \</i>
+ <i>--overlay-host rsync://rsync.myhost.com/myoverlay \</i>
+ <i>--overlay-only</i>
+<comment>(emerge app-editors/vim in 'myguest')</comment>
+# <i>vemerge myguest app-editors/vim -va</i>
+</pre>
+
+<note>
+This script requires you to have a shared portage tree.
+</note>
+
+</body>
+</section>
+<section>
+<title>Update guests</title>
+<body>
+
+<p>
+Gentoo guests can share packages to save compilation time. In order to use
+shared packages, you have to create a central directory for packages on the
+host. We will use <path>/var/cache/vpackages</path> on the host and mount it
+to <path>/usr/portage/packages</path> in every guest.
+</p>
+
+<pre caption="Add bind mount to guest configuration">
+# <i>mkdir -p /var/cache/vpackages</i>
+# <i>$EDITOR /etc/vservers/myguest/fstab</i>
+<comment>(Add this line at the end)</comment>
+/var/cache/vpackages /usr/portage/packages none bind,rw 0 0
+</pre>
+
+<p>
+Now you can use <c>vupdateworld</c> to update every guest. The command is
+equivalent to something like <c>emerge --deep --update --newuse world</c>
+depending on command line options.
+</p>
+
+<pre caption="vupdateworld examples">
+<comment>(Pretend update for 'myguest')</comment>
+# <i>vupdateworld -p myguest</i>
+<comment>(Update 'myguest' using binary packages)</comment>
+# <i>vupdateworld -k myguest</i>
+<comment>(Update all guests using binary packages)</comment>
+# <i>vupdateworld -ka</i>
+</pre>
+
+<note>
+In order to get binary packages you can either use PORTAGE_BINHOST (see <c>man
+make.conf</c>) or set FEATURES="buildpkg" in one or more guests.
+</note>
+
+<p>
+After a successful update you can easily update all configuration files with
+<c>vdispatch-conf</c>. It is a simple wrapper for <c>dispatch-conf</c> and
+behaves exactly the same.
+</p>
+
+<pre caption="vdispatch-conf examples">
+<comment>(Update configuration files for 'myguest')</comment>
+# <i>vdispatch-conf myguest</i>
+<comment>(Update configuration files for all guests)</comment>
+# <i>vdispatch-conf -a</i>
+</pre>
+
+</body>
+</section>
+
<section>
<title>Contact</title>
<body>
<p>
-Please feel free to contact the author or file a bug on <uri
-link="http://bugs.gentoo.org">Bugzilla</uri> in case of any problems.
+Please feel free to contact the <mail link="hollow@gentoo.org">author</mail> or
+file a bug on <uri link="http://bugs.gentoo.org">Bugzilla</uri> in case of any
+problems.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
* [gentoo-doc-cvs] cvs commit: vserver-howto.xml
@ 2006-10-06 21:55 Josh Saddler
0 siblings, 0 replies; 7+ messages in thread
From: Josh Saddler @ 2006-10-06 21:55 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/10/06 21:55:24
Modified: vserver-howto.xml
Log:
changed vserver package category for bug 150318
Revision Changes Path
1.8 xml/htdocs/doc/en/vserver-howto.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vserver-howto.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vserver-howto.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vserver-howto.xml?r1=1.7&r2=1.8
Index: vserver-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- vserver-howto.xml 17 Mar 2006 10:26:33 -0000 1.7
+++ vserver-howto.xml 6 Oct 2006 21:55:24 -0000 1.8
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.7 2006/03/17 10:26:33 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.8 2006/10/06 21:55:24 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/vserver-howto.xml">
@@ -21,8 +21,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.5</version>
-<date>2006-03-17</date>
+<version>1.6</version>
+<date>2006-10-06</date>
<chapter>
<title>Introduction</title>
@@ -160,8 +160,8 @@
<note>
This version of the howto requires features only available in
-<c>>=sys-apps/util-vserver-0.30.210-r6</c>. You may have to keyword/upgrade
-it first.
+<c>>=sys-cluster/util-vserver-0.30.210-r6</c>. You may have to
+keyword/upgrade it first.
</note>
<pre caption="Install util-vserver">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-10-06 21:55 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-06 21:55 [gentoo-doc-cvs] cvs commit: vserver-howto.xml Josh Saddler
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 10:26 Xavier Neys
2006-03-13 18:55 Josh Saddler
2005-12-19 12:20 Jan Kundrat
2005-12-19 12:09 Jan Kundrat
2005-10-06 16:42 Jan Kundrat
2005-08-08 11:08 Xavier Neys
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox