Hi, ty armour wrote on Sat, Jan 23, 2016 at 04:29:07PM -0500:
> I am looking for tutorials on developing any and every aspect of > OpenBSD, from bootloaders to device drivers to writing a > raspberry pi image of OpenBSD. > > The more tutorials the better, OpenBSD developers tend to think the opposite. We highly value reference documentation, in particular manual pages. If you need more details than the manual pages offer, read the source code. In general, we discourage writing tutorials because they are often written by people who barely know what they are talking about, because they encourage the wrong style of learning (gobbling together random bits and pieces without real understanding), and because they are almost impossible to maintain. Besides, developers prefer to spend their time on code rather than on tutorials. So please don't write tutorials, write reference manuals. > because it allows the end user to not only provide useful feedback > to the developers, it allows the user to customize their install > in a safe and easy manner. OpenBSD developers tend to think the opposite. We generally discourage gratuitious customization, highly value sane defaults and encourage using them as much as possible. It helps security, it helps to work on someone else's system when you need to, and it tremendously helps support. Customization breeds bugs and hurts interoperability. > You could post tutorials for writing custom audio and graphics > frameworks too as I am looking to write a few frameworks myself. OpenBSD developers tend to avoid writing frameworks as much as possible - of course, some frameworks must exist, but as few as possible. Usually, the less abstraction, the better. It makes code easier to understand, audit, and debug. [...] > including how to get software to run under openbsd That does exist and is maintained: http://www.openbsd.org/faq/ports/ http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/bsd.port.mk.5 Yours, Ingo
