On Mon, May 16, 2016 at 12:23:30PM +0100, Tony Finch wrote:
> Marc Haber wrote:
> > in Debian, the bind9 packages have recently started to trouble me in
> > chrooted environments since some cryptographic libraries are loaded
> > after bind has chrooted itself, which
On Mon, May 16, 2016 at 08:09:05AM -0400, Matthew Pounsett wrote:
> On 16 May 2016 at 04:38, Marc Haber wrote:
> > I have filed Debian Bug #820974 (http://bugs.debian.org/820974)
> > accordingly. The Debian bind people suggest that I copy the respective
> > libraries
On Mon, May 16, 2016 at 08:51:41PM -0400, Paul Kosinski wrote:
> I have avoided the problem chroot causes in a fairly general fashion by
> using "mount --bind". For example:
>
> /bin/mount --bind /lib /chroot/dns/lib
>
> will make the entire /lib directory available to the chrooted BIND,
>
I have avoided the problem chroot causes in a fairly general fashion by
using "mount --bind". For example:
/bin/mount --bind /lib /chroot/dns/lib
will make the entire /lib directory available to the chrooted BIND,
assuming the path /chroot/dns is created beforehand to serve as the
chroot base
On 16 May 2016 at 04:38, Marc Haber wrote:
> I have filed Debian Bug #820974 (http://bugs.debian.org/820974)
> accordingly. The Debian bind people suggest that I copy the respective
> libraries to the chroot so that bind can find them.
>
Yeah, this has been the fix
Marc Haber wrote:
>
> in Debian, the bind9 packages have recently started to trouble me in
> chrooted environments since some cryptographic libraries are loaded
> after bind has chrooted itself, which results - in the case of a
> minimal chroot - in a fatal run-time
Hi,
in Debian, the bind9 packages have recently started to trouble me in
chrooted environments since some cryptographic libraries are loaded
after bind has chrooted itself, which results - in the case of a
minimal chroot - in a fatal run-time error:
May 14 21:57:17 fan named[28066]: starting
7 matches
Mail list logo