Date: Sun, 9 Jan 2011 10:05:25 -0600 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Subbsd <subbsd@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: way for determine VIMAGE feature Message-ID: <AANLkTimnJhTj%2BVqqz0H1FdgLuMO6cd7svq=VBsit_YcR@mail.gmail.com> In-Reply-To: <AANLkTi=wSg%2BjNcV0QQs1_GJ1B3bEe7McLggO1bMshvpz@mail.gmail.com> References: <AANLkTi=wSg%2BjNcV0QQs1_GJ1B3bEe7McLggO1bMshvpz@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Sun, Jan 9, 2011 at 9:17 AM, Subbsd <subbsd@gmail.com> wrote: > Hi > > is there any mechanism to find out from userland is supports the > current kernel VIMAGE or not? something like 'sysctl > kern.features.vnet=1' ? > Thanks I've not been able to determine this either, but as it requires kernel re-configuration, I usually just know. In my scripts, I make sure and fail if the call to create a vnet jail fails: sh -c 'TEST=$(sudo jail -c vnet name=test host.hostname=test path=/) ; if [ $? = "1" ]; then echo "VIMAGE NOT AVAILABLE" ; exit 1 ; fi' ...or something like that. There may be a better way, or perhaps there should be. -Brandonhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimnJhTj%2BVqqz0H1FdgLuMO6cd7svq=VBsit_YcR>