From owner-freebsd-jail@FreeBSD.ORG Tue Aug 5 12:50:00 2014 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 07BB8453 for ; Tue, 5 Aug 2014 12:50:00 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AF74D25A0 for ; Tue, 5 Aug 2014 12:49:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s75Cnt6c066872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 5 Aug 2014 06:49:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s75CntRD066869; Tue, 5 Aug 2014 06:49:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 5 Aug 2014 06:49:55 -0600 (MDT) From: Warren Block To: mailinglists Subject: Re: ezjail and mergemaster In-Reply-To: <53E08A88.1030007@debank.tv> Message-ID: References: <53D81D43.6070503@freebsd.org> <53E08A88.1030007@debank.tv> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 05 Aug 2014 06:49:55 -0600 (MDT) Cc: freebsd-jail@freebsd.org X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2014 12:50:00 -0000 On Tue, 5 Aug 2014, mailinglists wrote: > On 5/08/14 11:13 am, Warren Block wrote: >> On Tue, 29 Jul 2014, Allan Jude wrote: >> >>> On 2014-07-29 17:44, Warren Block wrote: >>>> >>>> What process for running mergemaster should I suggest? Maybe different >>>> ones for trusted and untrusted jails? >>> >>> This will mount /usr/src into the basejail read-only: >>> >>> mount -t nullfs -o ro /usr/src /usr/jails/basejail/usr/src >> >> Thank you. I took the easy way out, by showing how to mount the >> source in the jails and just mentioning mergemaster. >> >> Draft version: >> http://www.wonkity.com/~wblock/jails/jails-ezjail.html >> _______________________________________________ > > Would it be an idea to list the files that can be excluded from > mergemaster updates, a lot of the rc scripts are a no-op inside a jail, > if one has to update a large number of ports this can make a real > difference. > > I guess ideally mergemaster itself could be extended to include a flag > to indicate it's run inside (or targeted at) a jail and remove/ignore rc > scripts that will never be used but that's probably outside the scope of > this discussion. A more predictable and possibly safer way is to manually add a standard list of ignorable jail files to IGNORE_FILES in /etc/mergemaster.rc. However, now I find that just null-mounting the source on the basejail is not enough. /usr/src is still empty inside the jails. There is a configuration option or something for this, I think, I just can't recall it.