Date: Sun, 29 May 2016 09:33:57 -0700 From: Tim Kientzle <tim@kientzle.com> To: Julian Elischer <julian@freebsd.org> Cc: "bapt@freebsd.org" <bapt@freebsd.org>, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: pkg chroot issues? Message-ID: <07425DF9-AD45-49FD-AC9B-DEF39BDAA10E@kientzle.com> In-Reply-To: <8886a4b1-492b-61ea-90ea-7e694311d03b@freebsd.org> References: <9BC1A0E1-696D-4C00-B8C8-B57C4DB3A8EF@kientzle.com> <20160522203108.GE11189@ivaldir.etoilebsd.net> <20160522203243.GF11189@ivaldir.etoilebsd.net> <8886a4b1-492b-61ea-90ea-7e694311d03b@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On May 29, 2016, at 8:55 AM, Julian Elischer <julian@freebsd.org> = wrote: >=20 > I was thinking that in order to do this properly the chrooted child = should do all it's fetch requests etc via the non-chrooted parent, but = that would have probably been a bit too complicated. (including add = requests) How complex would it be to perform all of the fetch requests before = chroot? Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07425DF9-AD45-49FD-AC9B-DEF39BDAA10E>