Hitchhiker's Guide to Openbsd

Doing a release
Define our DESTDIR and RELEASEDIR environment variables: 
# export DESTDIR=/usr/dest
# export RELEASEDIR=/usr/rel
We now clear the DESTDIR and create the directories if needed: 
# test -d ${DESTDIR} && mv ${DESTDIR} ${DESTDIR}.old && rm -
rf ${DESTDIR}.old &
# mkdir -p ${DESTDIR} ${RELEASEDIR}
RELEASEDIR does not normally need to be empty before starting the release process, however, if there 
are changes in the release files or their names, old files may be left laying around. You may wish to also 
http://www.openbsd.org/faq/faq5.html (12 of 26)9/4/2011 10:02:02 AM

---

5 - Building the System from Source
erase this directory before starting. 
We now make the release itself: 
# cd /usr/src/etc
# make release
After the release is made, it is a good idea to check the release to make sure the tar files are matching 
what is in the DESTDIR. The output of this step should be very minimal. 
# cd /usr/src/distrib/sets
# sh checkflist
You now have complete and checked release file sets in the RELEASEDIR. These files can now be used 
to install or upgrade OpenBSD on other machines. 
The authoritative instructions on making a release are in 
release(8)
. 
Note: if you wish to distribute the resultant files by HTTP for use by the upgrade or install scripts, you 
will need to add an "index.txt" file, which contains the list of all the files in your newly created release. 
# /bin/ls -1 >index.txt
Once you have the complete release made, you can use those files for a standard 
install
 or 
upgrade
 on 
another machine, or if updating a machine to a new -stable, simply 
unpack
 the tar files in the root 
directory of the target machine.