Difference between revisions of "OS template"
(added noinclude tags) |
m (add 'translate' tags) |
||
| Line 1: | Line 1: | ||
| + | <translate> | ||
An '''OS template''' is basically a set of packages from some Linux distribution used to populate a [[container]]. With OpenVZ, different distributions can co-exist on the same hardware box, so multiple OS templates can be available. | An '''OS template''' is basically a set of packages from some Linux distribution used to populate a [[container]]. With OpenVZ, different distributions can co-exist on the same hardware box, so multiple OS templates can be available. | ||
| Line 7: | Line 8: | ||
* [[OS template cache]] | * [[OS template cache]] | ||
* [[OS template cache preparation]] | * [[OS template cache preparation]] | ||
| + | </translate> | ||
[[Category: Definitions]] | [[Category: Definitions]] | ||
[[Category: Templates]] | [[Category: Templates]] | ||
</noinclude> | </noinclude> | ||
Revision as of 22:42, 25 December 2015
<translate> An OS template is basically a set of packages from some Linux distribution used to populate a container. With OpenVZ, different distributions can co-exist on the same hardware box, so multiple OS templates can be available.
An OS template consists of system programs, libraries, and scripts needed to boot up and run the system (container), as well as some very basic applications and utilities. Applications like a compiler and an SQL server are usually not included into an OS template.
See also
</translate>
