| 1 |
neysx 05/08/08 11:08:24 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en vserver-howto.xml |
| 4 |
Log: |
| 5 |
Removed tabs, shortened links, applied coding style, **No Content Change** |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.2 +72 -61 xml/htdocs/doc/en/vserver-howto.xml |
| 9 |
|
| 10 |
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 |
| 11 |
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 |
| 12 |
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 |
| 13 |
|
| 14 |
Index: vserver-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v |
| 17 |
retrieving revision 1.1 |
| 18 |
retrieving revision 1.2 |
| 19 |
diff -u -r1.1 -r1.2 |
| 20 |
--- vserver-howto.xml 17 Jun 2005 10:06:56 -0000 1.1 |
| 21 |
+++ vserver-howto.xml 8 Aug 2005 11:08:24 -0000 1.2 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.1 2005/06/17 10:06:56 fox2mike Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vserver-howto.xml,v 1.2 2005/08/08 11:08:24 neysx Exp $ --> |
| 26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 27 |
|
| 28 |
<guide link="/doc/en/vserver-howto.xml"> |
| 29 |
@@ -31,7 +31,7 @@ |
| 30 |
<body> |
| 31 |
|
| 32 |
<p> |
| 33 |
-The basic concept of the Linux-VServer solution is to separate the user-space |
| 34 |
+The basic concept of the Linux-VServer solution is to separate the user-space |
| 35 |
environment into distinct units (sometimes called Virtual Private Servers) in |
| 36 |
such a way that each VPS looks and feels like a real server to the processes |
| 37 |
contained within. |
| 38 |
@@ -50,23 +50,31 @@ |
| 39 |
</tr> |
| 40 |
<tr> |
| 41 |
<th>Linux-VServer, VServer</th> |
| 42 |
- <ti>Linux-VServer is the official name of the project and used in this Howto |
| 43 |
- the same way</ti> |
| 44 |
+ <ti> |
| 45 |
+ Linux-VServer is the official name of the project and used in this Howto |
| 46 |
+ the same way |
| 47 |
+ </ti> |
| 48 |
</tr> |
| 49 |
<tr> |
| 50 |
<th>virtual server, vserver, guest system</th> |
| 51 |
- <ti>All these are interchangable and refer to one instance of a server (i.e. |
| 52 |
- one virtual server)</ti> |
| 53 |
+ <ti> |
| 54 |
+ All these are interchangable and refer to one instance of a server (i.e. |
| 55 |
+ one virtual server) |
| 56 |
+ </ti> |
| 57 |
</tr> |
| 58 |
<tr> |
| 59 |
<th>host system, host</th> |
| 60 |
- <ti>The physical machine running your Gentoo Linux will host all virtual |
| 61 |
- servers</ti> |
| 62 |
+ <ti> |
| 63 |
+ The physical machine running your Gentoo Linux will host all virtual |
| 64 |
+ servers |
| 65 |
+ </ti> |
| 66 |
</tr> |
| 67 |
<tr> |
| 68 |
<th>util-vserver, vserver utils</th> |
| 69 |
- <ti>The <c>util-vserver</c> package contains all programs necessary for |
| 70 |
- maintaining your virtual servers</ti> |
| 71 |
+ <ti> |
| 72 |
+ The <c>util-vserver</c> package contains all programs necessary for |
| 73 |
+ maintaining your virtual servers |
| 74 |
+ </ti> |
| 75 |
</tr> |
| 76 |
</table> |
| 77 |
|
| 78 |
@@ -85,7 +93,7 @@ |
| 79 |
</pre> |
| 80 |
|
| 81 |
<p> |
| 82 |
-After the vserver-sources are installed it's time to configure them using |
| 83 |
+After the vserver-sources are installed it's time to configure them using |
| 84 |
<c>make menuconfig</c>. |
| 85 |
</p> |
| 86 |
|
| 87 |
@@ -97,18 +105,18 @@ |
| 88 |
<comment>(Required by current utils)</comment> |
| 89 |
[*] Enable Legacy Kernel API |
| 90 |
<comment>(Do not set!)</comment> |
| 91 |
- [ ] Disable Legacy Networking Kernel API |
| 92 |
+ [ ] Disable Legacy Networking Kernel API |
| 93 |
<comment>(Highly recommended)</comment> |
| 94 |
- [*] Enable Proc Security |
| 95 |
+ [*] Enable Proc Security |
| 96 |
[ ] Enable Hard CPU Limits |
| 97 |
- Persistent Inode Context Tagging (UID24/GID24) ---> |
| 98 |
+ Persistent Inode Context Tagging (UID24/GID24) ---> |
| 99 |
[ ] Tag NFSD User Auth and Files |
| 100 |
[ ] Compile Debugging Code |
| 101 |
</pre> |
| 102 |
|
| 103 |
<p> |
| 104 |
-After you've built and installed the kernel, update your boot loader and finally |
| 105 |
-reboot to see if the kernel boots correctly. |
| 106 |
+After you've built and installed the kernel, update your boot loader and |
| 107 |
+finally reboot to see if the kernel boots correctly. |
| 108 |
</p> |
| 109 |
|
| 110 |
<pre caption="Install the kernel"> |
| 111 |
@@ -137,12 +145,12 @@ |
| 112 |
</pre> |
| 113 |
|
| 114 |
<p> |
| 115 |
-If you use Proc Security you have to "unhide" certain files in your |
| 116 |
-<path>/proc</path> directory in order to make them available in virtual servers. |
| 117 |
-There is a script called <c>vprocunhide</c> in |
| 118 |
-<path>/usr/lib/util-vserver</path> which unhides files specified in |
| 119 |
+If you use Proc Security you have to "unhide" certain files in your |
| 120 |
+<path>/proc</path> directory in order to make them available in virtual |
| 121 |
+servers. There is a script called <c>vprocunhide</c> in |
| 122 |
+<path>/usr/lib/util-vserver</path> which unhides files specified in |
| 123 |
<path>/usr/lib/util-vserver/defaults/vprocunhide-files</path>. The util-vserver |
| 124 |
-ebuild installed a init-script which uses the <c>vprocunhide</c> command. Add |
| 125 |
+ebuild installed a init-script which uses the <c>vprocunhide</c> command. Add |
| 126 |
it to your runlevel: |
| 127 |
</p> |
| 128 |
|
| 129 |
@@ -152,8 +160,8 @@ |
| 130 |
</pre> |
| 131 |
|
| 132 |
<p> |
| 133 |
-The vshelper script is used to correctly stop and restart virtual servers. |
| 134 |
-You have to tell the kernel where the vshelper script is located: |
| 135 |
+The vshelper script is used to correctly stop and restart virtual servers. You |
| 136 |
+have to tell the kernel where the vshelper script is located: |
| 137 |
</p> |
| 138 |
|
| 139 |
<pre caption="vshelper setup"> |
| 140 |
@@ -168,9 +176,9 @@ |
| 141 |
<body> |
| 142 |
|
| 143 |
<p> |
| 144 |
-You have to create some configuration files and directories to get your |
| 145 |
-virtual server up and running. We use the skeleton build mode from the |
| 146 |
-util-vserver package to setup our basic configuration. |
| 147 |
+You have to create some configuration files and directories to get your virtual |
| 148 |
+server up and running. We use the skeleton build mode from the util-vserver |
| 149 |
+package to setup our basic configuration. |
| 150 |
</p> |
| 151 |
|
| 152 |
<p> |
| 153 |
@@ -181,8 +189,8 @@ |
| 154 |
|
| 155 |
<p> |
| 156 |
There is a new baselayout-vserver ebuild in portage which supports the plain |
| 157 |
-init-style, i.e.; you don't have to use the gentoo init style anymore. The |
| 158 |
-plain init-style uses <c>init</c> and <path>/etc/inittab</path> to manage |
| 159 |
+init-style, i.e.; you don't have to use the gentoo init style anymore. The |
| 160 |
+plain init-style uses <c>init</c> and <path>/etc/inittab</path> to manage |
| 161 |
runlevels and init scripts (considered more stable and is the default now). |
| 162 |
</p> |
| 163 |
|
| 164 |
@@ -202,9 +210,9 @@ |
| 165 |
</pre> |
| 166 |
|
| 167 |
<impo> |
| 168 |
-Per default the virtual server is allowed to set the hostname itself. Be |
| 169 |
-sure to change <path>/etc/conf.d/hostname</path> in your virtual server later |
| 170 |
-to match the hostname above. |
| 171 |
+Per default the virtual server is allowed to set the hostname itself. Be sure |
| 172 |
+to change <path>/etc/conf.d/hostname</path> in your virtual server later to |
| 173 |
+match the hostname above. |
| 174 |
</impo> |
| 175 |
|
| 176 |
</body> |
| 177 |
@@ -214,10 +222,10 @@ |
| 178 |
<body> |
| 179 |
|
| 180 |
<p> |
| 181 |
-We are creating a Gentoo template which we can copy later to get |
| 182 |
-multiple virtual servers easily. The vserver build-script created |
| 183 |
-some basic directories in <path>/vservers/gentoo</path> which |
| 184 |
-are installed by a stage anyway, so we remove them first. |
| 185 |
+We are creating a Gentoo template which we can copy later to get multiple |
| 186 |
+virtual servers easily. The vserver build-script created some basic directories |
| 187 |
+in <path>/vservers/gentoo</path> which are installed by a stage anyway, so we |
| 188 |
+remove them first. |
| 189 |
</p> |
| 190 |
|
| 191 |
<pre caption="Remove skeleton files"> |
| 192 |
@@ -225,48 +233,51 @@ |
| 193 |
</pre> |
| 194 |
|
| 195 |
<p> |
| 196 |
-You have to install a regular Gentoo system now. You can follow most |
| 197 |
-of the Gentoo Handbook with some limitations and additions: |
| 198 |
+You have to install a regular Gentoo system now. You can follow most of the |
| 199 |
+Gentoo Handbook with some limitations and additions: |
| 200 |
</p> |
| 201 |
|
| 202 |
<ul> |
| 203 |
- <li>Replace <path>/mnt/gentoo</path> with |
| 204 |
- <path>/vservers/gentoo</path> |
| 205 |
- </li> |
| 206 |
- <li>Choose the <path>vserver/x86</path> profile in |
| 207 |
- <uri link="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6#doc_chap1_sect6">chapter 6.a</uri> |
| 208 |
- </li> |
| 209 |
- <li>Use the vserver stages available |
| 210 |
- <uri link="http://dev.gentoo.org/~hollow/vserver/stages/">here</uri>. |
| 211 |
- </li> |
| 212 |
+ <li>Replace <path>/mnt/gentoo</path> with <path>/vservers/gentoo</path></li> |
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
-- |
| 217 |
gentoo-doc-cvs@g.o mailing list |
Archives