Language Selection

English French German Italian Portuguese Spanish

About Tux Machines

Monday, 03 Aug 20 - Tux Machines is a community-driven public service/news site which has been around for over a decade and a half and primarily focuses on GNU/LinuxSubscribe now Syndicate content

Search This Site

Quick Roundup

Typesort icon Title Author Replies Last Post
goblinxfc srlinuxx 26/04/2007 - 6:30pm
nixsys.com srlinuxx 24/09/2007 - 11:24pm
wolvixondisk srlinuxx 02/10/2007 - 10:49pm
arnybw srlinuxx 18/10/2007 - 3:39pm
webpathinlovelinux srlinuxx 07/02/2008 - 3:44pm
bluewhite srlinuxx 25/03/2008 - 10:44pm
pclos srlinuxx 15/06/2008 - 11:18pm
nixsys2 srlinuxx 18/08/2008 - 7:12am
nixsys3 srlinuxx 18/08/2008 - 7:22am
gg 480x60 srlinuxx 03/09/2008 - 11:55am

Kernel: Unicore32 and IO_uring in Linux

Filed under
Linux

  • Linux 5.9 Dropping The Unicore 32-bit RISC Architecture

    It's arguably long overdue but with the just-opened Linux 5.9 kernel cycle the Unicore32 CPU architecture is being removed. 

    Unicore is a 32-bit RISC architecture developed at China's Peking University. Unicore is an ARM-like architecture. But with Unicore not being too popular and this code not seeing any maintenance for the mainline kernel paired with no upstream compiler support, it's time to gut the code out of the kernel. 

  • IO_uring Has Many Improvements Set To Go Into Linux 5.9

    Facebook's Jens Axboe who oversees the Linux storage/block code and leads the IO_uring efforts summed up the changes for Linux 5.9 as "hardening the code and/or making it easier to read and fixing [bits]." There is though a big change and that is proper async buffered reads support. That work was previously covered but didn't end up getting pulled into Linux 5.8 due to a branching difference but is now ready to go with Linux 5.9. The async buffered reads support for IO_uring has some nice performance advantages and lower CPU usage while also working its way off KThreads for the fast code path once the async buffered write support is in place. 

Why I use Ingress Controllers to expose Kubernetes services

Filed under
Server

The meteoric rise of containerization and microservices has been necessary to meet the growing demand for applications, but getting it right means overcoming some critical network orchestration challenges. Out of the complexities that developers of cloud-native applications face, strategically utilizing Kubernetes ingress controllers is among the most difficult components to understand—and among the most important.

Before diving into ingress controllers, you need to understand why networking is so important to developer workflows.

It is common for development teams to create backend API services to enable connectivity for external applications and users. In early development phases, teams often use implementations of container environments on local development machines, which more simply rely on direct container invocations through Docker Compose or similar local orchestrators for access.

However, when the time comes to shift to a shared development or staging environment and match the configuration that will be used in production, these direct-access stopgaps are no longer sufficient. The access patterns often assume trusted access, which can't be assumed in production, or they rely on static values that are likely to change in a cloud infrastructure.

Read more

libinput 1.16.0

Filed under
Graphics/Benchmarks
Linux

libinput 1.16.0 is now available.

No significant changes since the second RC, so here's slightly polished RC1
announcement text.

This has been a long cycle, mostly because there weren't any huge changes on
the main development branch and a lot of the minor annoyances have found
their way into the 1.15.x releases anyway.

libinput now monitors timestamps of the events vs the current time when
libinput_dispatch() is called by the compositor. Where the difference
*may* result in issues, a (rate-limited) warning is printed to the log.
So you may see messages popping up in the form of
  "event processing lagging behind by XYZms, your system is too slow"
This is a warning only and has no immediate effect. Previously we would only
notice (and warn about) this when it affected an internal timer. Note that
these warnings do not show an issue with libinput, it shows that the the
compositor is not calling libinput_dispatch() quick enough.

The wheel tilt axis source was deprecated. No device ever had the required
udev properties set so we should stop pretending we support this.

