#+TITLE: 025 / 100daystooffload my BSD Love story
#+AUTHOR: screwtape
* Two helping hands from BSD
** inetd and gophernicus
Networking is hard to grok. A rollercoaster without a safety bar. And
you have to build it yourself, and yourself and everyone you love is
going to be on the maiden run. And you can't choose not to come.

Fortunately I am a recipient of how great openbsd is. On all the BSDs,
inetd(8) internet super-server is the expected norm, implying high
quality handling of all that networking stuff, rate limiting, figuring
out what network connection is whose, what to run. It is with this
context my friend Paul Someoneelse pioneers and shares lispy openbsd
networking [[codeberg.org/pkw/web]]. Collaborative designed-accessible
security is a name of the game, leading to the secure, dependable and
fully featured gophernicus(1) amoung gopher servers (pledge(2)d and
unveil(2)ed).

I was having trouble with enabling UTF-8 - what I had done ended
up... A message to the mailing list taught me that I was setting my
locale stuff too late, and over time helping context to find out that
that commentary was the appropriate and useful thing to say. It's nice
to feel halfway competent with my pf.conf(5) from the culture of
sharing knowledge and accessibility of safety and strength.

This is not just about openbsd. If anything, juxtaposing the stock
bozohttpd(8) on netbsd to openbsd httpd(8) basically got me
comfortable with inetd(8) at all, and the fairly gentooian FreeBSD
install handbook on So You Want X (and openbsd for the fainter of
heart). Actually this helped me port interlisp's maiko virtual machine
build scripts of which one existed then for freebsd to openbsd
readily. So I would even say the BSDs are a team (including
difficulties, differences, disagreements) that make the lispy gopher
climate possible! (literally SDF where the magic happens mainly uses
netbsd).