Language Selection

English French German Italian Portuguese Spanish

Linux 5.0 RC1

Filed under
Linux
  • Linux 5.0-rc1

    So this was a fairly unusual merge window with the holidays, and as a
    result I'm not even going to complain about the pull requests that
    ended up coming in late. It all mostly worked out fine, I think. And
    lot of people got their pull requests in early, and hopefully had a
    calm holiday season. Thanks again to everybody.

    The numbering change is not indicative of anything special. If you
    want to have an official reason, it's that I ran out of fingers and
    toes to count on, so 4.21 became 5.0. There's no nice git object
    numerology this time (we're _about_ 6.5M objects in the git repo), and
    there isn't any major particular feature that made for the release
    numbering either. Of course, depending on your particular interests,
    some people might well find a feature _they_ like so much that they
    think it can do as a reason for incrementing the major number.

    So go wild. Make up your own reason for why it's 5.0.

    Because as usual, there's a lot of changes in there. Not because this
    merge window was particularly big - but even our smaller merge windows
    aren't exactly small. It's a very solid and average merge window with
    just under 11k commits (or about 11.5k if you count merges).

    The stats look fairly normal. About 50% is drivers, 20% is
    architecture updates, 10% is tooling, and the remaining 20% is all
    over (documentation, networking, filesystems, header file updates,
    core kernel code..). Nothing particular stands out, although I do like
    seeing how some ancient drivers are getting put out to pasture
    (*cought*isdn*cough*).

    As usual even the shortlog is much too big to post, so the summary
    below is only a list of the pull requests I merged.

    Go test. Kick the tires. Be the first kid on your block running a 5.0
    pre-release kernel.

    Linus

  • Linux 5.0-rc1 Debuts With New Hardware Support, FreeSync, I3C, High-Res Scrolling

    Linus Torvalds ended the Linux 4.21 merge window on Sunday evening and decided to go ahead and rename it to Linux 5.0. Linux 5.0-rc1 is now available to begin the testing process for this next kernel release that will officially debut around the end of February or early March.

    A short time ago I posted our Linux 5.0 feature overview that covers the major highlights of this new kernel release. See that two-page article for all of the details but some of the highlights include: AMD FreeSync, Raspberry Pi Touchscreen driver, a new console font for HiDPI/retina displays, initial open-source NVIDIA RTX Turing support with Nouveau, Adiantum data encryption support, Logitech high resolution scrolling support, I3C subsystem, and a lot of other new hardware support. The decision to jump over to Linux 5.0 from Linux 4.21 was decided by Linus Torvalds with the 4.x kernel releases getting high, similar to the arbitrary move of re-branding Linux 3.20 to Linux 4.0.

Linux 5 is on the way

  • Linux 5 is on the way

    In his Linux Kernel Mailing List (LKML) post, Torvalds wrote, "The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0."

    Surely, there's more to it than that. Right? Nope.

    Torvalds went on, "Go wild. Make up your own reason for why it's 5.0."

"Linux 5.0-rc1 Released"

  • Linux 5.0-rc1 Released, Scratch 3 and Raspberry Pi, Phoronix Test Suite 8.6-Spydeberg Milestone 1 Is Now Available, Elteria Adventures Coming to Linux and Chromium Now Supports VAAPI in Fedora

    Linux 5.0-rc1 was released yesterday. Linus Torvalds wrote: "The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0. There's no nice git object numerology this time (we're _about_ 6.5M objects in the git repo), and there isn't any major particular feature that made for the release numbering either. Of course, depending on your particular interests, some people might well find a feature _they_ like so much that they think it can do as a reason for incrementing the major number. So go wild. Make up your own reason for why it's 5.0."

  • Linux Kernel 4.2

    A few weeks ago, in the final days leading up to Christmas, Linus Torvalds released version 4.20 of the Linux Kernel. Collaborans were once again active during this development cycle, contributing 22 patches, 112 reviews & 55 sign-offs. Below is a summary of their contributions. As is the custom, head to LWN.net if you would like to read more about the merge window for 4.20 (part 1 & part 2).

Linux reaches the big five (point) oh

  • Linux reaches the big five (point) oh

    Penguinistas, take heed. The kernel of your beloved OS has rung in the new year with a brand spanking new version number because... Linus felt like it.

    Linux fans will be relieved to know that while 2019 should feature a gentler, softer and less sweary Torvalds, the man's ability to make arbitrary decisions remains undiminished. The reason version 4.21 became 5.0 is because "I ran out of fingers and toes to count on."

Linus Torvalds Finally Kicks Off Development of Linux 5.0

  • Linus Torvalds Finally Kicks Off Development of Linux 5.0, Coming March 2019

    After a long wait, we will finally be able to run the long-anticipated Linux 5.0 kernel on our Linux-powered computers as Linus Torvalds kicked off 2019 with the development cycle of Linux kernel 5.0.

    While not a special release, like many of you out there would have expected from such major milestone, Linux kernel 5.0 is coming in a few months to the stable repositories of your favorite GNU/Linux distribution with updated and new drivers, architecture and tooling updates, as well as various improvements to networking, filesystems, documentation, and core kernel code.

    "The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and toes to count on, so 4.21 became 5.0. There's no nice git object numerology this time (we're _about_ 6.5M objects in the git repo), and there isn't any major particular feature that made for the release numbering either," said Linus Torvalds.

Linus Torvalds Welcomes 2019 with Linux 5.x

  • Linus Torvalds Welcomes 2019 with Linux 5.x

    Linus Torvalds has announced the release of Linux 5.0-rc1. The kernel was supposed to be 4.21, but he decided to move to the 5.x series. Torvalds has made it clear that the numbering of the kernel doesn’t make much sense. So don’t get too excited about this release.

    Torvalds explained in the LKML (Linux Kernel Mailing List), “The numbering change is not indicative of anything special. If you want to have an official reason, it's that I ran out of fingers and numerology this time (we're _about_ 6.5M objects in the git repo), and there isn't any major particular feature that made for the release numbering either,” he said.

