PLDWWW: Vserver
glen
glen at pld-linux.org
Sun Jan 8 13:46:07 CET 2006
Author: glen Date: Sun Jan 8 12:46:07 2006 GMT
Module: PLDWWW URL: http://www.pld-linux.org/Vserver
---- Log message:
restored my changes
---- Page affected: Vserver
---- Diffs:
================================================================
* {{{prefix}}} The network prefix-length.
* {{{scope}}} The scope of the network interface.
+
== Managing packages ==
- You can manage your packges using {{{vpoldek}}}:
+ You should decide your package management policy
- Syntax: {{{vpoldek <VSERVER> -- [REGULAR POLDEK OPTIONS]}}}
+ benefits managing packages externally
+ * provides extra security
+ * avoids duplicating rpm database and installed libraries/packages.
- For example:
+ benefits of managing packages internally
+ * moving vserver might be easier
+ * no dependency on host vserver rpm version or libraries.
+
+ === external package management ===
+
+ * with poldek
+ Syntax: vpoldek VSERVER -- REGULAR POLDEK OPTIONS
+
+
{{{
- # vpoldek test -- -u squid
+ vpoldek test -- -u squid
}}}
- You can also use {{{vrpm}}}:
+ * with rpm
+ Syntax: vrpm VSERVER -- REGULAR RPM OPTIONS
- Syntax: {{{vrpm <VSERVER> -- [REGULAR RPM OPTIONS]}}}
-
- For example:
{{{
- # vrpm test -- -qa 'apache-*'
+ vrpm test -- -qa 'apache-*'
}}}
- You should always manage your packages from the outside of your vserver. It provides extra security and avoids duplicating RPM database and installed libraries/packages. If you have no good reason for doing otherwise, keep it outside.
+ === internal package management ===
- To convert {{{rpmdb}}} from outside of the guest to inside, see this doc:
+
+ to convert rpmdb to inside there's doc:
{{{
- $ less /usr/share/doc/util-vserver-build-0.30.209/package-menagament.txt.gz
+ less /usr/share/doc/util-vserver-build-0.30.209/package-menagament.txt.gz
}}}
+
== Using plain init style ==
More information about the pld-cvs-commit
mailing list