Linked by Bob Sacamano on Tue 12th Jun 2012 22:31 UTC
OpenBSD Bitrig, a fork of OpenBSD, has surfaced. It aims to be less conservative than OpenBSD by being less loose with new features and only supporting modern architectures. Bitrig has also converted over to using LLVM's clang rather than GNU gcc for it's toolchain/compiler. A roadmap for Bitrig is also available.
Thread beginning with comment 521826
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Interesting
by Radio on Wed 13th Jun 2012 06:11 UTC in reply to "Interesting"
Radio
Member since:
2009-06-20

I do hope they are competent. A system is only as secure as its least secure component (like a chain is only as strong as its weakest link), so it would very easy to degrade OpenBSD's main (and almost only - sorry) selling point.

Reply Parent Score: 3

RE[2]: Interesting
by gan17 on Wed 13th Jun 2012 13:09 in reply to "RE: Interesting"
gan17 Member since:
2008-06-03

Been studying the sources and visited their IRC.

It's the same Marco Peereboom.
https://opensource.conformal.com/wiki/Main_Page

Pleasantly surprised their LLVM/Clang support is already so complete.

Reply Parent Score: 2

RE[3]: Interesting
by sakeniwefu on Wed 13th Jun 2012 14:16 in reply to "RE[2]: Interesting"
sakeniwefu Member since:
2008-02-26

Mm, I have mixed feelings about this...

While the people working on this seem to be more competent and sane than the people behind MirOS or AerieBSD, the kind of fork and all the name whoring means we won't see any more contributions from them to OpenBSD and this is sad.

I for one rely on scrotwm and xxxterm. In prespective, all the silly name changing was likely in preparation for this project. The real names made it hard to sell a product.

I wish them luck. On one hand, the OpenBSD codebase is very good, on the other, the "embedded" support will require some pretty big structural changes if it has to compete with real embedded OSes. At this point it can't even stand a fight with the massive non-RT Linux market. And what will the PHBs think of security when they learn they need to upgrade to a smartphone processor to get the same performance they had with an SH4.

...

Reading the FAQ, I wonder if something as simple as a VAX backend for LLVM could have avoided this fracture.

Reply Parent Score: 3