Bitrig: OpenBSD fork for the 21st Century

[acheng]

最近了解到一个openBSD衍生系统 Bitrig。它将会在OpenBSD的基础上引入KVM、更好的多处理器支持、新的文件系统以及编译系统和工具等“现代化”的特性。并计划支持ARM CPU。

该项目计划于本月底推出第一个公开发行的版本。拭目以待中...

https://www.bitrig.org/index.php?title=FAQ
https://www.bitrig.org/index.php?title=Roadmap

[leo]

在长沙还打不开，搬梯子后看见了Powered by Mediawiki, 难道这个也墙了？

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 those communities.

• Target actively developing hardware only. Legacy platforms are fun to hack on however we are trying to go along with new trends.
• Make the base system as small as possible in order to be able to run on embedded systems.
• Use social networks to disseminate information and news.
• Try to become an incubator for students who wish to contribute via GSoC and internships.
• Be a very commercially friendly code base by using non-viral licenses where possible.
• We are aiming to have long lived releases and paid for maintenance (this process is still being defined).
• Do a major release every year with a quarterly RC (Release Candidate). Snapshots will be provided throughout the year as well.

Do you have a roadmap?
Yes we do! Please see our roadmap page.
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 however some of us are of the opinion that it could use a bit of modernization. OpenBSD is a very security conscious project and inherently it has to be more conservative with features. We want to be a bit more loose when it comes to experimenting with features.
What is different from OpenBSD?
1. Architectures. Bitrig only supports current architectures, specifically, i386 and amd64. Support is planned for arm devices. 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.1, which provides very significant performance gains over gcc 4.2 for both C and C++ code, and the latest GNU toolchain.
3. New features planned, such as support for virtualization and journaling. As computers scale up in processor power and disk size, these technologies are increasingly useful.
How is Bitrig organized?
Please see our organization page.

roadmap

[f5b]

早上在slashdot看到Bitrig的消息，没想到acheng在gobsd抢先发布了:)

国内不同城市、不同网络运营商在不同时间的围墙高度和质量都不一样，f5b很生气。
Bitrig网站今天广州可以访问。

[f5b]

NetbBSD > OpenBSD > Bitrig
每fork一次，支持平台数量都会减少。

[f5b]

最近OpenBSD上的snapshot更新频率很低，不知道是否跟developer分家有关。

[碧落星河]

对KVM很感兴趣，OB上的虚拟软件太不给力了。
freebsd上面都有了virtualbox，不知为什么OB不移植过来，virtualbox不是开源的吗？

[f5b]

Theo de Raadt 开口了
详情http://marc.info/?t=133961305400003&r=1&w=2


>On Wed, Jun 13, 2012 at 7:44 PM, Dominguez, Roland
><[email protected]> wrote:
>> I just came across this article and was wondering if it's legit:
>> http://www.h-online.com/open/news/item/ ... rig-161695
>> 4.html
>
>Yes, it's legit and it reflects the reality of the facts

Except for the fact that it is bullshit.

They started the fork because they got kicked out because one
developer (Marco) hired 5 other developers for his startup company,
and attempted to hire around 10 other developers in a sneaky and
underhanded way. They were told, oh i forget they were "asked", to
not tell anyone else in OpenBSD that this was happening, probably
because people "including Theo" would be upset.

Funny thing is, I've never been upset about the 20+ OpenBSD and
ex-OpenBSD developers who now work for google.

Previously, many of those developers were in critical positions in the
development team. As they were suddenly hired with such terms and
conditions, they became more scarce in OpenBSD -- perhaps because they
suddenly got real busy with work, but also to avoid telling others
that this was happening. Various projects lagged. To avoid telling a
lie, they instead chose to not tell the truth. It had effects. It
was dishonest of them to not tell their co-developers that they were
creating vacuums in the development process.

So because of those decisions, they are now gone from OpenBSD. And
now they miss it. So now, all these guys who work for the same
company have started a fork. And it is directed by the guy who hired
them in the first place.

From where I stand, that is the truth.

Yet none of that is in that article, because the truth hurts,
doesn't it guys?

[acheng]

对KVM很感兴趣，OB上的虚拟软件太不给力了。
freebsd上面都有了virtualbox，不知为什么OB不移植过来，virtualbox不是开源的吗？

OpenBSD开发人员大都认为虚拟化技术有一些无法克服的安全隐患，所以他们对这些技术不大感冒...

[acheng]

也看到了Theo的邮件，对于bitrig这个分支的缘由也有了更多的了解。
但不管怎么说，作为一个普通用户，选择多一些总是好事。以OpenBSD目前的技术风格，在国内推广有些难度