Manual Page Search Parameters
MIDNIGHTBSD-UPDATE.CONF(5) MidnightBSD File Formats Manual MIDNIGHTBSD-UPDATE.CONF(5)

midnightbsd-update.conf — configuration file for midnightbsd-update(8)

The midnightbsd-update.conf file controls the behaviour of the midnightbsd-update(8) utility. The file contains lines consisting of a case-sensitive option name and zero or more parameters. Empty lines and any part of a line following a ‘#’ character are ignored. Unless stated otherwise, specifying an option multiple times is an error.

The possible options and their meanings are as follows:

The single parameter following this keyword is the SHA256 hash of the RSA key which will be trusted to sign updates.
The single parameter following this keyword is the name of the server or server pool from which updates will be downloaded.
The parameters following this keyword are the components or sub-components of which will be updated. The components are “src” (source code), “world” (non-kernel binaries), and “kernel”; the sub-components are the individual distribution sets generated as part of the release process (e.g., “src/base”, “src/sys”, “world/base”, “world/catpages”, “kernel/smp”). Note that prior to the “kernel” component was distributed as part of “world/base”.

This option can be specified multiple times, and the parameters accumulate.

The parameters following this keyword are regular expressions; updates to paths which start with a string matching one of these regular expressions will be ignored.

This option can be specified multiple times, and the parameters accumulate.

The parameters following this keyword are regular expressions; paths which start with a string matching one of these regular expressions will be ignored by "midnightbsd-update IDS".

This option can be specified multiple times, and the parameters accumulate.

The parameters following this keyword are regular expressions; updates to paths which start with a string matching one of these regular expressions will be ignored if the files have been modified locally (unless they are merged -- see MergeChanges below).

This option can be specified multiple times, and the parameters accumulate.

The parameters following this keyword are regular expressions; updates to paths which start with a string matching one of these regular expressions will be merged with local modifications.

This option can be specified multiple times, and the parameters accumulate.

The single parameter following this keyword is the directory in which temporary files and downloaded updates will be stored.
The single parameter following this keyword is the address to which cron output will be mailed.
The single parameter following this keyword must be “yes” or “no” and specifies whether midnightbsd-update is allowed to create new files, directories, and symlinks if these are part of updates downloaded. Note that midnightbsd-update will not re-add files which have been deleted from a installation unless those files were previously added as part of an update.
The single parameter following this keyword must be “yes” or “no” and specifies whether midnightbsd-update is allowed to delete files, directories, and symlinks as part of updates downloaded.
The single parameter following this keyword must be “yes” or “no” and specifies whether midnightbsd-update should keep existing file ownership, permissions, and flags when installing updates if these have been modified locally.
The single parameter following this keyword must be “yes” or “no” and specifies whether midnightbsd-update should interpret the list of components of specified via the Components option strictly as a list of components installed which should be upgraded when the upgrade command is used ("yes"), or merely as a list of components which might be installed, of which midnightbsd-update should identify which in fact are present ("no").
The single parameter following this keyword must be “yes” or “no” and specifies whether midnightbsd-update will create a backup of the old kernel before installing a new kernel. This backup kernel can be used to recover a system where the newly installed kernel somehow did not work. Note that the backup kernel is not reverted to its original state by the midnightbsd-update rollback command.
This keyword sets the directory which is used to store a backup kernel, if the BackupKernel feature is enabled. If the directory already exist, and it was not created by midnightbsd-update, the directory is skipped. In the case of the primary directory name not being usable, a number starting with ‘1’ is appended to the directory name. Like with the primary directory name, the constructed directory name is only used if the path name does not exist, or if the directory was previously created by midnightbsd-update. If the constructed directory still exist the appended number is incremented with 1 and the directory search process restarted. Should the number increment go above 9, midnightbsd-update will abort.
The single parameter following this keyword must be “yes” or “no” and specifies whether midnightbsd-update will also backup kernel symbol files, if they exist. The kernel symbol files takes up a lot of disk space and are not needed for recovery purposes. If the symbol files are needed, after recovering a system using the backup kernel, the midnightbsd-update rollback command will recreate the symbol files along with the old kernel.

/etc/midnightbsd-update.conf
Default location of the midnightbsd-update configuration file.

sha256(1), midnightbsd-update(8)

Colin Percival <cperciva@FreeBSD.org>

August 19, 2009 MidnightBSD