+ # with vserver 2.3, granting the vserver CAP_MKNOD is not enough
+ # check whether we run vs2.3 or above
+ vs_version=$(uname -a | sed -e 's,.*[\.\-]vs\([0-9]\)\.\([0-9]\)\..*,\1\2,')
+ # at this stage we have here 22 or 23
+ need_vdevmap=$(( $vs_version >= 23 ))
+
+ if [ "$need_vdevmap" == 1 ] ; then
+ util_vserver_215=0
+ vdevmap --help | grep -- --set &> /dev/null && util_vserver_215=1
+
+ if [ "$util_vserver_215" == 1 ] ; then
+ ctx=$(cat /etc/vservers/$vserver/context)
+ vdevmap --set --xid $ctx --open --create --target /dev/null
+ vdevmap --set --xid $ctx --open --create --target /dev/root
+ else
+ echo "You seem to be running vs2.3 with util-vserver < 0.30.215"
+ echo "This combination is not supported by $COMMAND"
+ echo "Please upgrade your environment"
+ exit 1
+# this supposedly is an equivalent to using vdevmap as invoked above
+# but it's not going to work in this case
+# mkdir -p /etc/vservers/$vserver/apps/vdevmap/default-{block,char}
+# touch /etc/vservers/$vserver/apps/vdevmap/default-{block,char}/{open,create}
+# echo /dev/root > /etc/vservers/$vserver/apps/vdevmap/default-block/target
+# echo /dev/null > /etc/vservers/$vserver/apps/vdevmap/default-char/target
+ fi
+ fi
+
+ # minimal config in the vserver for yum to work
+ configure_yum_in_vserver $vserver $fcdistro