From nobody Sun Sep 4 20:31:20 2022 X-Original-To: freebsd-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 4MLNbT4Cx9z4bW1v for ; Sun, 4 Sep 2022 20:31:33 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MLNbS3ZRwz3KLq for ; Sun, 4 Sep 2022 20:31:32 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from smtpclient.apple (unknown [IPv6:2001:470:e15b:23::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 0AD76418AC; Sun, 4 Sep 2022 16:31:21 -0400 (EDT) From: Paul Mather Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_785EE2E5-32C3-41A4-8D13-B7E9C7E056C4" 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 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: FreeBSD 12.2 can not be upgraded Date: Sun, 4 Sep 2022 16:31:20 -0400 In-Reply-To: Cc: Dan Mahoney , "freebsd-questions@freebsd.org" To: Doug Denault References: X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4MLNbS3ZRwz3KLq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=vt.edu (policy=none); spf=none (mx1.freebsd.org: domain of paul@gromit.dlib.vt.edu has no SPF policy when checking 128.173.126.123) smtp.mailfrom=paul@gromit.dlib.vt.edu X-Spamd-Result: default: False [-2.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[vt.edu : No valid SPF, No valid DKIM,none]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@FreeBSD.ORG]; ASN(0.00)[asn:1312, ipnet:128.173.0.0/16, country:US]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; FREEFALL_USER(0.00)[paul]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_785EE2E5-32C3-41A4-8D13-B7E9C7E056C4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Sep 4, 2022, at 2:06 PM, Doug Denault wrote: > On Sun, 4 Sep 2022, Dan Mahoney wrote: >=20 >>=20 >> On Sep 4, 2022, at 10:05, Doug Denault = wrote: >> There was a long thread on this. My observations and questions are = more about how to >> update production systems. My long standing update path is to update = my FreeBSD >> workstations. If that goes okay we some servers on out LAN that we = update next. >> I ran `freebsd-update -r 12.3-RELEASE upgrade` which converted my = laptop essentially into >> a paperweight by the introduction a bad copy of ld-elf.so.1. The = system would boot, but >> most useful commands (think cp) exited with an error. This is all = documented via google >> with no successful work arounds that I could fine. What you can not = do is `freebsd-update >> rollback`. I though I could maybe fix this by going to single user = and overwriting >> ld-elf.so.1. This can not be done as all commands depend on this = file. >> I created image files from: >> FreeBSD-12.3-RELEASE-amd64-dvd1.iso (4+GB) >> FreeBSD-12.3-RELEASE-amd64-memstick.img ~1GB >> Neither of these images are self contained. Both install 12.3 = correctly but by downloading >> the OS from a mirror site of your choosing. Is there a path thought = the dvd1 install that >> does something with the extra 3GB of data? Does the dvd1.iso image = have to be burned to a >> DVD? >=20 > Still left with what's in the extra 3GB. This is from the FreeBSD Handbook chapter on installing FreeBSD = (https://docs.freebsd.org/en/books/handbook/bsdinstall/#bsdinstall-install= ation-media): -dvd1.iso: This file contains all of the files needed to install = FreeBSD, its source, and the Ports Collection. It also contains a set of = popular binary packages for installing a window manager and some = applications so that a complete system can be installed from media = without requiring a connection to the Internet. This file should be = burned to a DVD using a DVD burning application. > With the ld-elf.so.1 /rescue/sh is useless because it depends on = /libexec. You can easily recover your data from the hosed system by = running an install image and chosing the third option, something like = 'live system'. Then all you have to do is mount the hard drive. In my = case I did not even have to remember the route and ifconfig commands = (obviously an issue for me :) dhclient worked fine. I don't understand your comment about /rescue/sh in the first sentence = in the quoted paragraph above. The binaries in /rescue are statically = linked, so I don't see how they depend on /libexec. In fact, ldd will = even complain if you run it against /rescue/sh because it is not a = dynamically-linked executable. Furthermore, file(1) will include = "statically linked" in its output when run against /rescue/sh. = (Disclaimer: I don't have any 12.x systems any more to double-check, but = it is true for FreeBSD 13.1 and historically has been the case for as = long as I know. See man rescue(8) for details.) Cheers, Paul. --Apple-Mail=_785EE2E5-32C3-41A4-8D13-B7E9C7E056C4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On = Sep 4, 2022, at 2:06 PM, Doug Denault <doug@safeport.com> = wrote:


On Sun, 4 Sep 2022, Dan Mahoney wrote:


     On Sep 4, 2022, at 10:05, Doug = Denault <doug@safeport.com> wrote:
There was a = long thread on this. My observations and questions are more about how = to
update production systems. My long standing update path = is to update my FreeBSD
workstations. If that goes okay we = some servers on out LAN that we update next.
I ran = `freebsd-update -r 12.3-RELEASE upgrade` which converted my laptop = essentially into
a paperweight by the introduction a bad = copy of ld-elf.so.1. The system would boot, but
most = useful commands (think cp) exited with an error. This is all documented = via google
with no successful work arounds that I could = fine. What you can not do is `freebsd-update
rollback`. I = though I could maybe fix this by going to single user and overwriting
ld-elf.so.1. This can not be done as all commands depend on = this file.
I created image files from:
 FreeBSD-12.3-RELEASE-amd64-dvd1.iso (4+GB)
 FreeBSD-12.3-RELEASE-amd64-memstick.img ~1GB
Neither of these images are self contained. Both install 12.3 = correctly but by downloading
the OS from a mirror site of = your choosing. Is there a path thought the dvd1 install that
does something with the extra 3GB of data? Does the dvd1.iso = image have to be burned to a
DVD?

Still left with what's in the extra 3GB.


This is from the FreeBSD Handbook chapter on = installing FreeBSD (https://docs.freebsd.org/en/books/handbook/bsdinstall/#bsdinsta= ll-installation-media):

-dvd1.iso: = This file contains all of the files needed to install FreeBSD, its = source, and the Ports Collection. It also contains a set of popular = binary packages for installing a window manager and some applications = so that a complete system can be installed from media without = requiring a connection to the Internet. This file should be burned = to a DVD using a DVD burning = application.


With the ld-elf.so.1 /rescue/sh is useless because it depends = on /libexec. You can easily recover your data from the hosed system by = running an install image and chosing the third option, something like = 'live system'. Then all you have to do is mount the hard drive. In my = case I did not even have to remember the route and ifconfig commands = (obviously an issue for me :) dhclient worked = fine.


I don't understand your comment about /rescue/sh = in the first sentence in the quoted paragraph above.  The binaries = in /rescue are statically linked, so I don't see how they depend on = /libexec.  In fact, ldd will even complain if you run it against = /rescue/sh because it is not a dynamically-linked executable. =  Furthermore, file(1) will include "statically linked" in its = output when run against /rescue/sh.  (Disclaimer: I don't have any = 12.x systems any more to double-check, but it is true for FreeBSD 13.1 = and historically has been the case for as long as I know.  See man = rescue(8) for details.)

Cheers,

Paul.

= --Apple-Mail=_785EE2E5-32C3-41A4-8D13-B7E9C7E056C4--