Touchpads now support the "flat" acceleration profile. The default remains
unchanged and this needs to be selected in the configuration interface. The
"flat" profile applies a constant factor to movement deltas (1.0 for the
default speed setting).

Events from lid or tablet-mode switches that are known to libinput as being
unreliable are now filtered and no longer passed to the caller.
This prevents callers from receiving those known-bogus events and having to
replicate the same heuristics to identify unreliable devices that libinput
employs internally.

A new "libinput analyze" debugging tool is the entry tool for analysing
various aspects of devices. Right now the only tool is
"libinput analyze per-slot-delta" which can be used to detect pointer jumps
in a libiput record output. This tool used to live elsewhere, it was moved
to libinput so that reporters can easier run this tool, reducing the load on
the maintainers.

The tools have seen a few minor improvements, e.g.
- "libinput record touchpad.yml" does the right thing, no explicit --output
  argument required
- libinput measure touchpad-pressure has been revamped to be a bit more
  obvious
- libinput measure touchpad-size has been added (as replacement for the
  touchpad-edge-detector tool)
- libinput measure fuzz has been fixed to work (again and) slightly more
  reliable

The libinput test suite has been fixed to avoid interference with the
currently running session. Previously it was virtually impossible to work
while the test suite is running - multiple windows would pop up, the screen
would blank regularly, etc.

And of course a collection of fixes, quirks and new bugs.

As usual, see the git shortlog for details.

Diego Abad A (1):
      FIX: typo on building documentation

Peter Hutterer (2):
      test: semi-fix the switch_suspend_with_touchpad test
      libinput 1.16.0

git tag: 1.16.0

Read more

Also: >Libinput 1.16 Released - Ready To Warn You If Your System Is Too Slow

18 Frameworks, Libraries, and Projects for Building Medical Applications

Filed under
OSS

Open-source is not just a license or a code-based that left free on an online repository, It's a complete concept which comes with several advantages. Moreover, the most advantage you can get from Open-source is beyond the open-code it's FREEDOM; freedom to use or re-shape it as you see fit within your project commercial or otherwise, and that depends on the license of course. You are free from the headache of license conflict legal problems but also from the dilemma of dealing with restrections and limitations which come with property licenses.

You are free from the system lock-in schemes, furthermore, you own your data, and freedom to customize the software as your structure requires and workflow demands.

The Community:

The Open-source project gains a powerful community as they gain users, the community users vary between advanced users, end-users, developers and end-users on decision-making level.

Many of the community users are providing quality inputs from their usage and customized use-case and workflow or test-runs, Furthermore, they always have something to add as new features, UI modification, different usability setup, and overall introducing new workflows and tools, and That's what makes the progress of the open-source different than non-free solutions.

While, Good community means good support, The community is a good resource to hire advanced users, developers, and system experts. It also provides alternative options when hiring developers. Unlike non-free software which are not blessed with such communities and where the options there are limited, The rich open-source community provides rich questions and answers sets that contributed by users from all around the world.

Higher education value for the in-house team

The open-source concept itself provides educational value, I owe most of what I know to open-source communities.The access to the source code and open-channels communication with the core developers is the best educational value any developer can get.

Read more

Python Programming

Filed under
Development

Journey of a Linux DevOps engineer

Filed under
GNU
Linux
Red Hat
Server

After navigating the streets of Manhattan and finding a parking spot, we walked down the block to what turned out to be a large bookstore. You've seen bookstores like this on TV and in the movies. It looks small from the outside, but once you walk in, the store is endless. Walls of books, sliding ladders, tables with books piled high—it was pretty incredible, especially for someone like me who also loves reading.

But in this particular store, there was something curious going on. One of the tables was surrounded by adults, awed and whispering among each other. Unsure of what was going on, we approached. After pushing through the crowd, I saw something that drew me in immediately. On the table, surrounded by books, was a small grey box—the Apple Macintosh. It was on, but no one dared approach it—no one, that is, except me. I was drawn like a magnet, immediately grokking that the small puck-like device moved the pointer on the screen. Adults gasped and murmured, but I ignored them all and delved into the unknown. The year was, I believe, 1984.

