CT0 - Revision history

Kir: VE->CT

2009-10-28T15:42:57Z

VE->CT

Kir: VE0->CT0

2008-03-11T12:03:04Z

VE0->CT0

Kir: VE0->CT0

2008-03-11T11:43:49Z

VE0->CT0

Kir: VE0 moved to CT0

2008-03-11T11:40:29Z

VE0 moved to CT0

Kir: VE->container

2008-03-11T09:51:56Z

VE->container

Botinki Kira: Robot: Automated text replacement (-VEs +containers)

2008-03-11T09:51:07Z

Robot: Automated text replacement (-VEs +containers)

Kir: Reverted edits by Avol (Talk); changed back to last version by Kir

2007-04-11T09:55:56Z

Reverted edits by Avol (Talk); changed back to last version by Kir

Avol at 09:50, 11 April 2007

2007-04-11T09:50:52Z

Kir: expanded a bit

2006-09-05T14:33:50Z

expanded a bit

Kir: Created

2006-06-06T10:11:46Z

Created

New page

In OpenVZ, you have multiple [[VE]]s, as well as the host system, which is otherwise known as '''VE0'''.

From VE0, you can use [[vzctl]] and other tools to manage [[VE]]s.

From VE0, all the VEs' processes, files, etc. are accessible.

== See also ==
* [[Hardware Node]]

[[Category: Definitions]]

← Older revision		Revision as of 15:42, 28 October 2009
Line 1:		Line 1:
−	In OpenVZ, you have multiple [[VE]]s, as well as the '''host system''' itself, which is otherwise known as '''CT0''' or '''VE0'''. In other words, CT0 means the server itself.	+	In OpenVZ, you have multiple [[CT]]s, as well as the '''host system''' itself, which is otherwise known as '''CT0''' or '''VE0'''. In other words, CT0 means the server itself.

	From CT0, you can use [[vzctl]] and other tools to manage [[container]]s. From CT0, all the containers' processes, files, etc. are accessible. From CT0, you manage the hardware, install a new kernel, etc.		From CT0, you can use [[vzctl]] and other tools to manage [[container]]s. From CT0, all the containers' processes, files, etc. are accessible. From CT0, you manage the hardware, install a new kernel, etc.

@@ Line 1: / Line 1: @@
 In OpenVZ, you have multiple [[VE]]s, as well as the '''host system''' itself, which is otherwise known as '''CT0''' or '''VE0'''. In other words, CT0 means the server itself.
-From CT0, you can use [[vzctl]] and other tools to manage [[container]]s. From CT0, all the containers' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
+From CT0, you can use [[vzctl]] and other tools to manage [[container]]s. From CT0, all the containers' processes, files, etc. are accessible. From CT0, you manage the hardware, install a new kernel, etc.
 == See also ==

@@ Line 1: / Line 1: @@
-In OpenVZ, you have multiple [[VE]]s, as well as the '''host system''', which is otherwise known as '''VE0'''. In other words, VE0 means the server itself.
+In OpenVZ, you have multiple [[VE]]s, as well as the '''host system''' itself, which is otherwise known as '''CT0''' or '''VE0'''. In other words, CT0 means the server itself.
-From VE0, you can use [[vzctl]] and other tools to manage [[container]]s. From VE0, all the containers' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
+From CT0, you can use [[vzctl]] and other tools to manage [[container]]s. From CT0, all the containers' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
 == See also ==
-* [[Hardware Node]]
+* [[Hardware Node]] == [[Host system]]
 [[Category: Definitions]]

@@ Line 1: / Line 1: @@
 In OpenVZ, you have multiple [[VE]]s, as well as the '''host system''', which is otherwise known as '''VE0'''. In other words, VE0 means the server itself.
-From VE0, you can use [[vzctl]] and other tools to manage [[VE]]s. From VE0, all the containers' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
+From VE0, you can use [[vzctl]] and other tools to manage [[container]]s. From VE0, all the containers' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
 == See also ==

@@ Line 1: / Line 1: @@
 In OpenVZ, you have multiple [[VE]]s, as well as the '''host system''', which is otherwise known as '''VE0'''. In other words, VE0 means the server itself.
-From VE0, you can use [[vzctl]] and other tools to manage [[VE]]s. From VE0, all the VEs' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
+From VE0, you can use [[vzctl]] and other tools to manage [[VE]]s. From VE0, all the containers' processes, files, etc. are accessible. From VE0, you manage the hardware, install a new kernel, etc.
 == See also ==

← Older revision	Revision as of 11:40, 11 March 2008
(No difference)

← Older revision		Revision as of 09:55, 11 April 2007
Line 7:		Line 7:

	[[Category: Definitions]]		[[Category: Definitions]]
−
−	~~http://musiic-63476s.dyatlyonok.org/~~
−	~~http://muusic-63476s.lyagushonok.org/~~
−	~~http://eebay-63476s.volchonok.org/~~
−	~~http://ebbay-63476s.drozdyonok.org/~~
−	~~http://resteraunts-63476s.dyatlyonok.org/~~
−	~~http://restarants-63476s.medvezhonok.org/~~
−	~~http://restaurents-63476s.medvezhonok.org/~~
−	~~http://insurence-cars-63476s.zubryonok.org/~~
−	~~http://celebritynudes-63476s.kabanyonok.org/~~
−	~~http://adullt-63476s.lyagushonok.org/~~

← Older revision		Revision as of 09:50, 11 April 2007
Line 7:		Line 7:

	[[Category: Definitions]]		[[Category: Definitions]]
		+
		+	http://musiic-63476s.dyatlyonok.org/
		+	http://muusic-63476s.lyagushonok.org/
		+	http://eebay-63476s.volchonok.org/
		+	http://ebbay-63476s.drozdyonok.org/
		+	http://resteraunts-63476s.dyatlyonok.org/
		+	http://restarants-63476s.medvezhonok.org/
		+	http://restaurents-63476s.medvezhonok.org/
		+	http://insurence-cars-63476s.zubryonok.org/
		+	http://celebritynudes-63476s.kabanyonok.org/
		+	http://adullt-63476s.lyagushonok.org/