Language Selection

English French German Italian Portuguese Spanish

One Linux to rule them all

There is a whole lot of noise being made about Googles OS announcement.

Most of it being made by raving distro fanboys who believe that by pledging their allegiance to one distro will make part of the 'cool crowd'

"No thanks Google, we have Ubuntu/Debian/Gentoo/pick one"

At the same time, everyone is crying that it is an example of Linux becoming 'more fragmented'. Just one more of the too many distros available.

First of all, what the raving fanboys and the fragmented wailers are forgetting is that Linux supersedes all of these things.

Linux is not an OS of only one image. It is not an OS to be dictated by one company or person.

To spell it out, GNU/Linux is not just 'an' OS, it's 'my' OS. it's 'your' OS. It's a promise of sorts that says this OS is here to work the way you want it to work, not the way someone else wants it to work.

The number of versions of GNU/Linux out there shouldn't be seen as an 'over-proliferation' or as fragmentation of the whole thing either. They are 'presentations' of just what can be done by many different people with one 'open' OS.

The beauty of GNU/Linux is that so many versions of it can be presented for so many different usage environments. If anything, what GNU/Linux needs is to better clarify what those examples are and provide better directions to 'types' of existing presentations of Linux for different types of users.

For example, If you are looking for examples of 'Home Desktops' in GNU/Linux, look at these on the left (see the pretend list of Home desktop distros compiled there), on the right, there are the Business Workstation presentations (see similar pretend compiled list).

On top, is our list of 'generic' Linux distros from which you can customize yourself split into 'binary' and 'source-based' versions (see pretend list of distros like Debian, CentOS, fedora, OpenSuse, Gentoo, Arch, LFS and so on...)

Googles advance into the Linux-based distro is just another example of how Linux can be modified for a specific, targeted market. I firmly believe it will be designed to support web based applications and usage and therefore is another exciting example of GNU/Linux displaying it's flexibility.

It's all good. Relax

More in Tux Machines

Android Leftovers

Heroku Review apps available for Treeherder

In bug 1566207 I added support for Heroku Review Apps (link to official docs). This feature allows creating a full Treeherder deployment (backend, frontend and data ingestion pipeline) for a pull request. This gives Treeherder engineers the ability to have their own deployment without having to compete over the Treeherder prototype app (a shared deployment). This is important as the number of engineers and contributors increases. Once created you get a complete Heroku environment with add-ons and workers configured and the deployment for it. Looking back, there are few new features that came out of the work, however, Heroku Review apps are not used as widely as I would have hoped for. Read more

Linux-driven RISC-V core to debut on an NXP i.MX SoC

The OpenHW Group unveiled a Linux-driven “CORE-V Chassis” eval SoC due for tape-out in 2H 2020 based on an NXP i.MX SoC, but featuring its RISC-V-and PULP-based 64-bit, 1.5GHz CV64A CPU and 32-bit CV32E cores. Meanwhile, Think Silicon demonstrated a RISC-V-based NEOX|V GPU. A not-for-profit, open source RISC-V initiative called the OpenHW Group that launched in June has announced that it plans to tape out a Linux-friendly CORE-V Chassis evaluation SoC in the second half of 2020 built around its 64-bit CV64A CPU core and 32-bit CV32E coprocessor. The RISC-V based cores will be integrated into an undefined, NXP i.MX heterogeneous, multi-core SoC design. The SoC was announced at this week’s RISC-V Summit in San Jose, Calif., where Think Silicon also demo’d an early version of a RISC-V-based NEOX|V GPU (see farther below). The open source CV64A CPU core and 32-bit CV32E are based on RISC-V architecture PULP Platform cores developed by the University of ETH Zurich. The 64-bit CV64A core is based on ETH Zurich’s Ariane implementation of its RV64GC RISC-V core IP. RV64GC is also used by many other RISC-V projects, including SiFive’s U54. Read more

today's howtos and leftovers