Somewhere around the same time, though likely a couple of years before, my father brought home a TI-99/4A computer. From what I remember, the TI had just been released, so this had to be somewhere around 1982. This machine served as the catalyst for my love of computer technology and was one of the first machines I ever cut code on.

My father tells a story about when I first started programming. He had been working on an inventory database, written from scratch, that he had built for his job. I would spend hours looking over his shoulder, absorbing everything I saw. One time, he finished coding, saved the code, and started typing the command to run his code ("RUN"). According to him, I stopped him with a comment that his code was going to fail. Ignoring me, as I was only five or six at the time, he ran the code, and, as I had predicted, it failed. He looked at me with awe, and I merely looked back and replied, "GOSUB but no RETURN."

Read more

Also: Authorizing multi-language microservices with Louketo Proxy

Linux Kernel 5.8 is Here. This is What's New

Filed under
GNU
Linux

A brand new Linux Kernel 5.8 is announced by Linus Torvalds. This kernel release is mostly a big release in terms of hardware, graphics, and other updates.
Read more

Review: Haiku R1 beta 2

Filed under
OS
OSS
Reviews

Haiku is an open-source operating system that specifically targets personal computing. Inspired by the Be Operating System (BeOS), Haiku aims to be fast, efficient, simple to use, and easy to learn. It is specifically geared toward desktop usage and maintaining a responsive desktop environment.

The Haiku project has been, to date, in perpetual development mode. Which is to say the releases to date have been labelled as being alpha or beta releases. I mention this because while the version label is R1 beta 2, the platform should probably be regarded a relatively mature project with the benefit of nearly 20 years of development behind it.

The R1 beta 2 release includes a number of new features such as improved font scaling and HiDPI support, along with the ability to work with mouse devices that offer more than three buttons. More applications have been ported and are now available through the project's software manager. The installer has mostly remained the same, however users can now exclude the installation of optional packages while setting up Haiku. New driver support has been added and there are some new options for keeping the Deskbar (a sort of combined desktop panel and system tray) out of the way.

The project's latest release is available in 32-bit (x86) and 64-bit (x86_64) builds. There are also builds for ARM, PowerPC, m68k, and SPARC architectures, however these builds are considered to be unsupported. I downloaded the 64-bit build which is available as a 955MB ZIP file. Unpacking the ZIP file presents us with a 1,108MB (1GB) ISO file we can write to optical media or a thumb drive.

Read more

Linux Kernel 5.8 “The Biggest Release of All Time” is Finally Available Now

Filed under
News

Linus Torvalds has called it “the biggest release of all time”. Check out what are the key changes in the recently released Linux Kernel 5.8.
Read more

Programming: Python, Perl, and GNOME/GTK

