fictional news - What will happen after the fall of BSD?

[nasyt]

OSnews - Students at the Cambridge University build their own unix system

OSnews - Students at the Cambridge University build their own unix system

Cambridge University: A group of Students began to build their own Unix-Like OS based on the ICAS framework. They desired to build a new kernel, that is able to utilize 64fs and the powerful ICAS TCP/IP stack. The Kernel will be distributed under the Apache License 2.0.

Phoronix - "Independent *nix" 0.1 Alpha: the first pre-release of the new Unix-Like OS

"Independent *nix", a MPL 2.0 Licensed Unix-Like operating system derived from xv6, a re-implementation of Dennis Ritchie's and Ken Thompson's Unix Version 6, experiences its first public release. It incorporates some ICAS components such as Vfs, Bdi and 64fs. There also plans to adopt HTN.i-tcpip.

[nasyt]

AboutTheBSDs noticed ICAS - "Is ICAS the next BSD?"

AboutTheBSDs noticed ICAS

AboutTheBSDs - Is ICAS the next BSD?

I recently read, that Apple got new fuel from ICAS, an open source project with a obviously proprietary-friendly license. ICAS was founded as a proprietary-friendly set of kernel building-blocks, kickstarted by proprietary software vendors such as Apple and Microsoft to gain new fuel for their proprietary products. Unfortunately I wasn't wary enough to detect these new atrocities going on there. ...... The network stack that they're released obviously was an former proprietary inhouse TCP/IP stack, but they should have kept it closed rather than offer it to Apple to incorporate. That new filesystem, 64fs, however is a cheap ext4 rip-off. They studied ext4 and wrote a broken remake in C++ and published it to Apple. The "Anywhere Threading" technology is just a rip-off of Linux' kernel preemtion. Basically it looks like ICAS simply copys ideas from the Linux kernel and reimplements them to get rid of the GPL. Maybe the Linux kernel developers can accuse the code, that is massively inspired by Linux as a "derived work" and sue these Leeches. ...... We should be wary of this project, that try to reimplement a new BSD system. As ICAS is not protected by the GPL, it will die soon. Until then, I will keep you up this news of these atrocities and thefts this project perceptrates.

[nasyt]

Dimitri Zet's Blog - AboutTheBSDs is wrong about ICAS

Dimitri Zet responds to AboutTheBSDs

Dimitri Zet's Blog - AboutTheBSDs is wrong about ICAS

As i noticed, there is a dude who criticises ICAS for being too proprietary-friendly and to "reimplement a new BSD system". I will prove his blog post wrong here. He says: "I recently read, that Apple got new fuel from ICAS, an open source project with a obviously proprietary-friendly license." What the heck is proprietary-friendly anyway? Do you mean permissive licensed or liberal licensed? Then, that dude prates: "ICAS was founded as a proprietary-friendly set of kernel building-blocks, kickstarted by proprietary software vendors such as Apple and Microsoft to gain new fuel for their proprietary products." Neigther Apple nor MS were fellow founders of ICAS. They joined later. YRU lying? And yes, it was foundet as a liberally licensed framework to be used in proprietary products. Anything wrong with this? That dude also waffles: "The network stack that they're released obviously was an former proprietary inhouse TCP/IP stack, but they should have kept it closed rather than offer it to Apple to incorporate." Oh, while being an open source seconder, you say: "Keep it proprietary, so apple cannot incorporate it!" F*ck'n Hypocrite! Other gases: "That new filesystem, 64fs, however is a cheap ext4 rip-off." Blatantly wrong. 64fs was designed from scratch, with focus on scalability and speed. Ext4 is just an ext2 FS with journaling layer, bigger block numbers and extends. 64fs doen't have those features, instead it has 64-block-adresses, WAL-Updates and Compression "They studied ext4 and wrote a broken remake in C++ and published it to Apple." They didn't study ext4 at all, in order to not accidentally copy its flaws. Also, 64fs is not broken. It is different from ext4 and it is better! Period. "The 'Anywhere Threading' technology is just a rip-off of Linux' kernel preemtion." Wrong, because 1. kernel preemtion wasn't invented by Linux, and 2. Anywhere-Threading was made in order to provide bare-metal applications with preemptive multithreading support. "Basically it looks like ICAS simply copys ideas from the Linux kernel and reimplements them to get rid of the GPL." Again meaningless slobbering and lies. "Maybe the Linux kernel developers can accuse the code, that is massively inspired by Linux as a 'derived work' and sue these Leeches." I don't think so. "As ICAS is not protected by the GPL, it will die soon. Until then, I will keep you up this news of these atrocities and thefts this project perceptrates." As ICAS is under the Apache License, it will Live and Grow. Why don't you look on the "atrocities and thefts" which the Apache Foundation "perceptrates", you punk**** moron?

[nasyt]

Phoronix - Camix 1.0 - the "Cambridge Unix"

Phoronix - Camix 1.0 - the "Cambridge Unix"

