Running update.sh without previously running check.sh will update the system but not the change log in the web GUI. When running on the latest version, this script will simply generate some output but not change anything. This script checks for new updates and installs the latest one, if updates are available. When updates are available, choosing to install then from the GUI seems to run /usr/local/opnsense/scripts/firmware/update.sh.It always reports success, whether or not the check was successful, and whether or not new versions are available. The script checks for new versions (and updates the change log in the Web GUI) but does not install them. Checking for new versions seems to run /usr/local/opnsense/scripts/firmware/check.sh.However, either action (potentially, not necessarily) reboots the system. These terms seem to be used much like in apt on Linux: update checks what new versions are available, upgrade installs them. Of these commands, update and upgrade seem to run a firmware update/upgrade, respectively (according to their description in the configd template).All of them seem to run a wrapper script which ultimately runs another script in /usr/local/opnsense/scripts/firmware/$COMMAND.sh. actions_nf has a few actions which look related to firmware upgrades.The template for firmware updates is actions_nf. Actions which can be triggered from the GUI are stored in configd templates, which reside in /usr/local/opnsense/service/conf/actions.d/. When invoked without command line option, it just reports Nothing to do, but it is used by several of the scripts mentioned below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |