NetBSD 9.3
blog.netbsd.org
blog.netbsd.org
Bonus points for their build system. It's about the only time I've ever felt like building from source was a pleasant experience.
It doesn't have the community like FreeBSD nor innovations like OpenBSD.
But admittedly it doesn't seem to have quite the following of those two other BSDs.
I love when projects add fun things such as this.
At least in 2017:
https://twitter.com/fastly/status/934495679849881601?s=21&t=...
Also on Jump Hosts with a weird cpu architecture, so that you could not do much with them
pkgsrc enjoys mild popularity in the scientific computing community, a lot of NetBSD use is probably in education - Cambridge University uses it for their thin clients too.
>wpi%d: fatal firmware error For some reason, the firmware crashed. The driver will reset the hardware. This should not happen.
They know.
I'm a long-time Tiny Core Linux user (loving it!), but I often think about trying out NetBSD more seriously. The documentation seems superb; apparently, it is not hard to reconfigure some bits of the kernel even as more of a "lean systems hobbyist". From what I have read, it is quite convenient to set up as a RAM-booted system, just like Tiny Core.
NetBSD (probably 7.0 or 6.1) was a pleasant experience for me on a Thinkpad T42 some 6-7 years ago.
It feels like at this point, Linux has the most choice out of the box, when it comes to software for displaying images/pdfs on the framebuffer? I use fbpdf on Linux, which is not available on NetBSD. Then again, it is based on libmupdf, which is available, so maybe I should get my (shaking) hands dirty. :)
I like it very much how NetBSD encourages user-side modifications of the kernel, e.g. for changing the console font or underclocking the cpu. Every time I read the NetBSD documentation, I feel tempted to install it, because the docs are so well structured and written. Very welcoming, even for (curious) non-CS users like me.
For that reason, using NetBSD may possibly be more educational than using Linux, in the long run? Due to heavy reliance on the official documentation, you'll have a more structured understanding of how stuff works -- as compared to trawling web forums of various Linux distros and sometimes blindly copy-pasting solutions or hacks provided by others. In that sense, a good base documentation encourages more acknowledged use and going to the details from early on. (Obviously, there are Linux distros witch excellent documentation, too, like the Arch wiki.)
That said, I am rather pleased with Tiny Core Linux. Their current release is something like 12.x, and I've been in their boat since version 6.x. It is a really simple, well thought out distro, excellent for older hardware; somewhat similar in that sense to the BSDs. But, yeah, sans that documentation. :)
However, I can always convert PDFs to images and go forward from there, I guess. It's not a bad workaround. The fbi image viewer is available for NetBSD's X Window system; not sure about the framebuffer port. https://www.kraxel.org/blog/linux/fbida/
EDIT: Apparently, NetBSD has lsix: https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/graphics/ls...
"Like ls, but for images. Shows thumbnails in terminal using sixel graphics. /.../ Because lsix uses ImageMagick pretty much any image format will be supported. However, some may be slow to render (like PDF), so lsix doesn't show them unless you ask specifically."
On Linux, the green pdf reader for Linux apparently supports sixel: https://github.com/schandinat/green
Screenshot of green+sixel on NixOS: https://teddit.net/r/commandline/comments/4oldf5/view_pdfs_i...
Another Linux pdf reader with sixel: https://github.com/dsanson/termpdf
All in all, woah, lots of fascinating reading and links here -- since I was not much aware of sixel before: https://github.com/saitoha/libsixel
The sixel format itself seems to match really well with the NetBSD philosophy (among other things, keeping old hardware running via low-demanding, essentials-only software). Thanks again for that pointer.
ssh works exactly the same as on linux as well.
https://github.com/bsdlabs/ssh-hardening
Then lock-down with PF (firewall).
Overall hardened FreeBSD:
Or take parts of this Gist: