Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Patrick Wildt edited this page · 14 revisions


What is Bitrig's goal?

Bitrig wants to foster an open source community with the goal of creating an operating system that is free and fun to work on. We want to leverage other open source projects while being an active participant in those communities.

  • Target actively developing hardware only. Legacy platforms are fun to hack on however we are trying to go along with new trends.
  • Use social networks to disseminate information and news.
  • Become an incubator for students who wish to contribute via GSoC and internships.
  • Be a commercially friendly code base by using BSD or ISC licenses where possible.
Do you have a roadmap?

Yes we do! Please see our roadmap page.

Where is Bitrig located?

Bitrig is based out of Texas, USA. Work is currently underway to create a non-profit organization that can accept charitable donations.

How do I contribute to Bitrig?

We are always looking for developers who can help moving the project forward. There are several ways one can contribute to Bitrig.

  • Code, there are large todo items on our roadmap and smaller ones (including bugs) on the issues page.
  • Ports, we are still fighting plenty of ports issues due to the tuple change. Additionally we are looking for original ports as well.
  • Artwork, we are always looking for more logos, icons etc.
  • Advocacy, feel free to say nice things about us :-)
Is there a tips & tricks page?

Yes there is!

Where did Bitrig come from?

Bitrig was forked from OpenBSD.

Why did you fork OpenBSD?

OpenBSD is an amazing project and has some of the best code around but some of us are of the opinion that it could use a bit of modernization. OpenBSD is a very security conscious project and, correspondingly, has to be more conservative with features. We want to be less restrictive with the codebase when it comes to experimenting with features.

What is different from OpenBSD?

1. Architectures. Bitrig only supports current architectures, specifically, amd64 and armv7. We are not opposed to supporting other architectures, but our development efforts are directed towards modernization, not supporting old hardware.

2. Compiler + toolchain. Bitrig is currently based on LLVM's clang 3.6, which provides performance gains over gcc 4.2 for both C and C++ code. Furthermore the GNU libstdc++ toolchain has been replaced by libc++ and libc++abi.

3. New features planned, such as support for virtualization. As computers scale up in processor power, that technology is increasingly useful.

Do you have mailing lists? source changes, to subscribe email - technical discussion / patch submission, to subscribe email

Why is the project named Bitrig?

The name Bitrig is derived from the Latin "Bitrigus", the name of the software used by the Romans to conquer Europe. Sadly, not having zero among its numerals made traditional computer science difficult for the Romans and the project was put on hold indefinitely. Bitrigus faded into obscurity until it was recently rediscovered at a Viking archaeological site in the modern day country of Iceland.

The Roman emperor Hadrian is rumored to have sent Bitrigus as far west as a boat could carry it to keep it from the then growing threat of religious fanaticism within the Roman Empire.


The current plan is to keep the OpenBSD ports tree, however, this plan may change in the near future.

Developers are currently working on implementing the OS name change from OpenBSD to Bitrig in ports. This is surprisingly non-trivial and the initial focus is on ports that are widely used, e.g. mozilla-firefox, libreoffice.


In the coming months there will be infrastructure changes to facilitate virtualization at close to native speeds. A particular approach has not been selected so far and our goal will be to make virtualization possible with the least negative impact to OS security.

We understand that the ability to virtualize guest OSes is often a trade-off between utility and security. Expect this section to be updated as progress occurs on the virtualization front.

Something went wrong with that request. Please try again.