From owner-freebsd-current@FreeBSD.ORG  Tue Jul  9 12:21:51 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id F1F52E07;
 Tue,  9 Jul 2013 12:21:50 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 by mx1.freebsd.org (Postfix) with ESMTP id CABF51C9E;
 Tue,  9 Jul 2013 12:21:50 +0000 (UTC)
Received: from Julian-MBP3.local (124-169-161-9.dyn.iinet.net.au
 [124.169.161.9]) (authenticated bits=0)
 by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id r69CLjCM011827
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Tue, 9 Jul 2013 05:21:49 -0700 (PDT)
 (envelope-from julian@freebsd.org)
Message-ID: <51DC0054.2040703@freebsd.org>
Date: Tue, 09 Jul 2013 20:21:40 +0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: FreeBSD Current <current@freebsd.org>, Jamie Gritton <jamie@freebsd.org>
Subject: chroots/jails in jails
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2013 12:21:51 -0000

I'm making a build system for a project which creates a chroot in 
which to do some of the building to avoid base-system contamination 
(yeah I know lots of people do that).
the trick is that my test system is itself, a jail.
So I can not mount /dev in the chroot.

I can not predict where a build will occur so I can not pre-mount the 
devfs from outside the jail. (users may fire off builds in different 
locations)

Does anyone have any solution to this problem?

We have hierarchical jails, but no way of allowing the parent jail to 
give the child jail a devfs.

Has anyone looked at what it would take to make devfs "jail friendly"?

I'm guessing that the jail would have to get some devfs-rule parameter 
and that mount_devfs or it's in-kernel parts would have to know what 
to do..

seems like there should be someone out there who has hit this.. (and 
solved it?)

Julian