Re: OpenBSD isn't good just because it's secure

------P5ZHM5CXGF8AGDM7G1N7SV68FLU6WN
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

I don't know that it's within the purview of designing and programming a co=
mputer operating system, but there are far too many "dark web" drug dealers=
 and mafia associates on all the OpenBSD lists=2E Are there any Narcotics A=
nonymous people or similar groups or individuals with related interests in =
highly secure computer systems?

If the "law" as such needs to be involved in saying no to drugs, or simply=
 locks on all our pantry doors and keeping our food and drink free of adult=
eration and contamination while programming any computer systems=2E

The FBI/RCMP cross-border mental health drug party has to be stopped or el=
se there is no such thing as a secure computer operating system, OpenBSD or=
 otherwise=2E It's going to take a lot of guns to say no to the drugs, and =
to the corrupt cops and disreputable doctors on both sides of the border wh=
o deal drugs so forcibly=2E Physical meatspace security is an absolute prer=
equisite for online cyberspace security=2E


On May 23, 2025 8:31:41 AM AKDT, "H=2E Hartzer" <h@hartzer=2Esh> wrote:
>Hi advocacy@,
>
>This list doesn't seem to be too active, but I thought it was the right
>one to share this on=2E
>
>I've started a Gemini[1] site and wrote a post about my migration to
>OpenBSD[2]=2E
>
>The format of the post is the gemtext, but I feel it's pretty readable
>for here=2E So here it is, for the curious, with mild formatting edits to
>make it more appropriate for email=2E
>
>-Henrich
>
>1: https://geminiprotocol=2Enet/
>2: gemini://hartzer=2Esh/gemlog/2025-05-23-openbsd-isnt-good-just-because=
-its-secure=2Egmi=20
>
>
>---
>
>
># 2025-05-23: OpenBSD isn't good just because it's secure
>
>The number one marketed aspect of OpenBSD is that it's secure=2E And
>I think that's been proven true over the years=2E pledge() and unveil()
>are frankly fantastic=2E But after finally using OpenBSD as a daily
>driver for a little while, I feel like it's disingenuous to only
>focus on the security aspect=2E I had assumed, based on the large
>security label put over OpenBSD, that it wasn't such a great
>desktop/laptop daily driver=2E It most certainly is a great one=2E
>
>Previously, I had been using FreeBSD for quite a while=2E And I still
>use it on a number of servers=2E Before that, Linux, which I still
>use quite a bit for one purpose or another=2E
>
>I have a bit of an attachment to FreeBSD and switching away from
>it was not a light decision=2E Lots of loyalty built up over the
>years, familiarity, and comfort=2E And I feel that FreeBSD has a
>number of compelling aspects for many=2E
>
>But most of my draw with FreeBSD has also applied to OpenBSD=2E It's
>a bit "less" than Linux=2E The development cycle is slower=2E The
>security model seems more reasonable than Linux's=2E Not that you
>can't be reasonably secure on Linux, but I think it's scope and
>general design (containers included) make it more difficult=2E Not
>that the average user isn't well served by certain Linux distributions=2E
>
>In my case, my needs are pretty minor=2E I run older hardware with
>gigabit expectations of performance=2E I'm not doing machine learning
>with expensive GPUs, running hundreds of containers, and counting
>each second of my boot times=2E Linux is a bit overkill=2E Not to mention
>the systemd aspect which can be avoided, but tends to come with the
>whole Linux package=2E Outside of say Alpine, most notably=2E
>
>FreeBSD is technologically a bit of a step down from Linux, and
>I've liked it that way=2E Now, that's not totally true=2E It's had ZFS
>for some time, which is awfully impressive=2E And FreeBSD has thrown
>some legendary network performance figures=2E It's just generally
>less bleeding edge than Linux, more thoroughly documented, and a
>little bit easier for me to use=2E
>
>I'd put myself in the "tinkerer" category, where I like being able
>to identify and fix a bug, or make some adjustment, or at least
>understand what's going on=2E And keeping up with Linux' pace is a
>lot for my hobbyist level of involvement=2E Technology seems like
>it's pretty good where it's at, in many aspects, and fast paced
>development often means more steps backward than forward -- for
>someone without sky-high expectations=2E FreeBSD also has a better
>"solid" feel to it, having a more consistent ideology throughout=2E
>Rather than just being a kernel, with some expectations, and some
>userland thrown on top=2E
>
>This all applies to OpenBSD, and even more so=2E OpenBSD's codebase
>is a bit slimmer yet than FreeBSD's=2E It doesn't have Jails or any
>equivalent (though pledge(), unveil(), and pf can accomplish most
>of what you might sanely want to do=2E) It's even a bit more "behind"
>FreeBSD in some ways=2E But this aspect of being behind, for me, is
>a good thing=2E It's less flashy, but more thorough=2E
>
>I managed to get a few patches in for FreeBSD and a number of bug
>reports=2E I love that it's (now) developed with git=2E Being able to
>open up a pull request and get feedback is something I'm very
>familiar with=2E However, FreeBSD for me was a frustrating daily
>driver=2E Wayland on FreeBSD is a joy, but memory management on FreeBSD
>seems to have some serious issues, at least on my hardware (older
>amd64 architecture=2E)
>
>I have a long bug report about my attempts of running Firefox on
>FreeBSD=2E And it does run, but it fails to evict pages from laundry,
>or so I understand=2E So Firefox will use more and more memory with
>quite few tabs, until something gets killed=2E And OOM killing in
>FreeBSD can take a while=2E It may have improved some in 14=2E1=2E
>
>I appreciate the various developers working with me on it, but the
>fact is that basic browsing would result in one crash after another=2E
>And it wasn't just Firefox, GIMP was also quite prone to run out
>of memory in conditions you wouldn't normally expect=2E But it was
>so bad that with 16GB of memory, I'd have issues every couple of
>days=2E With 8GB, several times a day=2E
>
>I had a final straw with FreeBSD, which was 14=2E2=2E 14=2E2 wouldn't
>boot on my old, tested, and well known hardware (primarily Thinkpads
>-- T400, R500, X200, etc=2E)
>
>I narrowed it down to where I could boot 14=2E2 if I installed 2GB
>of memory, or if I disabled SMP=2E I could also boot if I set a 4GB
>limit at boot time, which yes, is a lot better than being confined
>to 2GB of memory=2E Now disabling SMP on such old hardware is a big
>hit performance wise, but the bigger hit is that this brought about
>new, bizarre bugs=2E And Firefox with 4GB of memory left me in a
>situation where I couldn't even reliably have a single tab browsing
>a website like Home Depot's, without OOM=2E This isn't just a swap
>issue, either=2E
>
>But with no resolution to those issues and 14=2E1 being on the chopping
>block, I simply couldn't use FreeBSD anymore as a daily driver=2E
>
>## Time to give OpenBSD a try=2E=2E=2E
>
>This led to me giving OpenBSD a serious try=2E I had seen for a while
>the impresive community built up around it=2E Some very neat projects
>appear to be developed on OpenBSD=2E It seemed to fit my use case a
>bit more than FreeBSD, based on what I saw being used=2E And this
>proved to be true=2E
>
>In a lot of ways, switching to OpenBSD was uneventful=2E While there
>was certainly some confusion and mental shift involved, for desktop
>use it just worked! And no more memory management issues=2E
>
>Firefox under OpenBSD is far superior to Firefox under FreeBSD=2E
>OpenBSD with 2GB of memory and no swap results in a somewhat usable
>Firefox that'll OOM sometimes=2E Add in swap, and you get something
>quite usable, and quite slow=2E But usable! Adding swap under FreeBSD
>didn't improve the Firefox situation for me=2E
>
>OpenBSD with 2GB of memory was far more usable than FreeBSD with
>4GB of memory, as far as Firefox was concerned=2E But OpenBSD will
>let me boot with my full two cores *and* 8GB of memory=2E And with
>8GB of memory, I have to try a lot harder to push Firefox to the
>point of it being slow or eventually OOMing=2E Which is doable --
>Firefox and modern websites are pigs=2E But overall, things are smooth
>enough on this 16? year old hardware=2E
>
>OpenBSD's pledge() and unveil() don't just stay relegated to base
>components like OpenSSH -- they are even patched into Firefox which
>makes it a much more trustworthy setup, without jumping through
>hoops like doing say a Jail + VNC to try and isolate Firefox, or
>running it as another user=2E
>
>I will note that Wayland also works under OpenBSD, though it's less
>polished than FreeBSD=2E Far fewer ports for it=2E I feel that this may
>change in time=2E
>
>## OpenBSD is a "batteries included" OS
>
>While OpenBSD won't get you browsing without installing packages/ports,
>on the server side it's awfully complete=2E You get a good HTTP daemon,
>even an ACME client for SSL, authoritative DNS server, caching DNS
>server, and easily enough to run a router=2E I appreciate this quite
>a bit=2E These are well documented and tested components, already
>configured in a sane and secure model=2E
>
>## OpenBSD is easy to contribute to
>
>Despite not having my familiar git + pull request developmental
>model, OpenBSD's lists are quite active=2E I've had a few contributions
>already, all quite minor=2E Now sometimes I get crickets, I think in
>particular if the topic is a bit controversial, but it's quite easy
>to start a discussion that results in a commit on an obvious matter=2E
>There's three commits that mention discussion I was involved with,
>and I've only been using OpenBSD since the tail end of 7=2E6=2E
>
>## OpenBSD is easy to use
>
>Now, I don't think you should try to get your grandma using OpenBSD
>tomorrow, unless she was awfully savvy to begin with=2E But for me,
>as someone writing this post in neovim, under tmux and i3, to be
>hosted on Gemini, OpenBSD is really easy to figure out=2E It still
>takes some time to understand certain points, but I feel the learning
>curve is quite approachable=2E I feel like I have a good bit of a
>comfort with a system that I'm happy with, I know where to look,
>where to ask questions, and it doesn't take all day to attain this
>past some initial investment=2E
>
>Most of the ports I'm familiar with were already there=2E I am missing
>a few things, however, like Monero=2E
>
>## Not everything is perfect
>
>Some things feel like a step back, to me=2E
>
>* `ftp` (analogous to `fetch` on FreeBSD`) won't use IPv6 unless
>you tell it to=2E
>
>* There's no `make fetch-recursive` for ports=2E
>
>* FFS without softupdates is definitely not as fast=2E However,
>OpenBSD's scheduler is way better than FreeBSD's, and despite being
>slower on some aspects, it "feels" faster=2E
>
>* I understand not including ZFS, which is enormous, but ZFS certainly
>has some uses=2E I actually moved away from ZFS on FreeBSD prior to
>14=2E2=2E At one point I had a bunch of memory being held until I
>unloaded the zfs kernel module=2E I stopped using it to try and help
>track down where my memory issues were coming from=2E ZFS, though,
>is kind of like systemd in scope creep=2E
>
>* I have some audio stutter issues when using automatic performance
>adjustment=2E Without this, it seems fine=2E
>
>* OpenBSD still uses CVS=2E=2E=2E Maybe gogs will save the day?
>
>## In conclusion=2E=2E=2E
>
>OpenBSD really feels like a tinker's BSD=2E It feels like it's regularly
>developed by users on similar hardware to myself=2E And not just
>developed, but used=2E It isn't just in VirtualBox on a Macbook running
>MacOS, it's tried and tested for daily use=2E
>
>I really appreciate how it "just works" most of the time, how well
>documented it is, and how approachable it is to develop with=2E
>
>## Links
>
>https://openbsd=2Eorg/ https://freebsd=2Eorg/
>https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D280846
>https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D285867
>https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D286018
>

------P5ZHM5CXGF8AGDM7G1N7SV68FLU6WN
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div dir=3D"auto">I don't know that it's within th=
e purview of designing and programming a computer operating system, but the=
re are far too many "dark web" drug dealers and mafia associates on all the=
 OpenBSD lists=2E Are there any Narcotics Anonymous people or similar group=
s or individuals with related interests in highly secure computer systems?<=
br><br>If the "law" as such needs to be involved in saying no to drugs, or =
simply locks on all our pantry doors and keeping our food and drink free of=
 adulteration and contamination while programming any computer systems=2E<b=
r><br>The FBI/RCMP cross-border mental health drug party has to be stopped =
or else there is no such thing as a secure computer operating system, OpenB=
SD or otherwise=2E It's going to take a lot of guns to say no to the drugs,=
 and to the corrupt cops and disreputable doctors on both sides of the bord=
er who deal drugs so forcibly=2E Physical meatspace security is an absolute=
 prerequisite for online cyberspace security=2E<br></div><br><br><div class=
=3D"gmail_quote"><div dir=3D"auto">On May 23, 2025 8:31:41 AM AKDT, "H=2E H=
artzer" &lt;h@hartzer=2Esh&gt; wrote:</div><blockquote class=3D"gmail_quote=
" style=3D"margin: 0pt 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, 204=
, 204); padding-left: 1ex;">
<pre class=3D"k9mail"><div dir=3D"auto">Hi advocacy@,<br><br>This list doe=
sn't seem to be too active, but I thought it was the right<br>one to share =
this on=2E<br><br>I've started a Gemini[1] site and wrote a post about my m=
igration to<br>OpenBSD[2]=2E<br><br>The format of the post is the gemtext, =
but I feel it's pretty readable<br>for here=2E So here it is, for the curio=
us, with mild formatting edits to<br>make it more appropriate for email=2E<=
br><br>-Henrich<br><br>1: <a href=3D"https://geminiprotocol=2Enet/">https:/=
/geminiprotocol=2Enet/</a><br>2: gemini://hartzer=2Esh/gemlog/2025-05-23-op=
enbsd-isnt-good-just-because-its-secure=2Egmi <hr># 2025-05-23: OpenBSD isn=
't good just because it's secure<br><br>The number one marketed aspect of O=
penBSD is that it's secure=2E And<br>I think that's been proven true over t=
he years=2E pledge() and unveil()<br>are frankly fantastic=2E But after fin=
ally using OpenBSD as a daily<br>driver for a little while, I feel like it'=
s disingenuous to only<br>focus on the security aspect=2E I had assumed, ba=
sed on the large<br>security label put over OpenBSD, that it wasn't such a =
great<br>desktop/laptop daily driver=2E It most certainly is a great one=2E=
<br><br>Previously, I had been using FreeBSD for quite a while=2E And I sti=
ll<br>use it on a number of servers=2E Before that, Linux, which I still<br=
>use quite a bit for one purpose or another=2E<br><br>I have a bit of an at=
tachment to FreeBSD and switching away from<br>it was not a light decision=
=2E Lots of loyalty built up over the<br>years, familiarity, and comfort=2E=
 And I feel that FreeBSD has a<br>number of compelling aspects for many=2E<=
br><br>But most of my draw with FreeBSD has also applied to OpenBSD=2E It's=
<br>a bit "less" than Linux=2E The development cycle is slower=2E The<br>se=
curity model seems more reasonable than Linux's=2E Not that you<br>can't be=
 reasonably secure on Linux, but I think it's scope and<br>general design (=
containers included) make it more difficult=2E Not<br>that the average user=
 isn't well served by certain Linux distributions=2E<br><br>In my case, my =
needs are pretty minor=2E I run older hardware with<br>gigabit expectations=
 of performance=2E I'm not doing machine learning<br>with expensive GPUs, r=
unning hundreds of containers, and counting<br>each second of my boot times=
=2E Linux is a bit overkill=2E Not to mention<br>the systemd aspect which c=
an be avoided, but tends to come with the<br>whole Linux package=2E Outside=
 of say Alpine, most notably=2E<br><br>FreeBSD is technologically a bit of =
a step down from Linux, and<br>I've liked it that way=2E Now, that's not to=
tally true=2E It's had ZFS<br>for some time, which is awfully impressive=2E=
 And FreeBSD has thrown<br>some legendary network performance figures=2E It=
's just generally<br>less bleeding edge than Linux, more thoroughly documen=
ted, and a<br>little bit easier for me to use=2E<br><br>I'd put myself in t=
he "tinkerer" category, where I like being able<br>to identify and fix a bu=
g, or make some adjustment, or at least<br>understand what's going on=2E An=
d keeping up with Linux' pace is a<br>lot for my hobbyist level of involvem=
ent=2E Technology seems like<br>it's pretty good where it's at, in many asp=
ects, and fast paced<br>development often means more steps backward than fo=
rward -- for<br>someone without sky-high expectations=2E FreeBSD also has a=
 better<br>"solid" feel to it, having a more consistent ideology throughout=
=2E<br>Rather than just being a kernel, with some expectations, and some<br=
>userland thrown on top=2E<br><br>This all applies to OpenBSD, and even mor=
e so=2E OpenBSD's codebase<br>is a bit slimmer yet than FreeBSD's=2E It doe=
sn't have Jails or any<br>equivalent (though pledge(), unveil(), and pf can=
 accomplish most<br>of what you might sanely want to do=2E) It's even a bit=
 more "behind"<br>FreeBSD in some ways=2E But this aspect of being behind, =
for me, is<br>a good thing=2E It's less flashy, but more thorough=2E<br><br=
>I managed to get a few patches in for FreeBSD and a number of bug<br>repor=
ts=2E I love that it's (now) developed with git=2E Being able to<br>open up=
 a pull request and get feedback is something I'm very<br>familiar with=2E =
However, FreeBSD for me was a frustrating daily<br>driver=2E Wayland on Fre=
eBSD is a joy, but memory management on FreeBSD<br>seems to have some serio=
us issues, at least on my hardware (older<br>amd64 architecture=2E)<br><br>=
I have a long bug report about my attempts of running Firefox on<br>FreeBSD=
=2E And it does run, but it fails to evict pages from laundry,<br>or so I u=
nderstand=2E So Firefox will use more and more memory with<br>quite few tab=
s, until something gets killed=2E And OOM killing in<br>FreeBSD can take a =
while=2E It may have improved some in 14=2E1=2E<br><br>I appreciate the var=
ious developers working with me on it, but the<br>fact is that basic browsi=
ng would result in one crash after another=2E<br>And it wasn't just Firefox=
, GIMP was also quite prone to run out<br>of memory in conditions you would=
n't normally expect=2E But it was<br>so bad that with 16GB of memory, I'd h=
ave issues every couple of<br>days=2E With 8GB, several times a day=2E<br><=
br>I had a final straw with FreeBSD, which was 14=2E2=2E 14=2E2 wouldn't<br=
>boot on my old, tested, and well known hardware (primarily Thinkpads<br>--=
 T400, R500, X200, etc=2E)<br><br>I narrowed it down to where I could boot =
14=2E2 if I installed 2GB<br>of memory, or if I disabled SMP=2E I could als=
o boot if I set a 4GB<br>limit at boot time, which yes, is a lot better tha=
n being confined<br>to 2GB of memory=2E Now disabling SMP on such old hardw=
are is a big<br>hit performance wise, but the bigger hit is that this broug=
ht about<br>new, bizarre bugs=2E And Firefox with 4GB of memory left me in =
a<br>situation where I couldn't even reliably have a single tab browsing<br=
>a website like Home Depot's, without OOM=2E This isn't just a swap<br>issu=
e, either=2E<br><br>But with no resolution to those issues and 14=2E1 being=
 on the chopping<br>block, I simply couldn't use FreeBSD anymore as a daily=
 driver=2E<br><br>## Time to give OpenBSD a try=2E=2E=2E<br><br>This led to=
 me giving OpenBSD a serious try=2E I had seen for a while<br>the impresive=
 community built up around it=2E Some very neat projects<br>appear to be de=
veloped on OpenBSD=2E It seemed to fit my use case a<br>bit more than FreeB=
SD, based on what I saw being used=2E And this<br>proved to be true=2E<br><=
br>In a lot of ways, switching to OpenBSD was uneventful=2E While there<br>=
was certainly some confusion and mental shift involved, for desktop<br>use =
it just worked! And no more memory management issues=2E<br><br>Firefox unde=
r OpenBSD is far superior to Firefox under FreeBSD=2E<br>OpenBSD with 2GB o=
f memory and no swap results in a somewhat usable<br>Firefox that'll OOM so=
metimes=2E Add in swap, and you get something<br>quite usable, and quite sl=
ow=2E But usable! Adding swap under FreeBSD<br>didn't improve the Firefox s=
ituation for me=2E<br><br>OpenBSD with 2GB of memory was far more usable th=
an FreeBSD with<br>4GB of memory, as far as Firefox was concerned=2E But Op=
enBSD will<br>let me boot with my full two cores *and* 8GB of memory=2E And=
 with<br>8GB of memory, I have to try a lot harder to push Firefox to the<b=
r>point of it being slow or eventually OOMing=2E Which is doable --<br>Fire=
fox and modern websites are pigs=2E But overall, things are smooth<br>enoug=
h on this 16? year old hardware=2E<br><br>OpenBSD's pledge() and unveil() d=
on't just stay relegated to base<br>components like OpenSSH -- they are eve=
n patched into Firefox which<br>makes it a much more trustworthy setup, wit=
hout jumping through<br>hoops like doing say a Jail + VNC to try and isolat=
e Firefox, or<br>running it as another user=2E<br><br>I will note that Wayl=
and also works under OpenBSD, though it's less<br>polished than FreeBSD=2E =
Far fewer ports for it=2E I feel that this may<br>change in time=2E<br><br>=
## OpenBSD is a "batteries included" OS<br><br>While OpenBSD won't get you =
browsing without installing packages/ports,<br>on the server side it's awfu=
lly complete=2E You get a good HTTP daemon,<br>even an ACME client for SSL,=
 authoritative DNS server, caching DNS<br>server, and easily enough to run =
a router=2E I appreciate this quite<br>a bit=2E These are well documented a=
nd tested components, already<br>configured in a sane and secure model=2E<b=
r><br>## OpenBSD is easy to contribute to<br><br>Despite not having my fami=
liar git + pull request developmental<br>model, OpenBSD's lists are quite a=
ctive=2E I've had a few contributions<br>already, all quite minor=2E Now so=
metimes I get crickets, I think in<br>particular if the topic is a bit cont=
roversial, but it's quite easy<br>to start a discussion that results in a c=
ommit on an obvious matter=2E<br>There's three commits that mention discuss=
ion I was involved with,<br>and I've only been using OpenBSD since the tail=
 end of 7=2E6=2E<br><br>## OpenBSD is easy to use<br><br>Now, I don't think=
 you should try to get your grandma using OpenBSD<br>tomorrow, unless she w=
as awfully savvy to begin with=2E But for me,<br>as someone writing this po=
st in neovim, under tmux and i3, to be<br>hosted on Gemini, OpenBSD is real=
ly easy to figure out=2E It still<br>takes some time to understand certain =
points, but I feel the learning<br>curve is quite approachable=2E I feel li=
ke I have a good bit of a<br>comfort with a system that I'm happy with, I k=
now where to look,<br>where to ask questions, and it doesn't take all day t=
o attain this<br>past some initial investment=2E<br><br>Most of the ports I=
'm familiar with were already there=2E I am missing<br>a few things, howeve=
r, like Monero=2E<br><br>## Not everything is perfect<br><br>Some things fe=
el like a step back, to me=2E<br><br>* `ftp` (analogous to `fetch` on FreeB=
SD`) won't use IPv6 unless<br>you tell it to=2E<br><br>* There's no `make f=
etch-recursive` for ports=2E<br><br>* FFS without softupdates is definitely=
 not as fast=2E However,<br>OpenBSD's scheduler is way better than FreeBSD'=
