From owner-freebsd-virtualization@FreeBSD.ORG  Wed Jun 18 19:57:01 2008
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2FE80106566C
	for <freebsd-virtualization@freebsd.org>;
	Wed, 18 Jun 2008 19:57:01 +0000 (UTC) (envelope-from zec@icir.org)
Received: from xaqua.tel.fer.hr (xaqua.tel.fer.hr [161.53.19.25])
	by mx1.freebsd.org (Postfix) with ESMTP id B02BE8FC20
	for <freebsd-virtualization@freebsd.org>;
	Wed, 18 Jun 2008 19:57:00 +0000 (UTC) (envelope-from zec@icir.org)
Received: by xaqua.tel.fer.hr (Postfix, from userid 20006)
	id CD0929B646; Wed, 18 Jun 2008 21:56:59 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on xaqua.tel.fer.hr
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.7
Received: from [192.168.200.112] (zec2.tel.fer.hr [161.53.19.79])
	by xaqua.tel.fer.hr (Postfix) with ESMTP id E6AAD9B644;
	Wed, 18 Jun 2008 21:56:58 +0200 (CEST)
From: Marko Zec <zec@icir.org>
To: James Gritton <jamie@gritton.org>
Date: Wed, 18 Jun 2008 21:56:37 +0200
User-Agent: KMail/1.9.7
References: <48588595.7020709@gritton.org> <200806182140.23123.zec@icir.org>
	<4859661E.9070502@gritton.org>
In-Reply-To: <4859661E.9070502@gritton.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200806182156.37998.zec@icir.org>
Cc: freebsd-virtualization@freebsd.org
Subject: Re: V_* meta-symbols and locking
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
	<freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>,
	<mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>,
	<mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2008 19:57:01 -0000

On Wednesday 18 June 2008 21:46:38 James Gritton wrote:
> Marko Zec wrote:
>  > The only thing I'd like to have
>  > as an option is to be able to spawn a new process in the target VM
>  > _without_ making it chrooted...
>
> If you mean creating a jail that's not chrooted, that's no problem.
> If you mean creating a jail that *is* chrooted, and then placing a
> process into that jail without chrooting it, that would be a breakage
> of the jail paradigm.  Hopefully you mean the former?

No, I want the later, as an option.  Given that the parent environment / 
jail completely controls the child anyhow, I don't think such an 
(optional) behavior would be too big a security issue.

Marko