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> -- [email protected] mailing list
