Date: Mon, 28 May 2018 17:13:28 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: ldconfig(8) oddity on 11.2-BETA3? Message-ID: <alpine.BSF.2.21.999.1805281708100.89219@mail.fig.ol.no> In-Reply-To: <alpine.BSF.2.21.999.1805281509400.89219@mail.fig.ol.no> References: <CAJuc1zPurH94998BhcHGZOqAu04VV3pNFWnXBq-FknpydNWZqQ@mail.gmail.com> <CAALwa8kUTdN1FV8e5d0oOs5O%2BEKZ_ueKjk5UA16%2BH3%2BEt5GrqQ@mail.gmail.com> <20180527154219.GR88128@kib.kiev.ua> <CAJuc1zMHhQjF=jCNLeyNzRYtEDAAYMT%2BX1jX9MV4MyRVU0PsHQ@mail.gmail.com> <20180528114427.GA32825@elch.exwg.net> <alpine.BSF.2.21.999.1805281509400.89219@mail.fig.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 May 2018 15:24+0200, Trond Endrestøl wrote: > I can see one reason for not making /etc/rc.subr accessible inside > each chroot, and thus a copy of the ldconfig startup script, and that > is to prevent services from being started automatically within each > chroot. The latest commits to the synth repo forces synth to copy /etc/rc.subr and /etc/rc.d/ldconfig into each chroot. CommitDate: Fri May 25 08:16:19 2018 -0500 A new release might be imminent. Don't look at me, I'm just a synth luser. -- Trond. From owner-freebsd-stable@freebsd.org Mon May 28 15:38:09 2018 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 960CCEFE007 for <freebsd-stable@mailman.ysv.freebsd.org>; Mon, 28 May 2018 15:38:09 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [IPv6:2a01:4f8:140:50a2::3:1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C2027485C; Mon, 28 May 2018 15:38:09 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from localhost (localhost [127.0.0.1]) by smtp.burggraben.net (Postfix) with ESMTP id 8BC486002F3; Mon, 28 May 2018 17:38:07 +0200 (CEST) X-Spam-Scanned: by amavisd-new at exwg.net Received: from smtp.burggraben.net ([127.0.0.1]) by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ufZpnBJIeO1o; Mon, 28 May 2018 17:37:55 +0200 (CEST) Received: from elch.exwg.net (elch.exwg.net [IPv6:2001:470:7120:1:127b:44ff:fe4f:148d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "elch.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK)) by smtp.burggraben.net (Postfix) with ESMTPS; Mon, 28 May 2018 17:37:55 +0200 (CEST) Received: by elch.exwg.net (Postfix, from userid 1000) id E75C62730D; Mon, 28 May 2018 17:37:54 +0200 (CEST) Date: Mon, 28 May 2018 17:37:54 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: freebsd-stable@freebsd.org Cc: ericbsd@freebsd.org Subject: Re: ldconfig(8) oddity on 11.2-BETA3? Message-ID: <20180528153754.GB32825@elch.exwg.net> Mail-Followup-To: freebsd-stable@freebsd.org, ericbsd@freebsd.org References: <CAJuc1zPurH94998BhcHGZOqAu04VV3pNFWnXBq-FknpydNWZqQ@mail.gmail.com> <CAALwa8kUTdN1FV8e5d0oOs5O+EKZ_ueKjk5UA16+H3+Et5GrqQ@mail.gmail.com> <20180527154219.GR88128@kib.kiev.ua> <CAJuc1zMHhQjF=jCNLeyNzRYtEDAAYMT+X1jX9MV4MyRVU0PsHQ@mail.gmail.com> <20180528114427.GA32825@elch.exwg.net> <alpine.BSF.2.21.999.1805281509400.89219@mail.fig.ol.no> <alpine.BSF.2.21.999.1805281708100.89219@mail.fig.ol.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <alpine.BSF.2.21.999.1805281708100.89219@mail.fig.ol.no> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 28 May 2018 15:38:09 -0000 ## Trond Endrestøl (Trond.Endrestol@fagskolen.gjovik.no): > The latest commits to the synth repo forces synth to copy /etc/rc.subr > and /etc/rc.d/ldconfig into each chroot. Aha! Yes, looking at https://github.com/jrmarino/synth/commit/465ab8d2133a9d1e15cbf46337a1a809f828495d I think the issue is solved: synth in it's current incarnation from our ports tree does not handle ports with USE_LDCONFIG in a way the ports tree expects it. Omitting rc.subr and rc.d from the ports build chroots may have it's merits - but I wonder what else may break when using an incomplete base system? Would using a pristine system with an empty rc.conf improve matters? Cc'ing Eric as the synth maintainer (as in port maintainer) - perhaps it's possible to backport that commit until the next release? (I'm not only "not a synth user", but also "rather inept with Ada"). Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.999.1805281708100.89219>