From nobody Fri Jan 28 13:26:50 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6D7401981889 for ; Fri, 28 Jan 2022 13:26:54 +0000 (UTC) (envelope-from SRS0=l6OR=SM=perdition.city=julien@bebif.be) Received: from orval.bbpf.belspo.be (orval.bbpf.belspo.be [193.191.208.90]) by mx1.freebsd.org (Postfix) with ESMTP id 4JldXY43kWz4h1x for ; Fri, 28 Jan 2022 13:26:53 +0000 (UTC) (envelope-from SRS0=l6OR=SM=perdition.city=julien@bebif.be) Received: from x1 (unknown [10.209.1.149]) by orval.bbpf.belspo.be (Postfix) with ESMTPSA id 929FD1D4FC16; Fri, 28 Jan 2022 14:26:52 +0100 (CET) Date: Fri, 28 Jan 2022 14:26:50 +0100 From: Julien Cigar To: Christoph Brinkhaus Cc: questions@freebsd.org Subject: Re: freebsd-update jail Message-ID: <20220128132650.7rgksy5tlteykme7@x1> Mail-Followup-To: Christoph Brinkhaus , questions@freebsd.org References: <20220128103032.mts7xrgy3k5ghbgo@x1> <20220128110754.znqx2z2ciw4hi4xo@x1> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="svsq4h6ajhwr3ocv" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4JldXY43kWz4h1x X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of "SRS0=l6OR=SM=perdition.city=julien@bebif.be" designates 193.191.208.90 as permitted sender) smtp.mailfrom="SRS0=l6OR=SM=perdition.city=julien@bebif.be" X-Spamd-Result: default: False [-4.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FORGED_SENDER(0.30)[julien@perdition.city,SRS0=l6OR=SM=perdition.city=julien@bebif.be]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_NA(0.00)[perdition.city]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.997]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[questions]; FREEMAIL_TO(0.00)[t-online.de]; RCVD_NO_TLS_LAST(0.10)[]; SIGNED_PGP(-2.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:2611, ipnet:193.191.192.0/19, country:BE]; FROM_NEQ_ENVFROM(0.00)[julien@perdition.city,SRS0=l6OR=SM=perdition.city=julien@bebif.be] X-ThisMailContainsUnwantedMimeParts: N --svsq4h6ajhwr3ocv Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 28, 2022 at 02:16:38PM +0100, Christoph Brinkhaus wrote: > Am Fri, Jan 28, 2022 at 12:07:54PM +0100 schrieb Julien Cigar: >=20 > Hello Julien! >=20 > > I was also wondering why does (12.3) freebsd-update creates a new boot > > environment when updating a jail? > >=20 >=20 > I have no idea. I found PR 261446=20 >=20 > > On Fri, Jan 28, 2022 at 11:30:32AM +0100, Julien Cigar wrote: > > > Hello, > > >=20 > > > I was wondering what is the best way to upgrade a jail nowadays? > > >=20 > > > I usually use: > > >=20 > > > $> freebsd-update -b /jails/myjail -d /jails/myjail/var/db/freebsd-up= date/ -f /jails/myjail/etc/freebsd-update.conf -r new-RELEASE --currently-r= unning old-RELEASE upgrade > > >=20 > > > but I was wondering if, with the newly "-j" option, "-b" is still > > > necessary? (from what I can understand in the source code it is not) > > >=20 > > > so could I used something like: > > >=20 > > > $> freebsd-update -j myjail -r new-RELEASE -d /jails/myjail/var/db/fr= eebsd-update/ -f /jails/myjail/etc/freebsd-update.conf upgrade ? > > >=20 > > > (I usually use -f as the Components aren't the same in the jail as in > > > the HOST, for example kernel is not installed, nor src) >=20 > As far as I remember I have run the latest upgrade as > freebsd-update -b /jails/myjail -r new-RELEASE --currently-running old-RE= LEASE upgrade >=20 freebsd-update has been updated with a -j (operate on the given jail specified by jid or name) so --currently-running is no more required when using -j. I was wondering about -b, but after testing it seems that -b is no more required too, so the following works: $> sudo freebsd-update -j myjail -r new-RELEASE upgrade > I have not been aware of the -d and -f options. >=20 I was using a separate -f as Components differ, but it looks like freebsd-update detects is nowadays (so not required anymore) > > No trees were killed in the creation of this message. > > However, many electrons were terribly inconvenienced. >=20 > This is a nice signature :-). >=20 :-) > Kind regards, > Christoph >=20 >=20 --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --svsq4h6ajhwr3ocv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEnF27CBNtOraRNmgqCLYqJMpBHmkFAmHz7xcACgkQCLYqJMpB HmmrSw/+MEkiOIdjXCS5jM+03iKCLU/g5c+ISdrwig6Ebr6PTC/d+eHROS5tESxQ PUzwLduFpxkpMCRKKOnVNDyVStyL1yV+HfyBXq9CL1TeQrdJ4qYttfCXxpKK68O5 T2upZNInJjNmx/xfSPC2X1ci732mc7s5+4+e9MDb+85NRkHnPihBpwf9KfHZfWpm +x1TCzomRMiDKSxVc0HPbmiInwN8apUxAKqUFl0QP/qqC4nFW8r4FjxXP2R8wd52 2jJqTYFMugAkR+3EUR5+XXRqqxYZPyvxtV4czG/uD/7IKRRcRJ9nUL0SXxlPXd5G T8GUsp7/Oeg2MStvboQIUJgUEFb8s0C9VRj8nzAaIapgE61GxJGwqDC5Er/HWSuN FwOHe/LH2wf787314eRMj3OGnlkwzf35VG6G4sH21Qh1AYWDz+swT0k0htImQyGJ awyw5go1abDhYuClvPZMQKOTUaTObOrnsGTu4Fkto/rj+uwhwj8sOHwpsbO3Gmio Cj/+fhN2OFJz2O64Wdom12RTRGkMeh40/G4Pe5yZUBd6xFYQCS+MYtOHe87jlkwh hgFIRxNtqp9MCUaukrnZEh8+8ZVp4ilkNvYDwNKs3xcRQ6zfXLWhULxS9VAheEI/ HNk++akDV7469108RC4cHirWtyVDho7edhCtYK/EVwKqw/4qNXU= =fSvx -----END PGP SIGNATURE----- --svsq4h6ajhwr3ocv--