Description
OpenBSD 6.1 site config
This project creates a siteXX.tgz file used for quick rollout of similar OpenBSD systems.
Currently testing on OpenBSD 6.1, i386 and amd64.
To get started with a new release: - clean the fossil archive by running the cleanup.sh script (you may want to create a new fossil archive first as a duplicate of an existing one) - create a vanilla OpenBSD installation of the correct version for each architecture (eg. amd64 and i386) - transfer and run the siteprep.sh script on each of the vanilla installations. this will download specific packages, build daemontools, and prompt you to transfer those packages and daemontools back to the proper location in the new fossil archive working directory. - now run the makesite.sh script to generate the siteXX.tgz fileset, and follow the directions for getting the fileset to the proper location on the OpenBSD installation mirror (if applicable).
Note: Between releases, package names and other things sometimes change. These will have to be addressed as found during testing, after which a new siteXX.tgz file can be easily generated.
Note: The postupgrade.site file is a best-effort attempt at automating upgrades, and will need to be addressed for each new release since the instructions are different each time. I personally never use this, as I always perform a wipe/reload and push configuration out via ansible instead of going through the upgrade process.
Note: The diskmirror.txt script (named as .txt for ease of viewing from the mirror) was last checked on 5.9. To use, boot your blank machine from bsd.rd and drop to a shell. Configure networking (you can simply use dhcpd ifname) and grab the script from the mirror (eg. ftp http://my.openbsd.mirror/pub/OpenBSD/diskmirror.txt). Then execute the script and provide disk devices to use as mirror components. This results in a simple bootable softraid mirror with small filesystem sizes (OpenBSD really only needs 400MB or so). The idea here is to keep the OS small and create /data or whatever other filesystem to store actual data (this can also leverage softraid mirroring, raid5, or whatever).
This document is written in markdown:
Manage this file in the repository at this location: docs/README.md