Filed under
Development

           

  • Why proactively clean Python 2 up?

    It seems a recurring complaint that we’re too aggressive on cleaning Python 2 up from packages. Why remove it if (package’s) upstream still supports py2? Why remove it when it still works? Why remove it when somebody’s ready to put some work to keep it working?

    I’m pretty sure that you’re aware that Python 2 has finally reached its end-of-life. It’s past its last release, and the current version is most likely vulnerable. We know we can’t remove it entirely just yet (but the clock is ticking!), so why remove its support here and there instead of keeping it some more?

    This is best explained on the example of dev-python/twisted — but dev-python/pillow is also quite similar. Twisted upstream removed support for Python 2 at version 20. This means that we ended up having to keep two versions of Twisted — 19 that still supports Python 2, and 20 that does not. What does that means for our users?

    Firstly, they can’t normally upgrade Twisted if at least one of its reverse dependencies supports Python 2 and is installed. What’s important is that the user does not have to meaningfully need or use Python 2 in that reverse dependency. It is entirely sufficient that it supports Python 2 and the user is using default PYTHON_TARGETS.

    Of course, you could argue that changing the default PYTHON_TARGETS would resolve the problem without having to proactively remove Python 2 from Twisted revdeps. Today, I’m not sure which of the two options is better. However, back when cleanup started changing default PT would involve a lot of pain for the users. We’d have to reenable 2.7 via package.use for many packages (but which ones?) or the users would have to reenable it themselves. But that’s really tangential now.

  •        

  • Python Bytes: #192 Calculations by hand, but in the compter, with Handcalcs

    Idea by Guido van Rossum to bring back the print statement.

  •        

  • PyDev 7.7.0 released (mypy integration improvements, namespace packages)

    This release brings multiple improvements for dealing with type hints as well as improvements in the Mypy integration in PyDev:

    The MYPYPATH can now be set automatically to the source folders set on PyDev and the --follow-imports flag is set to silent by default (this flag is required because only one file is analyzed at a time in PyDev as failing to do so would end up showing errors for other files).

  •        

  • PSF GSoC students blogs: Weekly Check-in #10
  • PSF GSoC students blogs: Weekly Check-In: Week 10
  • Perl Weekly Challenge 71: Peak Elements and Trim Linked List
  • The Perl Weekly Challenge #071

    With another Linked List related task, I am now enjoying it a lot. It also gives me the opportunity to work with Class in Raku. Learning Raku has changed my thinking a big way. The developer inside me is more organised than before. Also doing regular weekly challenge made me think from unit test point of view every time I come up with a solution. In fact, it dictates the design of my solution. Now with the regular Live Video Raku Reviews by Andrew Shitov gave me the insights of others Raku solutions. It is amazing how he break the code into pieces to make it easy to understand. No book can teach you that. You only learn from experience or watching video from Andrew Shitov.

    Running [The|Perl] Weekly Challenge also taught me how to manage my spare time. I use my spare time very carefully. Before I would jump to anything that excites me. Last few weeks, I have started playing with Swift programming language. I am enjoying the journey. Please checkout my Swift solution to the Task #1 of Peak Elements.

  • Mariana Pícolo: The Second milestone

    By discussing with my mentor how could the best approach be, I found out that the notifications were already grouped on the code level, but these groups were not being represented in the UI.

    In the code, there's a class named Source, which is responsible for the group. They handle the info's about the app that have sent us any notification and store them.

    There's also a class named Notification, that creates a single notification, with title, banner, and has optional parameters such as playing sounds etc.

    Each Source has an array property that contains its notification objects, which gives us the groups.

    [...]

    Lastly, I'd like to talk about GUADEC which this year was completely remote.

    This was my first talk at a conference, in a language that I'm not a native speaker. I want to thank my mentor and the GNOME community for creating a comfortable environment for the interns to talk about their projects.

DragonFlyBSD Pulls In AMD Temperature Driver, SMN Support From FreeBSD

Filed under
BSD

DragonFlyBSD has been generally working out well for AMD Zen systems sans a few motherboard specific woes, but now is getting even better thanks to importing some new drivers from FreeBSD.

Most exciting is the amdtemp driver now being imported from FreeBSD to DragonFlyBSD. This driver allows for temperature monitoring on AMD Family 0Fh, 10h, 11h, 12h, 14h, 15h, 16h, and 17h processors. The AMD Family 17h support covers Zen 1 as well as Zen 2, including the likes of Threadripper and EPYC.

Also imported from FreeBSD is the amdsmn driver. This driver is for the AMD System Management Network (SMN) support on AMD Zen systems.

Read more

BunsenLabs Linux Lithium Release Hits Stable After Two Years, Based on Debian Buster

Filed under
Debian

After more than two years in development, BunsenLabs Linux Lithium release has finally hit the stable channel today for this OpenBox-based and lightweight Debian GNU/Linux derivative, a continuation of the acclaimed CrunchBang Linux.

The BunsenLabs Team is proud to announce today the official release of BunsenLabs Lithium, a new major release based on the latest Debian GNU/Linux 10 “Buster” operating system series.

As expected, BunsenLabs Linux Lithium is packed with lots of goodies, including the ability to install the distribution on newer computers that use Secure Boot, a new look and feel featuring a brand-new dark theme with custom-colored Papirus icons by default, and more modularity for user to fully customize the distro to their needs.

