Date: Tue, 28 Dec 2021 04:09:53 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260628] FreeBSD 12.3-Release got stuck during the boot process after the update (maybe nsswitch issue?) Message-ID: <bug-260628-227-knonz3SaHZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260628-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260628-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260628 --- Comment #3 from Graham Perrin <grahamperrin@gmail.com> --- (In reply to Yoshisato Yanagisawa from comment #2) For myself, I often (quietly) run:=20 freebsd-version -kru I find it particularly useful to run at various stages of an _upgrade_ rout= ine. To help me not lose sight of the point at which a restart is appropriate, a= nd so on.=20 freebsd-version(1) <https://www.freebsd.org/cgi/man.cgi?query=3Dfreebsd-version&sektion=3D1&ma= npath=3DFreeBSD> It's not unusual to find the patch level of the installed userland different from the patch level of the running kernel. Some patches apply to userland = but not the kernel. Non-official <https://bokut.in/freebsd-patch-level-table/#releng/12.2>; might help to understand things such as this. > =E2=80=A6 I assume there is no ZFS update between 12.2R and 12.3R. =E2=80= =A6 <https://cgit.freebsd.org/src/log/?h=3Dreleng%2F12.3&qt=3Dgrep&q=3Dzfs>; some ZFS-related changes.=20 As orientation: less specifically, we currently have the amber 'release/12.= 3.0' at the head of <https://cgit.freebsd.org/src/log/?h=3Dreleng%2F12.3>. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260628-227-knonz3SaHZ>