Some additional information OpenBSD admins need to know, that may not be obvious from my previous posting:
- OpenBSD is source code maintained. To make changes to OpenBSD source code, an admin needs to understand the tools used for managing OpenBSD source: cvs(1), diff(1), and patch(1). The OpenBSD Project uses unified diffs only, by the way: diff -u is mandatory when creating patch files.
- OpenBSD admins need to understand the flavors of OpenBSD, the release lifecycle, and how cvs is used to manage these. A cvs log for an individual file must be understandable: the revision history and associated tags need to be understood.
- Any patch which is to be applied to a different source code version will likely require manual integration. In this case, Darshadow would likely have to revise the patch to be able to apply it to 4.9-release, since it was developed against 4.8-current.
Understanding FAQ 5 is also a necessity.