content: There is a Wikipedia page that does a decent job explaining. Once upon a time there was one BSD, a series of patches and tools you would add to Unix.   Then there was a lovely little legal issue of who owned BSD, after the dust settled from that legal mess two BSD codebases arose - FreeBSD and NetBSD. One was run by a few cucks and a Afrikaaner-Canadian, that was NetBSD.  NetBSD went on for a while and people were uncomfortable with how Theo would call people out on their bullshit, he would insult their code, their coding ability, and even refuse patches if the code was bad.  This de Raadt fellow kept grating on nerves for a year before the cucks in the crowd cut off his access to NetBSD's code and terminated all interaction with him, effectively cutting him out of the project. So he started his own BSD, with security and code quality.  OpenBSD forked from NetBSD and began to draw in like minded grumpy men who were interested in code that worked and was clean and easy to read over magic numbers and obtuse poorly cobbled together shit that seemed to work. It created OpenSSH, the standard SSH implementation that nearly the entire world uses.  It forked OpenSSL when it was found to be entirely insecure and created LibreSSL, which nearly every system running OpenSSH has. It has existed entirely distinct from FreeBSD its entire history, incorporating minor driver and tool components only when the license was proper and the code was good enough. OpenBSD's wireless networking framework was so much better than that of the other BSDs that major parts of the code were taken from OpenBSD and incorporated into NetBSD and FreeBSD both. OpenBSD is far and away less end-user friendly than FreeBSD, which has guides and hand holding in many places.  OpenBSD has a lot of extremely high quality man pages and it expects you to read them, not a guide.