For example, users can now replace the default Openbox window manager with another desktop environment and keep many of the settings, such as menu item, key bindings, and autostarted apps. Also, the BunsenLabs session now uses jgmenu by default and can coexist with a default Openbox or Xfce sessions.

[...]

The BunsenLabs Linux Lithium release is available for download right now from the official website as a 64-bit live ISO and a minimal, CD-sized 32-bit non-PAE version, which can be extended to full-size by installing the bunsen-meta-all or bunsen-meta-lite metapackages.

Read more

Direct: [STABLE RELEASE] BunsenLabs Lithium Official ISOs

Also: [Debian-Based SparkyLinux] July 2020 donation report

Linux 5.8 Released

Filed under
Linux

  • Linux 5.8
    So I considered making an rc8 all the way to the last minute, but
    decided it's not just worth waiting another week when there aren't any
    big looming worries around.
    
    Because despite the merge window having been very large, there really
    hasn't been anything scary going on in the release candidates. Yeah,
    we had some annoying noise with header file dependencies this week,
    but that's not a new annoyance, and it's also not the kind of subtle
    bug that keeps me up at night worrying about it.
    
    It did reinforce how nice it would be if we had some kind of tooling
    support to break nasty header file dependencies automatically, but if
    wishes were horses.. Maybe some day we'll have some kind of SAT-solver
    for symbol dependencies that can handle all our different
    architectures and configurations, but right now it's just a manual
    pain that occasionally bites us.
    
    Anyway..
    
    Aside from silly header file noise, the last week was mostly dominated
    by the networking pull, which accounts for about half of the changes
    (mellanox drivers and selftests stand out, but there's other smaller
    things in there too). Some RCU fixes stand out.
    
    Outside of the networking stuff, it's mostly various small driver
    fixes (gpu, rdma, sound and pinctrl being much of it), and some minor
    architecture noise (arm, x86, powerpc). But it's all fairly small.
    
    So there it is, a shiny new kernel. Give it a whirl before all you
    people start sending me the pull requests for the merge window, which
    I'll start handling tomorrow..
    
                     Linus
    
  • Linus Torvalds Officially Releases the Linux 5.8 Kernel, Now Available for Download

    The Linux 5.8 kernel series has been officially announced by Linus Torvalds.

    [...]

    You can download the Linux 5.8 kernel sources right now from the kernel.org website or using the direct link below. However, please keep in mind that this currently marked as a “mainline” kernel, which means it’s not yet ready for mass deployments or use in production environments.

    You should probably wait for the first point release, Linux kernel 5.8.1, to hit the streets before considering upgrading your kernel packages to the new series. Many of the rolling GNU/Linux distributions like Arch Linux or openSUSE Tumbleweed will probably upgrade to Linux 5.8 in the coming weeks.

  • Linux 5.8 Released With AMD Energy Driver, F2FS LZO-RLE, IBM POWER10 Booting

    Linus Torvalds was debating up to the last minutes today of whether to opt for Linux 5.8-rc8 or go ahead and release Linux 5.8 as stable... He opted for Linux 5.8 splashing down on this historic day.

    Linus wrote in the 5.8 release announcement that despite this cycle being very large, it turned out fairly well and didn't need a 5.8-rc8 release. Though due to some last minute changes, he does dream of having a sort of SAT-solver for symbol dependencies that would work across architectures and configurations for cleaning up the Linux kernel header file dependency mess. But that for now is just a dream.

  • The 5.8 kernel is out

    Linus has released the 5.8 kernel. "So I considered making an rc8 all the way to the last minute, but decided it's not just worth waiting another week when there aren't any big looming worries around." Headline features in this release include: branch target identification and shadow call stacks for the arm64 architecture, the BPF iterator mechanism, inline encryption support in the block layer, the CAP_PERFMON and CAP_BPF capabilities, a generalized kernel event-notification subsystem, the KCSAN data-race detector, and more. As always, see the KernelNewbies 5.8 page for more information.

Syndicate content

More in Tux Machines

