Date: Sat, 2 Sep 2023 16:11:04 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: brian whalen <brian@sonicboom.org> Cc: freebsd-current@freebsd.org Subject: Re: user problems when upgrading to v15 Message-ID: <7CDB341A-F9E1-4816-8443-E4C349A86C84@FreeBSD.org> In-Reply-To: <fa5fdd87-9b32-6036-98f7-40a56ee65d33@sonicboom.org> References: <5c5c3ea5-5b14-d969-f55f-b894e4983359@sonicboom.org> <e96bef2d-5b16-f97d-4da2-6e78a3e8f0d7@sonicboom.org> <46ee9e3b-adeb-4cd1-5fcc-43547c5c7231@gmail.com> <222e96ba-70b6-e976-8e32-d3726dde18b1@sonicboom.org> <f2f3942e-7e66-1c5b-5702-ec83f0c71cb9@gmail.com> <fa5fdd87-9b32-6036-98f7-40a56ee65d33@sonicboom.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 1 Sep 2023, at 03:42, brian whalen <brian@sonicboom.org> wrote: >=20 > Repeating the entire process: >=20 > I created a 13.2 vm with 6 cores and 8GB of ram. >=20 > Ran freebsd-update fetch and install. >=20 > Ran pkg install git bash ccache open-vm-tools-nox11 >=20 > Used git clone to get current and ports source files. >=20 > Edited /etc/make.conf to use ccache >=20 > Ran make -j6 buildworld && make -j6 kernel >=20 > I then rebooted in single user mode and did the next steps saving = output to a file with > filename. >=20 > etcupdate -p was pretty uneventful. It did show the below and did not = prompt to edit. >=20 > root@f15:~ # less etcupdatep > C /etc/group > C /etc/master.passwd This is a problem: the "C" characters mean there were conflicts, and = it's indeed very unfortunate that etcupdate does not immediately force = you to resolve them. Because now you basically have mangled group and = master.passwd files, with conflict markers in them! Immediately after this, you should run "etcupdate resolve", and fix any = conflicts that it has found. Note that recently there was a lot of churn due to the removal of = $FreeBSD$ keywords, and this almost always creates conflicts in the = group and passwd files. For lots of other files in /etc, the conflicts = are resolved automatically, but unfortunately not for the files that are = essential to log in! > make installworld seemed mostly error free though I did see a nonzero = status for a man page failed inn the man4 directory. >=20 > etcupdate -B only showed the below. This was my first build after = install. >=20 > root@f15:~ # less etcupdateB > Conflicts remain from previous update, aborting. Yes, that is indeed the problem. You must first resolve conflicts from = any previous etcupdate run, before doing anything else. As to why it = does not immediately forces you to do so, and delegates this to a = separate step, which can easily be forgotten, I have no idea. >=20 > If I type exit in single user mode to go multi user mode, the local = user still works. After a reboot the local user still works. This local = user can also sudo as expected. This wasn't the case for the previous = build when I first reported this. However, if I run etcupdate resolve it = is still presenting /etc/group and /etc/master/passwd as problems. >=20 > If this is is expected behavior for current then no big deal. I just = wasn't sure. The conflicts themselves are expected, alas. But you _must_ resolve = them, otherwise you can end up with a mostly-bricked system. -Dimitry --Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZPNCeAAKCRCwXqMKLiCW oxKVAJ9AZue/5lyC9boIuNQ/E0CAOL1K/gCg4wfzwmYahtROcaL7n6hdZ3szBiQ= =bRNx -----END PGP SIGNATURE----- --Apple-Mail=_D8920F38-DD76-4DA7-B6F1-03324CC36EE2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7CDB341A-F9E1-4816-8443-E4C349A86C84>