Language Selection

English French German Italian Portuguese Spanish

Stable Kernels: 5.7.11, 5.4.54, 4.19.135, and 4.14.190

Filed under
Linux
  • Linux 5.7.11

    I'm announcing the release of the 5.7.11 kernel.

    All users of the 5.7 kernel series must upgrade.

    The updated 5.7.y git tree can be found at:
    git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.7.y
    and can be browsed at the normal kernel.org git web browser:
    https://git.kernel.org/?p=linux/kernel/git/stable/linux-s...

  • Linux 5.4.54
  • Linux 4.19.135
  • Linux 4.14.190

More in Tux Machines

Games Leftovers

  • Gaming Like It's 1925: Last Week To Join The Public Domain Game Jam!

    Sign up for the Public Domain Game Jam on itch.io »

  • ujoy(4) added to -current

    With the following commit, Thomas Frohwein (thfr@) added a joystick/gamecontroller driver to -current: [...]

  • The First Online Conference Is Happening Today For The Godot Game Engine - Phoronix

    For those interested in Godot as the premiere open-source 2D/3D game engine or just looking for some interesting technical talks to enjoy this weekend, the first GodotCon Online is today. GodotCon 2021 is the open-source game engine's first entirely online conference for developers, users, and other contributors to this promising open-source project. The YouTube-based event has been running from 8:45 UTC today until 16:00 UTC, but fear not if you missed out as you can already go back and listen to the prior talks in the stream. The recordings will remain available for those wanting to enjoy it in the days ahead. All of the content is free of charge.

Programming Leftovers

  • How to test PHP code using PHPUnit - Anto ./ Online

    PHPUnit automatically executable tests that verify your application’s behavior. Thus – you can ensure that your changes don’t break existing functionality. This post will show you how to test your PHP code using PHPUnit.

  • Latency Numbers Every Team Should Know

    We design systems around the size of delays that are expected. You may have seen the popular table “latency numbers every programmer should know” which lists some delays that are significant in technology systems we build. Teams are systems too. Delays in operations that teams need to perform regularly are significant to their effectiveness. We should know what they are. Ssh to a server on the other side of the world and you will feel frustration; delay in the feedback loop from keypress to that character displayed on the screen. Here’s some important feedback loops for a team, with feasible delays. I’d consider these delays tolerable by a team doing their best work (in contexts I’ve worked in). Some teams can do better, lots do worse. [...] In recent times you may have experienced the challenge of having conversations over video links with significant delays. This is even harder when the delay is variable. It’s hard to avoid talking over each other. Similarly, it’s pretty bad if we know it’s going to take all day to deploy a change to production. But it’s so worse if we think we can do it in 10 minutes, when it actually ends up taking all day. Flaky deployment checks, environment problems, change conflicts create unpredictable delays. It’s hard to get anything done when we don’t know what to expect. Like trying to hold a video conversation with someone on a train that’s passing through the occasional tunnel.

  • How I programmed a virtual gift exchange

    Every year, my wife's book club has a book exchange during the holidays. Due to the need to maintain physical distance in 2020, I created an online gift exchange for them to use during a book club videoconference. Apparently, the virtual book exchange worked out (at least, I received kind compliments from the book club members), so I decided to share this simple little hack.

  • Dirk Eddelbuettel: prrd 0.0.4: More tweaks

    The key idea of prrd is simple, and described in some more detail on its webpage and its GitHub repo. Reverse dependency checks are an important part of package development that is easily done in a (serial) loop. But these checks are also generally embarassingly parallel as there is no or little interdependency between them (besides maybe shared build depedencies). See the (dated) screenshot (running six parallel workers, arranged in split byobu session). This release brings several smaller tweaks and improvements to the summary report that had accumulated in my use since the last release last April. We also updated the CI runners as one does these days.

  • vrurg: A New Release Of Cro::RPC::JSON

    I don’t usually announce regular releases of my modules. But not this time. I start this new year with the new v0.1 branch of Cro::RPC::JSON. Version 0.1.1 is currently available on CPAN (will likely be replaced with fez as soon as it is ready). The release is a result of so extensive changes in the module that I had to bump its :api version to 2.

  • gfldex: Anonymous slurpers

    I have a script where I’m only interested in the last two lines of its output.

Nouveau X.Org Driver Sees First Release In Two Years

Two years and nine patches later, xf86-video-nouveau 1.0.17 is out as the latest X.Org driver update for this open-source NVIDIA driver component. Like the other DDX drivers with the exception of the generic xf86-video-modesetting driver that is quite common now to those still running on X.Org with the open-source stack, xf86-video-nouveau seldom sees new activity. Since the prior v1.0.16 release two years ago there has been less than a dozen patches for it. The interesting activity happens in DRM/KMS kernel space and an increasing number of users are just relying upon xf86-video-modesetting over these hardware-specific X.Org user-space drivers. Read more

KDE Goals – a year lost, a year gained

The year 2020 was difficult in many ways, but it also was important for me: I joined KDE e.V. as a consultant in the role of Project Coordinator. One of the main focuses of mine was supporting the KDE Goals initiative, which resulted in creating a formalized process. As you might know (or read in the process), the KDE Goals are to be replaced roughly every two years. This timebox was selected to balance keeping the Goals fresh, and letting the Goal Champions have enough time to work on the topics with the community. Read more Also: GNOME 40's Mutter Adds Atomic Mode-Setting Support