libinput 1.16.0

libinput 1.16.0 is now available.

No significant changes since the second RC, so here's slightly polished RC1
announcement text.

This has been a long cycle, mostly because there weren't any huge changes on
the main development branch and a lot of the minor annoyances have found
their way into the 1.15.x releases anyway.

libinput now monitors timestamps of the events vs the current time when
libinput_dispatch() is called by the compositor. Where the difference
*may* result in issues, a (rate-limited) warning is printed to the log.
So you may see messages popping up in the form of
  "event processing lagging behind by XYZms, your system is too slow"
This is a warning only and has no immediate effect. Previously we would only
notice (and warn about) this when it affected an internal timer. Note that
these warnings do not show an issue with libinput, it shows that the the
compositor is not calling libinput_dispatch() quick enough.

The wheel tilt axis source was deprecated. No device ever had the required
udev properties set so we should stop pretending we support this.

Touchpads now support the "flat" acceleration profile. The default remains
unchanged and this needs to be selected in the configuration interface. The
"flat" profile applies a constant factor to movement deltas (1.0 for the
default speed setting).

Events from lid or tablet-mode switches that are known to libinput as being
unreliable are now filtered and no longer passed to the caller.
This prevents callers from receiving those known-bogus events and having to
replicate the same heuristics to identify unreliable devices that libinput
employs internally.

A new "libinput analyze" debugging tool is the entry tool for analysing
various aspects of devices. Right now the only tool is
"libinput analyze per-slot-delta" which can be used to detect pointer jumps
in a libiput record output. This tool used to live elsewhere, it was moved
to libinput so that reporters can easier run this tool, reducing the load on
the maintainers.

The tools have seen a few minor improvements, e.g.
- "libinput record touchpad.yml" does the right thing, no explicit --output
  argument required
- libinput measure touchpad-pressure has been revamped to be a bit more
  obvious
- libinput measure touchpad-size has been added (as replacement for the
  touchpad-edge-detector tool)
- libinput measure fuzz has been fixed to work (again and) slightly more
  reliable

The libinput test suite has been fixed to avoid interference with the
currently running session. Previously it was virtually impossible to work
while the test suite is running - multiple windows would pop up, the screen
would blank regularly, etc.

And of course a collection of fixes, quirks and new bugs.

As usual, see the git shortlog for details.

Diego Abad A (1):
      FIX: typo on building documentation

Peter Hutterer (2):
      test: semi-fix the switch_suspend_with_touchpad test
      libinput 1.16.0

git tag: 1.16.0
Read more Also: >Libinput 1.16 Released - Ready To Warn You If Your System Is Too Slow

18 Frameworks, Libraries, and Projects for Building Medical Applications

Open-source is not just a license or a code-based that left free on an online repository, It's a complete concept which comes with several advantages. Moreover, the most advantage you can get from Open-source is beyond the open-code it's FREEDOM; freedom to use or re-shape it as you see fit within your project commercial or otherwise, and that depends on the license of course. You are free from the headache of license conflict legal problems but also from the dilemma of dealing with restrections and limitations which come with property licenses. You are free from the system lock-in schemes, furthermore, you own your data, and freedom to customize the software as your structure requires and workflow demands. The Community: The Open-source project gains a powerful community as they gain users, the community users vary between advanced users, end-users, developers and end-users on decision-making level. Many of the community users are providing quality inputs from their usage and customized use-case and workflow or test-runs, Furthermore, they always have something to add as new features, UI modification, different usability setup, and overall introducing new workflows and tools, and That's what makes the progress of the open-source different than non-free solutions. While, Good community means good support, The community is a good resource to hire advanced users, developers, and system experts. It also provides alternative options when hiring developers. Unlike non-free software which are not blessed with such communities and where the options there are limited, The rich open-source community provides rich questions and answers sets that contributed by users from all around the world. Higher education value for the in-house team The open-source concept itself provides educational value, I owe most of what I know to open-source communities.The access to the source code and open-channels communication with the core developers is the best educational value any developer can get. Read more

Android Leftovers

Python Programming