Some months after the Students of cambridge university, england, began their own unix based on the ICAS framework, their "Academic Cambridge Unix" attracted former BSD- and Illumos-Developers and grew very fast. Camix 1.0 is finally there. A notable feature is, that Camix implements the so called multi-identity model. As in the POSIX-model, a process can only and at least have one uid and one gid, in Camix, processes can have multiple uids and multiple gids. This was also used in order to implement an example RBAC-Policy. As Camix is currently just a Kernel, there is just a reference system, made of the camix kernel, the ICE-Libc and Busybox.

OSnews - "Independent *nix" gets renamed to Indyx

The a MPL 2.0 Licensed got renamed to Indyx. The project's current version is 0.5. It is the first OS to incorporate the standalone TCP/IP stack "HTN.i-tcpip". Matt Dillon initiated the jump to the name Indyx in order to push the popularity of this OS. On the past OSCon he gave a talk about the new project Indyx. Currently Indyx implements a fairly complete POSIX-like Operating System kernel, that supports kernel polling through a kqueue compatible API, called "kpoll". It also supports the AIO API. A new API has also been developed: IOQ - a scalable AIO- and polling-replacement. The Kernel-API-Headers for these subsystems are distributed under the MIT-license in order to ease the adoption of the api in other OSes.

[nasyt]

Distrowatch news - OpenPhoenix - the first full-featured Camix distro

Distrowatch news - OpenPhoenix - the first full-featured Camix distro

Two months after the release of Camix 1.0, OpenPhoenix is the first true Camix distribution. OpenPhoenix uses the "base-system"-model, wich means, that the OS consists of a base system and a set of packages wich are seperated from each other. The main target of OpenPhoenix are Servers. It uses the Illumos userland - a true open source descent of SVR4's (System V Release 4) userland - to give the user a true unix user experience. Moreso it uses runit as its Init-System with asl-scripts in place of shell scripts. Asl is a new small language, developed as a lightweight and secure shellscript replacement. OpenPhoenix uses the RPM package manager together with a custom apt-like frontend tool, called RIT (RPM Install Tool). The OpenPhoenix project will also offer it's base-system for people who want to build their own ulSVR4/Camix-Distribution atop a base-system.

[Luke_Wolf]

*snip*

Now this is one fanfic I'm actually enjoying.

[nasyt]

OSnews - Indyx 0.9 - "Free, Fast and Secure"

OSnews - Indyx 0.9 - "Free, Fast and Secure"

The Indyx Operating system has developing an implementation of Camix' multi-identity model along with some Camix' security mechanisms. As Camix is Apache-licensed, Indyx possibly could have taken parts of Camix' source code, but Camix is written in C++ while Indyx is written in C, with the exception of the Vfs and Bdi framework. At the same time the Indyx-project has pushed a C++ reimplementation of IOQ and kpoll to Camix. Dimitri: "Since Camix and Indyx are written in different languages, colaboration isn't easy. But since Camix is the 'open source friend' of Indyx, we invest this effort."

[nasyt]

Slashdot news - Camix 1.2 : Improvements in manageability and IO scalability

Slashdot news - Camix 1.2 : Improvements in manageability and IO scalability

The recent Camix 1.2 update came up with new Non-Blocking IO subsystems, namely IOQ and kpoll. These features have been emerged from the colaboration with the Indyx project, another open source Unix. Camix also incubated a new Process management and tracking subsystem called "pgroups", wich is inspired by Linux' "cgroups" and will improve the ability to manage daemons: pgroups will keep track of every child process, a specific daemon makes. An OS container primitive has also been implemented, wich allows multiple isolated unix-enviromnents to run simultanously on the same kernel. The Camix maintainers will push the pgroups specification to Indyx.

Phoronix - Xv6-forked OS-Kernel Indyx becomes STABLE

The Indyx project released version 1.0 of its kernel. New features include pgroups as well as many small bugfixes. Other features include a largely lock-free architecture with fine grained locking where unavoidable and where lock-free algorithms would't be efficient. Indyx was started as "Independent *nix" as a fork of a xv6, a MIT-remake of the original research unix v6 from bell labs.

[nasyt]

Now this is one fanfic I'm actually enjoying.

I am pleased.

I hope, that this thread also gets noticed from endman, Pawl and so on.

[nasyt]

Distrowatch news - ZevourPhoenix, a new ulSVR4/Camix distribution

Distrowatch news - ZevourPhoenix, a new ulSVR4/Camix distribution

ZevourPhoenix is a new Camix Distribution, based on the OpenPhoenix Base-System. ZevourPhoenix uses the XBPS package system instead of the RPM package manager. The goal is to improve the OpenPhoenix-system by using a faster, more robust package management.

Phoronix - OpenPhoenix developers release SystemE, a "systemd-emulator" for Camix

OpenPhoenix devs have written "systemE", a "systemd-emulator" for unix-like OSes like Camix or Indyx. SystemE will be used in order to run server software, that requires systemd. According to OpenPhoenix leader, Dave Magge, systemE will lower the barrier to entry of other Unixoid operating systems, making them more usable and rich of software. Moreso, systemE could give the software developers the opportunity to write software in a more cross-plattform way.