s, and despite being<br>slower on some aspects, it "feels" faster=2E<br><br=
>* I understand not including ZFS, which is enormous, but ZFS certainly<br>=
has some uses=2E I actually moved away from ZFS on FreeBSD prior to<br>14=
=2E2=2E At one point I had a bunch of memory being held until I<br>unloaded=
 the zfs kernel module=2E I stopped using it to try and help<br>track down =
where my memory issues were coming from=2E ZFS, though,<br>is kind of like =
systemd in scope creep=2E<br><br>* I have some audio stutter issues when us=
ing automatic performance<br>adjustment=2E Without this, it seems fine=2E<b=
r><br>* OpenBSD still uses CVS=2E=2E=2E Maybe gogs will save the day?<br><b=
r>## In conclusion=2E=2E=2E<br><br>OpenBSD really feels like a tinker's BSD=
=2E It feels like it's regularly<br>developed by users on similar hardware =
to myself=2E And not just<br>developed, but used=2E It isn't just in Virtua=
lBox on a Macbook running<br>MacOS, it's tried and tested for daily use=2E<=
br><br>I really appreciate how it "just works" most of the time, how well<b=
r>documented it is, and how approachable it is to develop with=2E<br><br>##=
 Links<br><br><a href=3D"https://openbsd=2Eorg/">https://openbsd=2Eorg/</a>=
 <a href=3D"https://freebsd=2Eorg/">https://freebsd=2Eorg/</a><br><a href=
=3D"https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D280846">https=
://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D280846</a><br><a href=
=3D"https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D285867">https=
://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D285867</a><br><a href=
=3D"https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D286018">https=
://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D286018</a><br><br></di=
v></pre></blockquote></div></body></html>
------P5ZHM5CXGF8AGDM7G1N7SV68FLU6WN--