By Chris Merriman 5 days late

  • Linux 5.0 lands with added Nvidia Turing RTX, AMD FreeSync support

    LINUX HAS been updated to a brand new version number, something that creates more excitement in users than in Linus Torvald's mind.

    Linux 5.0 has hit rc1, meaning that within weeks (roughly seven or eight), it will be the stable kernel for the various operating systems that depend on it.

    Despite the renumbering being as arbitrary as ever (he's been thinking of changing this for the last four versions) there are actually a whole bunch of new features to talk about.

    AMD FreeSync and Raspberry Pi touchscreen support have been added, there's early support for the Nvidia RTX Turing GPUs, and Logitech's high-resolution scrolling from its high-end mice.

Linux 5.0 Is Finally Arriving In March

  • Linux 5.0 Is Finally Arriving In March

    With last week’s release of Linux 5.0-rc1, it’s confirmed that Linus Torvalds has finally decided to adopt the 5.x series.

    The kernel enthusiasts and developers have been waiting for this change since the release of Linux 4.17. Back then, Linus Torvalds hinted at the possibility of the jump to place after 4.20 release.

Linux kernel 5.0 RC1 is available with ARM big.LITTLE

  • Linux kernel 5.0 RC1 is available with ARM big.LITTLE EAS support, F2FS fixes, and much more

    While we don’t typically cover what happens in the mainline Linux kernel realm, it’s important for us to keep track of what’s going on with each new kernel release since Google mandates a minimum Linux kernel version requirement with each new release of Android. The recent decision to extend LTS releases from 2 to 6 years will play a major role in reducing security patch fragmentation since device makers will have to do less work in backporting security patches. Plus, the mainline kernel does often integrate new features that are relevant to mobile devices.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Reducing sysadmin toil with Kubernetes controllers

Kubernetes is a platform for reducing toil cunningly disguised as a platform for running containers. The element that allows for both running containers and reducing toil is the Kubernetes concept of a Controller. [...] The canonical example of this in action is in how we manage Pods in Kubernetes. A Pod is effectively a running copy of an application that a specific worker node is asked to run. If that application crashes, the kubelet running on that node will start it again. However, if that node crashes, the Pod is not recovered, as the control loop (via the kubelet process) responsible for the resource no longer exists. To make applications more resilient, Kubernetes has the ReplicaSet controller. The ReplicaSet controller is bundled inside the Kubernetes controller-manager, which runs on the Kubernetes master node and contains the controllers for these more advanced resources. The ReplicaSet controller is responsible for ensuring that a set number of copies of your application is always running. To do this, the ReplicaSet controller requests that a given number of Pods is created. It then routinely checks that the correct number of Pods is still running and will request more Pods or destroy existing Pods to do so. By requesting a ReplicaSet from Kubernetes, you get a self-healing deployment of your application. You can further add lifecycle management to your workload by requesting a Deployment, which is a controller that manages ReplicaSets and provides rolling upgrades by managing multiple versions of your application's ReplicaSets. Read more

Android Leftovers

Server: IBM, LAMP and Kubernetes

  • A HATS For Many Occasions
    IBM gives customers plenty of options when it comes to its Rational Host Access Transformation software, including several modes of operation, different runtime options, and support for different operating systems in screen modernization engagements. With last week’s launch of HATS version 9.7, the development and deployment options got even wider. Regardless of which downstream options a HATS customer ultimately chooses, it all starts out basically the same on the front side of the sausage machine: Customers come to HATS because they have a 5250 (or 3270 or VT100) application that they want to transform, but they don’t want to go through the hassle, expense, and risk of modifying the IBM i, z/OS, or Unix application’s source code.
  • Six top skills that you should acquire in 2019
    There is a growing demand for the fullstack development skill set, which is the ability to develop tech both on the front-end/client side and back-end/server side. As you can’t learn all, select combinations like MEAN or LAMP stack.
  • Kubernetes and the Enterprise
    The reason we were having this conversation was around SUSE’s Cloud Application Platform (CAP). This is our Kubernetes focused Cloud Foundry distribution. And as part of the Kubernetes focus, we have been supporting and running SUSE CAP on Azure’s AKS for the last year or so. The conversation continued with observations that Kubernetes was clearly the future across IT. Yet to date, Cloud Foundry still has a good following with the large enterprise. And the thinking was that the Cloud Foundry approach really helped the large enteprise work with their applications, even if the applications were purely ‘container’ applications. Cloud Foundry makes the container-side of managing your ‘container’ application transparent. This approach ultimately lowers the tasks, breadth of tooling, and knowledge you have to surround Kubernetes with. It was with this thought, that a light-bulb went on.

today's howtos