Date: Tue, 14 Oct 2025 13:26:06 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: etcupdate usage Message-ID: <86v7kh67xt.fsf@ltc.des.dev> In-Reply-To: <aO31zACedXpxfqsj@rail.eu.org> (Erwan David's message of "Tue, 14 Oct 2025 09:03:40 %2B0200") References: <aO31zACedXpxfqsj@rail.eu.org>
index | next in thread | previous in thread | raw e-mail
Erwan David <erwan@rail.eu.org> writes: > I do not understand how to use etcupdate. [...] Is it because src is > not on the machine ? If you didn't upgrade from source, you don't need etcupdate. > I soon will upgrade another machine (with /usr/src this one), and I'd > prefer to be sure to be able to use etcupdate on it > (especially if I need to to a extract or build before upgrade) If and only if upgrading your machine from source, run `etcupdate -B` after `make installworld`. This will update every file that isn't conflicted and tell you of any that are, in which case you will have to run `etcupdate resolve` to resolve the conflicts. Once in a great while (the last time it happened was in 2020), `make installworld` will fail due to a missing user or group. In that case, you need to run `etcupdate -p` (and possibly `etcupdate resolve -p`) to update the user and group databases before retrying `make installworld`. When doing so, you will still have to run `etcupdate -B` afterwards to update everything else. DES -- Dag-Erling Smørgrav - des@FreeBSD.orghelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86v7kh67xt.fsf>