<story><title>What I think what we need to do to keep FreeBSD relevant (2019)</title><url>https://www.leidinger.net/blog/2019/01/27/strategic-thinking-or-what-i-think-what-we-need-to-do-to-keep-freebsd-relevant/</url></story><parent_chain></parent_chain><comment><author>alexhutcheson</author><text>Quick summary:&lt;p&gt;- Port several container and virtualization systems (OpenStack, OpenNebula, oVirt, CloudStack, Kubernetes, Docker, Podman, …)  to FreeBSD.&lt;p&gt;- Improve linuxolator, and run Linux tests on linuxolator as part of FreeBSD CI.&lt;p&gt;- Make kerberos work.&lt;p&gt;- Port more SDN software to FreeBSD and improve the documentation for it.&lt;p&gt;- Add interfaces to hardware sensors (fans, voltage, temperature, etc.)&lt;p&gt;- Add an implementation of Multipath TCP.&lt;p&gt;- Make SecureBoot work.&lt;p&gt;- Support writing kernel modules in C++ or Rust.&lt;p&gt;- Improve end-user HOWTO docs on how to use specific 3rd party software (mail server, web server, display server, etc.) with FreeBSD.&lt;p&gt;- Review existing docs and remove outdated information.&lt;p&gt;- Add a &amp;quot;cloud&amp;quot; section to end-user docs.&lt;p&gt;- Use doxygen or a similar system to generate additional developer docs from source code.&lt;p&gt;- Polish and improve DTrace.&lt;p&gt;- Make default options for ports packages consistent.&lt;p&gt;- Create &amp;quot;meta-ports&amp;quot; for specific use-cases (webserver, database, etc.)&lt;p&gt;- Revise default settings to target improved performance on modern machines.&lt;p&gt;- Add fuzzers and Clang sanitizers to FreeBSD CI.&lt;p&gt;- Make the CI system more visible.&lt;p&gt;[I&amp;#x27;m not the author, just a guy reading the post. Add a comment if I missed anything important]</text></comment>
<story><title>What I think what we need to do to keep FreeBSD relevant (2019)</title><url>https://www.leidinger.net/blog/2019/01/27/strategic-thinking-or-what-i-think-what-we-need-to-do-to-keep-freebsd-relevant/</url></story><parent_chain></parent_chain><comment><author>pnako</author><text>It seems to me like a list of things the Linux community is working on; and I think that&amp;#x27;s a bit of the problem with FreeBSD. For a long time, it was known as the &amp;quot;high-reliability &amp;#x2F; high-performance server OS&amp;quot;. But Linux has mostly taken that crown now, for quite a few years. Where does that leave FreeBSD? I wouldn&amp;#x27;t be able to define FreeBSD&amp;#x27;s identity at the moment; but granted I&amp;#x27;m more a OpenBSD user.&lt;p&gt;It&amp;#x27;s easier to define OpenBSD, beyond the obvious stuff (security). It&amp;#x27;s a system that does not really want to deviate too much from old-school Unix, and a community that firmly rejects any fad or fashion and embraces simple, and indeed sometimes simplistic solutions. That doesn&amp;#x27;t make it the best system for everything, but at least we know where it stands: the best old-school Unix OS. It&amp;#x27;s almost as if it lives in a parallel universe where time has stopped in 1990, and the OpenBSD developers are asymptotically converging to the perfect Unix system of that era. I&amp;#x27;m not saying that as a criticism at all.&lt;p&gt;And NetBSD and Dragonfly BSD are also, more or less explicitly, research operating systems where individual developers can come and try stuff.&lt;p&gt;FreeBSD is still a very impressive project but I think they can do better than being just-like-Linux-but-five-years-later.</text></comment>