Date: Sat, 25 Aug 2018 11:38:40 +0200 From: "Kristof Provost" <kristof@sigsegv.be> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: "FreeBSD CURRENT" <freebsd-current@freebsd.org>, "Brad Davis" <brd@FreeBSD.org> Subject: Re: [CURRENT, ezjail] rc, rc.subr and other rc. scripts gone: ezjail fails on 12-ALPHA Message-ID: <3C0C5CB5-1A0F-49DD-A3FE-ADA5B00BAD48@sigsegv.be> In-Reply-To: <20180825090704.69e17a6e@thor.intern.walstatt.dynvpn.de> References: <20180825090704.69e17a6e@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 Aug 2018, at 9:06, O. Hartmann wrote:
> I'm using ezjail-admin from ports (most recent tree, up to date as of
> today, at Revision:
> 478001, FreeBSD is FreeBSD 12.0-ALPHA3 #455 r338309: Sat Aug 25
> 07:10:45 CEST 2018 amd64,
> the jails sources are at revision 338309).
>
> Updates of the jail's base is taken from /usr/src or another path (in
> case of another
> path, ezjail-admin update -i requires the setting of evn
> MAKEOBJDIRPREFIX= some/place).
>
> Updating jails and creating new jails has worked for a while, but
> recently, newly created
> jails fail to start because the initial start routine bringing up the
> jail dumps an error
> about /bin/sh /etc/rc missing!
>
> Investigating a complete fresh ezajil setup (on ZFS) reveals, that
> neither in fulljail,
> newjail or basejail any of the initial rc-srcipts rc or rc.subr is
> present any more! I
> stopped looking for other missing scripts since rc and rc.subr are
> crucial and essential
> to the system, so I guess there has been introduced a sort of bug
> recently in the way
> FreeBSD 12 is going to handle/keep/store rc scripts in the source tree
> or their
> installation and ezjai didn't catch up so far.
>
> I already filed a PR (see Bug 230822), but I'm unsure whether this is
> a "real" bug or I
> did just miss some important changes and I didn't catch up.
>
Yep, it’s a real problem. I ran into it myself a few weeks ago.
Many of the scripts and files in sys/etc have been moved, for pkg base.
This, combined with ezjail doing the install wrong breaks your jails.
Brad posted a patch to the ezjail mailing list. I can’t immediately
find an archive linke, but this should fix it:
--- ezjail-admin 2018-08-12 09:41:46.750946000 +0200
+++ /usr/local/bin/ezjail-admin 2018-08-12 09:42:42.863180000 +0200
@@ -1053,7 +1053,7 @@
# make and setup our world, then split basejail and newjail
cd "${ezjail_sourcetree}" && env DESTDIR="${ezjail_jailfull}" make
${ezjail_installaction} || exerr "Error: The command 'make
${ezjail_installaction}' failed.\n Refer to the error report(s) above."
- cd "${ezjail_sourcetree}/etc" && env DESTDIR="${ezjail_jailfull}"
make distribution || exerr "Error: The command 'make distribution'
failed.\n Refer to the error report(s) above."
+ cd "${ezjail_sourcetree}" && env DESTDIR="${ezjail_jailfull}" make
distribution || exerr "Error: The command 'make distribution' failed.\n
Refer to the error report(s) above."
ezjail_splitworld
fi # installaction="none"
Regards,
Kristof
From owner-freebsd-current@freebsd.org Sat Aug 25 10:13:16 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 51C9710853D5
for <freebsd-current@mailman.ysv.freebsd.org>;
Sat, 25 Aug 2018 10:13:16 +0000 (UTC)
(envelope-from herbert@gojira.at)
Received: from mail.bsd4all.net (mail.bsd4all.net [144.76.30.122])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.bsd4all.net",
Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id EAD69921B4
for <freebsd-current@freebsd.org>; Sat, 25 Aug 2018 10:13:15 +0000 (UTC)
(envelope-from herbert@gojira.at)
Date: Sat, 25 Aug 2018 12:13:08 +0200
From: "Herbert J. Skuhra" <herbert@gojira.at>
To: freebsd-current@freebsd.org
Subject: Re: pkg-base: how to avoid FreeBSD-$PACKAGE-{profile|development}
when using FreeBSD pkg-base
Message-ID: <20180825101308.xbnfbv7xfmuifl2b@mail.bsd4all.net>
References: <20180825113108.19b8cd86@thor.intern.walstatt.dynvpn.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180825113108.19b8cd86@thor.intern.walstatt.dynvpn.de>
User-Agent: NeoMutt/20180716
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Aug 2018 10:13:16 -0000
On Sat, Aug 25, 2018 at 11:30:41AM +0200, O. Hartmann wrote:
>
> For some experiments on PINE64 we build packages from FreeBSD's base system. The
> individual package seems to comprise always from several flavours, the
> "regular/production" one, profile/profiling one and development, for instance for package
> FreeBSD-libxo:
>
> FreeBSD-libxo: 12.0.s20180825090036 [FreeBSD-base]
> FreeBSD-libxo-development: 12.0.s20180825090036 [FreeBSD-base]
> FreeBSD-libxo-profile: 12.0.s20180825090036 [FreeBSD-base]
>
> When installing packages as recommended on the FreeBSD pkg-base Wiki
> (https://wiki.freebsd.org/PkgBase) via
>
> pkg install -g 'FreeBSD-*'
>
> it is implicit that I also get those unwanted "profiling" and "development" packages as
> well as the supposed to be the "production" ones. Fiddling around whith the pattern left
> me with some problems, as it seems to me to make the efforts to high to target all wanted
> packages or avoid development packages. I haven't found a proper way to exclude all the
> unwanted packages (development, prifile) by the global pattern.
Have you checked the content of the development packages? I guess you
have to install them! To disable profile-packages set WITHOUT_PROFILE in
/etc/src.conf.
--
Herbert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C0C5CB5-1A0F-49DD-A3FE-ADA5B00BAD48>