From owner-freebsd-virtualization@FreeBSD.ORG Tue Jul 15 00:22:42 2008 Return-Path: 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 8FCA11065674 for ; Tue, 15 Jul 2008 00:22:42 +0000 (UTC) (envelope-from jamie@gritton.org) Received: from gritton.org (gritton.org [161.58.222.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6329E8FC15 for ; Tue, 15 Jul 2008 00:22:42 +0000 (UTC) (envelope-from jamie@gritton.org) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by gritton.org (8.13.6.20060614/8.13.6) with ESMTP id m6F0MeRb029509; Mon, 14 Jul 2008 18:22:40 -0600 (MDT) Message-ID: <487BEDCA.8090705@gritton.org> Date: Mon, 14 Jul 2008 18:22:34 -0600 From: James Gritton User-Agent: Thunderbird 2.0.0.9 (X11/20080228) MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org References: <487BE548.3050500@gritton.org> <487BEB21.6040407@elischer.org> <487BEB9F.3000502@elischer.org> In-Reply-To: <487BEB9F.3000502@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on gritton.org X-Virus-Status: Clean Cc: Julian Elischer Subject: Re: jail_set_vimage - Vimage under new jails X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 00:22:42 -0000 These jails are hierarchical. The "named-based" I refer to is the extensibility, where new named parameters can be set in the jail_set system call, rather than relying on a fixed structure. Perhaps I should just say "extensible" instead. - Jamie Julian Elischer wrote: >> James Gritton wrote: >> I've finished the merge of jail_set and Vimage. This uses the >> name-based jails instead of the jail-similar vimage frameworks, with >> Vimage's VNET stuff being enabled in a jail with the "vnet" parameter >> (in this scenario, it's optional whether a jail has its own network >> stack or just inherits its parent's). Once such a jail is set up, it >> behaves in the same way as a vimage does, as far as the network stack >> separation goes. The only difference is in administration, which uses >> the jail framework. > > I liked the hierarchical feature of the vimage system. > when you say "name based", do you mean the code you refer to is > not hierarchical?