Date: Tue, 05 Aug 2014 19:40:56 +1200 From: mailinglists <mailinglists@debank.tv> To: freebsd-jail@freebsd.org Subject: Re: ezjail and mergemaster Message-ID: <53E08A88.1030007@debank.tv> In-Reply-To: <alpine.BSF.2.11.1408041707100.34818@wonkity.com> References: <alpine.BSF.2.11.1407291519270.34044@wonkity.com> <53D81D43.6070503@freebsd.org> <alpine.BSF.2.11.1408041707100.34818@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Rob Evers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E08A88.1030007>