Date: Sun, 4 Sep 2022 16:31:20 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Doug Denault <doug@safeport.com> Cc: Dan Mahoney <freebsd@gushi.org>, "freebsd-questions@freebsd.org" <freebsd-questions@FreeBSD.ORG> Subject: Re: FreeBSD 12.2 can not be upgraded Message-ID: <D6FA74F6-B8C9-4CD8-B58D-27D1B01025C0@gromit.dlib.vt.edu> In-Reply-To: <alpine.BSF.2.00.2209041352190.67914@bucksport.safeport.com> References: <alpine.BSF.2.00.2209041200310.67914@bucksport.safeport.com> <AA1D2084-FB1A-418E-A26A-D468312A6DC5@gushi.org> <alpine.BSF.2.00.2209041352190.67914@bucksport.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <doug@safeport.com> wrote: > On Sun, 4 Sep 2022, Dan Mahoney wrote: >=20 >>=20 >> 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? >=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 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On = Sep 4, 2022, at 2:06 PM, Doug Denault <<a = href=3D"mailto:doug@safeport.com" class=3D"">doug@safeport.com</a>> = wrote:<div class=3D""><br class=3D""><div><br class=3D""><blockquote = type=3D"cite" class=3D""><span style=3D"font-family: Menlo-Regular;" = class=3D"">On Sun, 4 Sep 2022, Dan Mahoney wrote:</span><br = class=3D""><div class=3D""><br style=3D"caret-color: rgb(0, 0, 0); = font-family: Menlo-Regular; font-size: 14px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;" class=3D""><blockquote type=3D"cite" = style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: = normal; font-variant-caps: normal; font-weight: 400; letter-spacing: = normal; orphans: auto; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: auto; word-spacing: = 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; = text-decoration: none;" class=3D""><br = class=3D""> On Sep 4, 2022, at 10:05, Doug = Denault <<a href=3D"mailto:doug@safeport.com" = class=3D"">doug@safeport.com</a>> wrote:<br class=3D"">There was a = long thread on this. My observations and questions are more about how = to<br class=3D"">update production systems. My long standing update path = is to update my FreeBSD<br class=3D"">workstations. If that goes okay we = some servers on out LAN that we update next.<br class=3D"">I ran = `freebsd-update -r 12.3-RELEASE upgrade` which converted my laptop = essentially into<br class=3D"">a paperweight by the introduction a bad = copy of ld-elf.so.1. The system would boot, but<br class=3D"">most = useful commands (think cp) exited with an error. This is all documented = via google<br class=3D"">with no successful work arounds that I could = fine. What you can not do is `freebsd-update<br class=3D"">rollback`. I = though I could maybe fix this by going to single user and overwriting<br = class=3D"">ld-elf.so.1. This can not be done as all commands depend on = this file.<br class=3D"">I created image files from:<br = class=3D""> FreeBSD-12.3-RELEASE-amd64-dvd1.iso (4+GB)<br = class=3D""> FreeBSD-12.3-RELEASE-amd64-memstick.img ~1GB<br = class=3D"">Neither of these images are self contained. Both install 12.3 = correctly but by downloading<br class=3D"">the OS from a mirror site of = your choosing. Is there a path thought the dvd1 install that<br = class=3D"">does something with the extra 3GB of data? Does the dvd1.iso = image have to be burned to a<br class=3D"">DVD?<br = class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); = font-family: Menlo-Regular; font-size: 14px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, = 0); font-family: Menlo-Regular; font-size: 14px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none; float: none; display: inline !important;" = class=3D"">Still left with what's in the extra 3GB.</span><br = style=3D"caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; = font-size: 14px; font-style: normal; font-variant-caps: normal; = font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none;" class=3D""></div></blockquote><div><br class=3D""></div><div><br = class=3D""></div><div>This is from the FreeBSD Handbook chapter on = installing FreeBSD (<a = href=3D"https://docs.freebsd.org/en/books/handbook/bsdinstall/#bsdinstall-= installation-media" = class=3D"">https://docs.freebsd.org/en/books/handbook/bsdinstall/#bsdinsta= ll-installation-media</a>):</div><div><br = class=3D""></div></div><blockquote style=3D"margin: 0 0 0 40px; border: = none; padding: 0px;" class=3D""><div><div><div class=3D"">-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.</div></div></div></blockquote><div><div><br = class=3D""></div><div><br class=3D""></div><blockquote type=3D"cite" = class=3D""><div class=3D""><span style=3D"caret-color: rgb(0, 0, 0); = font-family: Menlo-Regular; font-size: 14px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none; float: none; display: inline !important;" = class=3D"">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.</span></div></blockquote><br class=3D""></div><div><br = class=3D""></div><div>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.)</div><div><br = class=3D""></div><div>Cheers,</div><div><br = class=3D""></div><div>Paul.</div><br class=3D""></div></body></html>= --Apple-Mail=_785EE2E5-32C3-41A4-8D13-B7E9C7E056C4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D6FA74F6-B8C9-4CD8-B58D-27D1B01025C0>