f-upgrade

[rainer_d]

Hi,

I'm trying this tool:

GitHub - fraenki/f-upgrade: Unattended FreeBSD operating system updates

Unattended FreeBSD operating system updates. Contribute to fraenki/f-upgrade development by creating an account on GitHub.

github.com

also available as a port since for a while:

FreshPorts -- sysutils/f-upgrade: Unattended FreeBSD operating system updates

f-upgrade automates the process of installing FreeBSD operating system updates. It targets server fleets, not desktop environments.

www.freshports.org

It doesn't merge /etc files (which is interactive).

Once the upgrade is complete, how can I merge /etc ?

 

[sko]

It doesn't merge /etc files (which is interactive).

Once the upgrade is complete, how can I merge /etc ?

from the github README.md:

Note that f-upgrade automatically disables the MergeChanges option in freebsd-update, because this would require user-interaction. It is important that this option remains disabled until the upgrade process is finished.

[...]

• Changes to /etc/passwd and /etc/group are not automatically applied (because MergeChanges is disabled)
• Changes to system configuration files are not automatically applied (because MergeChanges is disabled)

hence further up in the requirements:

• Some kind of automation (Puppet, Ansible, Chef) to fix/update configuration files

I.e. this tool is intended to be part of a whole toolchain (e.g. ansible, chef, puppet etc...) which will handle the merging/update of /etc

I guess you should first perform the upgrade manually on a test system where you can work out what config files need to be updated/merged, then either provide automation for that (scripts, playbooks/recipes/...) or prepare the new config files that then can be put in place by your configuration management/orchestration tool.

 

[cracauer@]

Merging /etc is for wussies

 

[rainer_d]

I'm mainly concerned about /etc/password and /etc/group - basically, when new users are added.

I thought there is a way to invoke the merge manually after the upgrade is completed.

The update itself seems to have worked well with the tool (14.1 -> 14.2).

With the support-periods for minor-releases shrinking, I have to do the upgrade more efficiently.