From nobody Wed Aug 09 10:45:26 2023 X-Original-To: freebsd-current@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 4RLRXp5VjWz4pmX3 for ; Wed, 9 Aug 2023 10:45:30 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RLRXp4nPCz3Pj5 for ; Wed, 9 Aug 2023 10:45:30 +0000 (UTC) (envelope-from guru@unixarea.de) Authentication-Results: mx1.freebsd.org; none Received: from [132.174.172.2] (helo=pureos) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qTggy-0000TJ-UA; Wed, 09 Aug 2023 12:45:28 +0200 Date: Wed, 9 Aug 2023 12:45:26 +0200 From: Matthias Apitz To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Kevin Oberman , freebsd-current@freebsd.org Subject: Re: Has the update procedure changed? Message-ID: Reply-To: Matthias Apitz Mail-Followup-To: Miroslav Lachman <000.fbsd@quip.cz>, Kevin Oberman , freebsd-current@freebsd.org References: <7A0E604D-EF40-4F10-B597-F1F076507192@gmail.com> <3f8ab464-c9c9-b637-5cc6-c14f25f055b0@quip.cz> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3f8ab464-c9c9-b637-5cc6-c14f25f055b0@quip.cz> X-Operating-System: FreeBSD 13.0-CURRENT r368166 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 132.174.172.2 X-Rspamd-Queue-Id: 4RLRXp4nPCz3Pj5 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE] El día miércoles, agosto 09, 2023 a las 12:40:31 +0200, Miroslav Lachman escribió: > On 09/08/2023 08:22, Kevin Oberman wrote: > > > I don't see how you get this from the man page. > > "Compares only files known to be > >                  essential to the success of {build|install}world, i.e., > >                  /etc/group and /etc/master.passwd. > > > > If it is potentially updating files that MIGHT be essential to a > > successful buildworld, running it after buildkernel seems quite wrong. > > At least I read {build|install}world as buildworld or installworld. > > Correct me if I am wrong but AFAIK etcupdate -p (or mergemaster -p) updates > entries in [master.]passwd and group which are only needed to install new > files with the right owner and group set, not to build these files. > (installkernel installs everything ass root:wheel) > > Also Makefile contains this steps where mergemaster -p should be run after > installkernel and reboot: > > 2. `make buildworld' > 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > [steps 3. & 4. can be combined by using the "kernel" target] > 5. `reboot' (in single user mode: boot -s from the loader prompt). > 6. `mergemaster -p' > 7. `make installworld' > > > And man page for etcpupdate -p has this: > > -p Enable “pre-world” mode. Only merge changes to files > that are necessary to successfully run ‘make > installworld’ or ‘make installkernel Yes, exactly. Running mergemaster -p or (etcupdate -p) before 'make buildworld' does not make any sense. matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub