"What's your NetBSD story?"
(deep breath) ... okay, this is long. Sorry.
I grew up on 4.2BSD in 1984. I've been following BSD through 4.3BSD, then its sub-incarnations as SunOS 3.x and 4.x, and when I finally found 0.8 in 1993, especially with the AT&T v. UCB flapdoodle (which ended favourably to the open-source community, mostly -- I can't imagine that writing the scheduler and the hardclock routines were trivial tasks), I was thinking, I gotta check this out.
I got NetBSD-1.1 for SPARC running at work one day, on a dual-disk system. I booted from the NetBSD disk but neglected to tell it to use /dev/sd1a as the root filesystem, so it booted up the GENERIC NetBSD kernel, but everything else was SunOS. The only things that failed were the kmem grovelers (ps, uptime, w, and their ilk) -- EVERYTHING else worked. The SunOS emulation code was that good, out of the box, on a one-dot release.
Fast forward, and my first me-owned "personal computer" was a SPARCstation IPX, around the time that Sun had released 4.1.4 (which was, I believe, their last move before giving messy, premature birth to the bastard child that was to grow up into Solaris Two Dot). I was given the system as a bonus from work (we had lots of Sun hardware but precious little x86 hardware at the time).
NetBSD was the ONLY even remotely stable system for the SPARC hardware, outside of SunOS, and I was damned if I was going to put Slowaris on my IPX.
[Those were the days when memory was measured in Megabytes, and disk space was measured in hundreds of Megabytes. But I digress.]
Since 1995, I've migrated from the IPX, to a SPARCstation 5, to the Athlon-II, to the Athlon64, to an i7-4770, which I'm still using.
In retrospect, the layout of the filesystems and the devices matches most closely to what I think the CSRG would have done had 4.4BSD actually seen more of the light of day than it did.
Lately, my work environments have been Linux back-ends with Windows {desk/,lap}tops. When I drop one of the Linux servers into single-user mode, and do 'ps ax', there are about thirty processes running, give or take.
When I do the same on a NetBSD box, there are four: kernel, init, sh, and ps.
It's familiar, it's friendly. I'm still using ipf because I haven't sussed out npf yet [I hope npf doesn't behave like the one pfSense uses, because it did some things that made CVS stop working].
My server AND my firewall/router are NetBSD. I want to migrate my Raspberry Pi 2 B+ to NetBSD (nameserver) because I don't think Raspbian plays as nicely with CARP.
That NetBSD just got NCQ/SATA (I JUST found this out today) is a HUGE coup in my mind. I'm looking forward to getting NVMM running on the server somewhere down the road.
I never was really enthusiastic about Linux in the first place, and once systemd and Wayland walked onto the scene, I decided I would never again run Linux in my house (I'd rather deal with Windows 10 for the duration). I tried FreeBSD a couple times but it didn't grab me. I might reach to OpenBSD for a server installation, but as Net works fine for me, I don't see the point at the moment.
[and holy gods what a schism THAT was. Got my shoes dirty in the Bog of Eternal Stench on that one!]
(exhale). So that's my story.