Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

freebsd-update(8) [freebsd man page]

FREEBSD-UPDATE(8)					    BSD System Manager's Manual 					 FREEBSD-UPDATE(8)

NAME
freebsd-update -- fetch and install binary updates to FreeBSD SYNOPSIS
freebsd-update [-b basedir] [-d workdir] [-f conffile] [-k KEY] [-r newrelease] [-s server] [-t address] command ... DESCRIPTION
The freebsd-update tool is used to fetch, install, and rollback binary updates to the FreeBSD base system. Note that updates are only avail- able if they are being built for the FreeBSD release and architecture being used; in particular, the FreeBSD Security Team only builds updates for releases shipped in binary form by the FreeBSD Release Engineering Team, e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD 6.3-STABLE or FreeBSD 9.0-CURRENT. OPTIONS
The following options are supported: -b basedir Operate on a system mounted at basedir. (default: /, or as given in the configuration file.) -d workdir Store working files in workdir. (default: /var/db/freebsd-update/, or as given in the configuration file.) -f conffile Read configuration options from conffile. (default: /etc/freebsd-update.conf) -k KEY Trust an RSA key with SHA256 of KEY. (default: read value from configuration file.) -r newrelease Specify the new release to which freebsd-update should upgrade (upgrade command only). -s server Fetch files from the specified server or server pool. (default: read value from configuration file.) -t address Mail output of cron command, if any, to address. (default: root, or as given in the configuration file.) COMMANDS
The command can be any one of the following: fetch Based on the currently installed world and the configuration options set, fetch all available binary updates. cron Sleep a random amount of time between 1 and 3600 seconds, then download updates as if the fetch command was used. If updates are downloaded, an email will be sent (to root or a different address if specified via the -t option or in the configuration file). As the name suggests, this command is designed for running from cron(8); the random delay serves to minimize the proba- bility that a large number of machines will simultaneously attempt to fetch updates. upgrade Fetch files necessary for upgrading to a new release. Before using this command, make sure that you read the announcement and release notes for the new release in case there are any special steps needed for upgrading. Note that this command may require up to 500 MB of space in workdir depending on which components of the FreeBSD base system are installed. install Install the most recently fetched updates or upgrade. rollback Uninstall the most recently installed updates. IDS Compare the system against a "known good" index of the installed release. TIPS
o If your clock is set to local time, adding the line 0 3 * * * root /usr/sbin/freebsd-update cron to /etc/crontab will check for updates every night. If your clock is set to UTC, please pick a random time other than 3AM, to avoid overly imposing an uneven load on the server(s) hosting the updates. o In spite of its name, freebsd-update IDS should not be relied upon as an "Intrusion Detection System", since if the system has been tam- pered with it cannot be trusted to operate correctly. If you intend to use this command for intrusion-detection purposes, make sure you boot from a secure disk (e.g., a CD). FILES
/etc/freebsd-update.conf Default location of the freebsd-update configuration file. /var/db/freebsd-update/ Default location where freebsd-update stores temporary files and downloaded updates. SEE ALSO
freebsd-update.conf(5) AUTHORS
Colin Percival <cperciva@FreeBSD.org> FreeBSD July 14, 2010 FreeBSD

Check Out this Related Man Page

PORTSNAP.CONF(5)					      BSD File Formats Manual						  PORTSNAP.CONF(5)

NAME
portsnap.conf -- configuration file for portsnap(8) DESCRIPTION
The portsnap.conf file controls where portsnap(8) fetches ports tree snapshots from, which RSA key should be trusted to sign the updates, and what directories should hold the compressed and live ports trees. A line of the form SERVERNAME=portsnap.example.com specifies the source from which snapshots should be fetched. This is equivalent to the -s server option to portsnap(8), and will be ignored if the command-line option is used. A line of the form KEYPRINT=0123456789abc ... 456789abcdef (64 characters in total) specifies the SHA-256 hash of the OpenSSL public key file belonging to an RSA keypair which is trusted to sign updates. This is equivalent to the -k KEY option to portsnap(8), and will be ignored if the command-line option is used. A line of the form WORKDIR=/path/to/workdir specifies the directory in which portsnap should maintain its compressed snapshot of the ports tree. This is equivalent to the -d workdir option to portsnap(8), and will be ignored if the command-line option is used. A line of the form PORTSDIR=/path/to/portstree specifies the directory in which portsnap will create the live ports tree from its compressed snapshot via the extract and update commands. This is equivalent to the -p portsdir option to portsnap(8), and will be ignored if the command-line option is used. If more than one line of any of the above forms is included in portsnap.conf then only the last one will take effect. A line of the form INDEX INDEXFILE DESCRIBEFILE will instruct portsnap(8) that the specified INDEX file is generated from the specified describe file distributed by the portsnap server. Finally, a line of the form REFUSE foo bar will instruct portsnap(8) to ignore parts of the ports tree with paths starting with foo or bar, which are interpreted as extended regular expressions by egrep(1). This will result in those parts of the tree not being updated in the compressed snapshot when the fetch and cron commands are used and not being extracted when the extract command is used (unless a specific path is passed to portsnap(8)), and if those parts of the ports tree are present they will not be updated when the update command is used. Unlike the other options, the parameters in REFUSE lines accumulate and all such lines are considered. Note that operating with an incomplete ports tree is not supported and may cause unexpected results. Any lines not of the above forms will be ignored. FILES
/etc/portsnap.conf Default location of the portsnap configuration file. SEE ALSO
egrep(1), fetch(1), portsnap(8), sha256(8) AUTHORS
Colin Percival <cperciva@FreeBSD.org> FreeBSD January 30, 2005 FreeBSD
Man Page