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.


Reply via email to