Difference between revisions of "Talk:Debian template creation"
(answered →edit/symlink /etc/mtab, /proc/mounts) |
|||
Line 1: | Line 1: | ||
== edit/symlink /etc/mtab, /proc/mounts == | == edit/symlink /etc/mtab, /proc/mounts == | ||
Does anybody have valuable information why this would make sense and if this is needed? | Does anybody have valuable information why this would make sense and if this is needed? | ||
− | http://wiki.openvz.org/Debian_template_creation#Fix_.2Fetc.2Fmtab | + | http://wiki.openvz.org/Debian_template_creation#Fix_.2Fetc.2Fmtab {{unsigned|Juggler|20:41, 13 February 2007}} |
+ | |||
+ | : Linking /etc/mtab -> /proc/mounts is needed since VE's root filesystem is actually mounted from the [[Hardware Node]]. Thus, there is no appropriate record in /etc/mtab, so utilities like df fail to work (since they get a list of mounts from the /etc/mtab). After linking /etc/mtab to /proc/mounts, /etc/mtab shows all the mounts, including the one for root filesystem, so df works fine. --[[User:Kir|Kir]] 10:25, 14 February 2007 (EST) | ||
== problem with path == | == problem with path == |
Revision as of 15:25, 14 February 2007
edit/symlink /etc/mtab, /proc/mounts
Does anybody have valuable information why this would make sense and if this is needed? http://wiki.openvz.org/Debian_template_creation#Fix_.2Fetc.2Fmtab —The preceding unsigned comment was added by Juggler (talk • contribs) 20:41, 13 February 2007.
- Linking /etc/mtab -> /proc/mounts is needed since VE's root filesystem is actually mounted from the Hardware Node. Thus, there is no appropriate record in /etc/mtab, so utilities like df fail to work (since they get a list of mounts from the /etc/mtab). After linking /etc/mtab to /proc/mounts, /etc/mtab shows all the mounts, including the one for root filesystem, so df works fine. --Kir 10:25, 14 February 2007 (EST)
problem with path
Hi all, This is my first trial with openVZ and a wiki. Please give me some hints, if anything is wrong. Don't hesitate to correct my poor english.
I just installed openVZ on a rather old test box with Debian. Installation failed at first and I suppose there is a wrong path statement used for the debian packages.
When I came to
vzctl start 777
I received the message
Starting VE ...
VE private area /var/lib/vz/private/777 does not exist
Moving the directory 777 from /vz/private to /var/lib/vz/private solves this problem.
Now I could start and enter the new VE.
Debian template creation
For backward compablity to main OpenVZ:
Create a symlink from /var/lib/vz to /vz
# ln -s /var/lib/vz /vz