From owner-freebsd-jail@FreeBSD.ORG Mon Jun 15 17:10:33 2015 Return-Path: Delivered-To: freebsd-jail@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AEBC6695; Mon, 15 Jun 2015 17:10:33 +0000 (UTC) (envelope-from kikuchan@uranus.dti.ne.jp) Received: from vsmtp07.dti.ne.jp (vsmtp07.dti.ne.jp [202.216.231.142]) by mx1.freebsd.org (Postfix) with ESMTP id 6A0097CF; Mon, 15 Jun 2015 17:10:32 +0000 (UTC) (envelope-from kikuchan@uranus.dti.ne.jp) Received: from mail.dream.jp (webmail01.ga.dti.ne.jp [202.216.229.152]) by vsmtp07.dti.ne.jp (3.11v) with ESMTP AUTH id t5FHAQ4b002127; Tue, 16 Jun 2015 02:10:26 +0900 (JST) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Date: Tue, 16 Jun 2015 02:10:26 +0900 From: To: "Bjoern A. Zeeb" Cc: , Subject: Re: How to implement jail-aware SysV IPC (with my nasty patch) In-Reply-To: <2B7AA933-CB74-4737-8330-6E623A31C6DA@lists.zabbadoz.net> References: <2B7AA933-CB74-4737-8330-6E623A31C6DA@lists.zabbadoz.net> Message-ID: X-Sender: kikuchan@uranus.dti.ne.jp User-Agent: DTI MyMail/0.3-trunk X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2015 17:10:33 -0000 On Mon, 15 Jun 2015 09:53:53 +0000, "Bjoern A. Zeeb" wrote: > Hi, > > removed hackers, added virtualization. > > >> On 12 Jun 2015, at 01:17 , kikuchan@uranus.dti.ne.jp wrote: >> >> Hello, >> >> I’m (still) trying to figure out how jail-aware SysV IPC mechanism should be. > > The best way probably is to finally get the “common” VIMAGE framework into HEAD to allow easy virtualisation of other services. That work has been sitting in perforce for a few years and simply needs updating for sysctls I think. > > Then use that to virtualise things and have a vipc like we have vnets. The good news is that you have identified most places and have the cleanup functions already so it’d be a matter of transforming your changes (assuming they are correct and working fine; haven’t actually read the patch in detail;-) to the different infrastructure. And that’s the easiest part. > > > Bjoern Hi Bjoern, Thank you for your reply. The "common" VIMAGE framework sounds good, I really want it. I want to know what the IPC system looks like for user-land after virtualized, and what happen if vnet like vipc is implemented. For example, jail 1, 2, 3 join vipc group A, and jail 4, 5, 6 join vipc group B ?? Hmm, it looks good. Regards, Kikuchan