base @PKGLIBDIR@/defaults/environment
build @PKGLIBDIR@/defaults/fstab
build @PKGLIBDIR@/defaults/debootstrap.uri
+build @PKGLIBDIR@/defaults/context.start
@ENSC_HAVE_C99_COMPILER_TRUE@build @PKGLIBDIR@/defaults/vunify-exclude
base @PKGLIBDIR@/capchroot
base @PKGLIBDIR@/chain-echo
misc/mtab \
misc/vprocunhide-files \
misc/vunify-exclude \
- misc/environment
+ misc/environment \
+ misc/context.start
nobase_distrib_SCRIPTS = redhat/initpost \
redhat/initpre \
The default fstab file to put in newly built guests.
</description>
</data>
+
+ <boolean name="context.dynamic">
+ <description>
+If this file exists, kernel-side dynamic contexts will be used by the "vserver
+... build" command. Otherwise a context will be generated, based on the
+contents of <optionref>context.next</optionref>.
+ </description>
+ </boolean>
+
+ <scalar id="context.next" name="context.next">
+ <description>
+The context id to use for the next guest created by "vserver ... build".
+ </description>
+ </scalar>
<collection name="apps">
<collection name="pkgmgmt">
findFile SETUP_FSTAB "$__CONFDIR"/.defaults/fstab "$__PKGLIBDEFAULTDIR"/fstab
}
+function _setup_generateContext
+{
+ if test -z "$SETUP_CONTEXT" && test ! -e "$__CONFDIR/.defaults/context.dynamic"; then
+ if test -e "$__CONFDIR/.defaults/context.next"; then
+ SETUP_CONTEXT=`$_CAT "$__CONFDIR/.defaults/context.next"`
+ else
+ SETUP_CONTEXT=`$_CAT "$__PKGLIBDEFAULTDIR/context.start"`
+ fi
+ expr "$SETUP_CONTEXT" + 1 > "$__CONFDIR/.defaults/context.next"
+ fi
+}
+
function setup_writeOption
{
local name=$1
mkdir -p "$cfgdir"/interfaces "$cfgdir"/apps/init "$cfgdir"/uts "$cfgdir"/cpuset
+ _setup_generateContext
+
_setup_writeSingleOption "$name" "$cfgdir"/name
_setup_writeSingleOption "$SETUP_CONTEXT" "$cfgdir"/context
_setup_writeSingleOption "$SETUP_HOSTNAME" "$cfgdir"/uts/nodename