Language Selection

English French German Italian Portuguese Spanish

Linus

He's a god!
61% (643 votes)
bit too arrogant
16% (169 votes)
just a potty mouth
8% (80 votes)
can be abusive
10% (103 votes)
shouldn't be allowed out
5% (53 votes)
Total votes: 1048

More in Tux Machines

FUD, EEE, and Openwashing

Kubernetes News

  • When Does Kubernetes Become Invisible And Ubiquitous?
    The sign of a mature technology is not just how pervasive it is, but in how invisible and easy to use it is. No one thinks about wall sockets any more – unless you happen to need one to charge your phone and can’t find one – and that is but one example of a slew of technologies that are part of every day life. Since Google first open sourced the Kubernetes container controller, inspired by its Borg and Omega internal cluster and container management systems, more than four years ago, we have been betting that it would become the dominant way of managing containers on clouds both public and private. The irony is that the people in charge of Google’s infrastructure were not initially all that enthusiastic in giving away such intellectual property, but the Kubernetes and open source enthusiasts correctly predicted that Google would get tremendous cred with the open source community and help create a Google-alike containerized private cloud environment and also possibly spread Google’s approach to rival clouds as well as helping its own Cloud Platform expansion by giving Kubernetes to the world.
  • Crictl Vs Podman
    As people continue to adopt CRI-O as a new container runtime for Kubernetes I am hearing questions from administrators who are confused whether they should use Crictl or Podman to diagnose and understand what is going on in a Kubernetes node. This is not one or the other — these tools are complementary, and this article attempts to explain the tools and examine when it is best to use each of these tools. If you take away one thing from this post, remember that Crictl checks the front entrance, while Podman examines the foundation. First things first. For those people who aren’t familiar with it, CRI-O is a lightweight, Open Container Initiative (OCI) compliant, container runtime for Kubernetes. It is designed to run any OCI-based container, it is optimized for Kubernetes and committed to being stable and conformant with the Kubernetes container runtime interface with each Kubernetes release. CRI-O is also now fully supported in OpenShift, Red Hat’s enterprise Kubernetes container platform. For more information on CRI-O check out the CRI-O community web site and blog.
  • BlueData Announces BlueK8s Open Source Kubernetes Initiative
    Kubernetes (aka K8s) is now the de facto standard for container orchestration. Kubernetes adoption is accelerating for stateless applications and microservices, and the community is beginning to evolve and mature the capabilities required for stateful applications. But large-scale distributed stateful applications – including analytics, data science, machine learning (ML), and deep learning (DL) applications for AI and Big Data use cases – are still complex and challenging to deploy with Kubernetes.

RPM And Yum Are A Big Deal For IBM i. Here’s Why

By now you’ve probably heard about Yum and RPM, the new processes that IBM will use to deliver open source software to IBM i customers. But you may have questions about how the process works, and what the benefits will be. IT Jungle talked with IBM’s open source guru Jesse Gorzinski to get the low down on why the new tech is so important to the platform. RPM, which stands for Red Hat Package Manager, is a piece of software created more than 20 years that allows customers in that Linux community to more easily distribute and install the various pieces of software required to create a working Linux environment. Over the years, RPM use has migrated beyond the Red Hat community to other Linux and Unix environments (including AIX), and has essentially become a de facto standard for distributing software in the open source world. Read more Also: Red Hat Announces Ansible Engine 2.6 with Simplified Connections to Network APIs and Automation across Windows & Cloud

New Facilities for System76

  • System76 Linux computer maker offers a sneak peek into its new manufacturing facility
    System76 has long been a Linux computer seller, but recently, it has transitioned into a Linux computer maker. What's the difference, you ask? Well, currently, the company doesn't really make its own computers. System76's laptops, for instance, are made by other manufacturers, which it re-brands as its own. No, System76 doesn't just slap its name on other company's laptops and ship them out the door. Actually, it works closely with the manufacturers, tweaks firmware, and verifies that both Ubuntu and its Ubuntu-based Pop!_OS will work well on the hardware. System76 then offers top-notch support too. In other words, the company isn't just selling a computer, but an experience too.
  • System76 New Manufacturing Facility
  • System76 Moves Ahead With Preparing To Manufacture Their Own Desktop Linux PCs
    Back in April 2017 was the announcement that System76 would begin designing and manufacturing their own systems beginning with desktops and to be followed at a later date by their own laptops, rather than relying upon whitebox designs that they currently retail with their Ubuntu/Pop!_OS-loaded PCs. The Colorado-based company is inching closer to fully realizing their goal. For a while now the System76 folks have been posting various pictures of their in-progress manufacturing facility while today they have shared more images on their blog.