From nobody Fri Sep 1 01:42:27 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 4RcLPh0cFJz4rspv for ; Fri, 1 Sep 2023 01:42:32 +0000 (UTC) (envelope-from brian@sonicboom.org) Received: from sheehan.sonicboom.org (2603-8001-7e00-f435-0000-0000-0000-1000.res6.spectrum.com [IPv6:2603:8001:7e00:f435::1000]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RcLPg1slpz4F5C for ; Fri, 1 Sep 2023 01:42:31 +0000 (UTC) (envelope-from brian@sonicboom.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2603:8001:7e00:f435::1000 is neither permitted nor denied by domain of brian@sonicboom.org) smtp.mailfrom=brian@sonicboom.org; dmarc=none Received: from [10.10.1.112] (rrcs-69-75-45-51.west.biz.rr.com [69.75.45.51]) by sheehan.sonicboom.org (Postfix) with ESMTPSA id 2D7583A00582 for ; Thu, 31 Aug 2023 18:42:28 -0700 (PDT) Message-ID: Date: Thu, 31 Aug 2023 18:42:27 -0700 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 From: brian whalen Subject: Re: user problems when upgrading to v15 To: freebsd-current@freebsd.org References: <5c5c3ea5-5b14-d969-f55f-b894e4983359@sonicboom.org> <46ee9e3b-adeb-4cd1-5fcc-43547c5c7231@gmail.com> <222e96ba-70b6-e976-8e32-d3726dde18b1@sonicboom.org> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; NEURAL_HAM_LONG(-0.99)[-0.989]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:20001, ipnet:2603:8000::/28, country:US]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[sonicboom.org]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[brian]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; R_SPF_SOFTFAIL(0.00)[~all]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4RcLPg1slpz4F5C Repeating the entire process: I created a 13.2 vm with 6 cores and 8GB of ram. Ran freebsd-update fetch and install. Ran pkg install git bash ccache open-vm-tools-nox11 Used git clone to get current and ports source files. Edited /etc/make.conf to use ccache Ran make -j6 buildworld && make -j6 kernel I then rebooted in single user mode and did the next steps saving output to a file with > filename. etcupdate -p was pretty uneventful. It did  show the below and did not prompt to edit. root@f15:~ # less etcupdatep   C /etc/group   C /etc/master.passwd make installworld seemed mostly error free though I did see a nonzero status for a man page failed inn the man4 directory. etcupdate -B only showed the below. This was my first build after install. root@f15:~ # less etcupdateB Conflicts remain from previous update, aborting. 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. If this is is expected behavior for current then no big deal. I just wasn't sure. Brian On 8/30/2023 7:35 PM, Graham Perrin wrote: > On 31/08/2023 03:31, brian whalen wrote: > >> Understood. I guess I was expecting the update process of etcupdate >> -p && make installworld && etcupdate -B to not whack existing users >> or delete an existing root user's password. I accepted the remote and >> then recreated users and reset passwords and am retrying this. >> >> BW >> > Thanks. > > For clarity: did the routine /not/ prompt you to edit the file (in > which, you would have seen conflict markers etc.)? > >> On 8/30/2023 7:21 PM, Graham Perrin wrote: >>> On 31/08/2023 03:00, brian whalen wrote: >>>> … I ran etcupdate resolve accepting the remote option and saw 2 >>>> issues. >>>> >>>> The root user's password was deleted. >>>> >>>> The non root user no longer existed. >>> Logically, remote does not include things such as your root user's >>> password. >