Language Selection

English French German Italian Portuguese Spanish

Red Hat and SUSE: Drools, Systemd, Libinput, Fedora and Beta for SUSE Manager 4.0

Filed under
Red Hat
SUSE
  • Quarking Drools: How we turned a 13-year-old Java project into a first-class serverless component

    Rule-based artificial intelligence (AI) is often overlooked, possibly because people think it’s only useful in heavyweight enterprise software products. However, that’s not necessarily true. Simply put, a rule engine is just a piece of software that allows you to separate domain and business-specific constraint from the main application flow. We are part of the team developing and maintaining Drools—the world’s most popular open source rule engine and part of Red Hat—and, in this article, we will describe how we are changing Drools to make it part of the cloud and serverless revolution.

  • Why feedback, not metrics, is critical to DevOps

    Most managers and agile coaches depend on metrics over feedback from their teams, users, and even customers. In fact, quite a few use feedback and metrics synonymously, where they present feedback from teams or customers as a bunch of numbers or a graphical representation of those numbers. This is not only unfortunate, but it can be misleading as it presents only part of the story and not the entire truth.

  • L2TP Tunnel Support Added To Systemd

    The newest feature addition for systemd is supporting L2TP, the Layer 2 Tunneling Protocol, as part of its networking code. 

    Systemd's networkd now has support merged for LT2TP tunnel support. L2TP can be used for extending a local area network (LAN) or also for VPN purposes when paired with the likes of IPsec for providing encryption. L2TP also has a variety of other use-cases with this bare protocol able to offer a layer two link over an L3 network.

  • libinput 1.12.901
    The first RC for libinput 1.13 is now available.
    
    
    
    
    Only two notable features in this release but patches are accumulating on
    master, it's been 6 months since 1.12 and I've decided to postpone the two
    major features (hi-res scrolling and totem support) to 1.14.
    
    
    
    
    Touch arbitration has improved for tablets, especially on touch screens.
    A timer set on pen proximity out means we don't get ghost touches anymore
    when the hand lifts off slower than the pen itself. And location-based touch
    arbitration means that parts of the screen can be interacted with even while
    the pen is in proximity. libinput uses the tilt information where
    available to disable touches in a rectangle around the pen where the hand is
    likely to be but leaves the rest of the touchscreen available otherwise.
    Where the UI supports it, this allows for bimanual interaction.
    
    
    
    
    The test suite is installed on demand (meson -Dinstall-tests=true). Where
    run from the installed location it will use the normal library lookups and
    the quirks directory as defined by the prefix. This makes it useful for
    distribution-level testing, i.e. run this on a test machine after updating
    the package to make sure everything is as expected. Where available, you can
    invoke it with the "libinput test-suite" command.
    
    
    
    
    Other than that, a load of fixes, quirks added, cleanups, tidy-ups and so on
    an so forth.
    
    
    
    
    As usual, the git shortlog is below. Many thanks to all the contributors.
  • Libinput 1.13 Is Coming But High-Resolution Scrolling & Dell Totem Support Delayed

    Libinput is fairly mature at this stage for offering a unified input handling library for use on both X.Org and Wayland Linux desktops. Libinput has largely reached a feature plateau with new releases no longer coming out so often and no glaring gaps in support. With it already being a half-year since the last major release, libinput 1.13 is now being buttoned up for release and available today is the first release candidate. 

    Libinput 1.13 isn't that exciting of a release particularly since maintainer Peter Hutterer of Red Hat decided to delay the high resolution scrolling support. The Linux 5.0 kernel brought the much anticipated high resolution scrolling support for various Logitech/Microsoft mice to improve the scroll-wheel experience. Besides the kernel support, there is also the user-space support that needs updating. Peter decided to delay this functionality now until Libinput 1.14 to give it more time to bake.

  • New package in Fedora: python-xslxwriter
  • First Public Beta for SUSE Manager 4.0!

More in Tux Machines

KDE Usability & Productivity: Week 72

Week 72 in Usability & Productivity initiative is here and it’s chock-full of goodies! We continue to polish Plasma 5.16 ahead of its release in two weeks. There was one point in time when veteran KDE developer and author of the new notifications system Kai Uwe Broulik was literally committing fixes faster than I could add them to this blog post! In addition, features for Plasma 5.17 as well as many of our apps are starting to trickle in. Check it out... Read more

Iran & Iraq Are Embracing GNU Health Project | Dr Axel Braun

In this episode of Let’s Talk, Dr Axel Braun talks about the new features and updates of the GNU Health project. He also talked about the increasing adoption of the project. Read more Also: The Man Behind OpenSUSE Conference – Douglas DeMaio

GNOME 3.33.2 released!

Hello GNOME developers,

GNOME 3.33.2 is now available. This is the second unstable release
leading to 3.34 stable series.

I had to disable gnome-contacts, gnome-calendar and gnome-maps because of the not-very-well coordinated evolution-data-server transition.

If you want to compile GNOME 3.33.2, you can use the official
BuildStream project snapshot.

https://download.gnome.org/teams/releng/3.33.2/gnome-3.33.2.tar.xz

The list of updated modules and changes is available here:

https://download.gnome.org/core/3.33/3.33.2/NEWS

The source packages are available here:

https://download.gnome.org/core/3.33/3.33.2/sources/

WARNING!
--------
This release is a snapshot of development code. Although it is
buildable and usable, it is primarily intended for testing and hacking
purposes. GNOME uses odd minor version numbers to indicate development
status.

For more information about 3.34, the full schedule, the official module
lists and the proposed module lists, please see our 3.33 wiki page:

https://www.gnome.org/start/unstable


Cheers,

Abderrahim Kitouni,
GNOME Release Team
Read more Also: GNOME 3.33.2 Released As Another Step Towards The GNOME 3.34 Desktop

Security Leftovers

  • Serious Security: Don't let your SQL server attack you with ransomware [Ed: Article focuses on things like Windows and RDP. SQL Server is proprietary software that runs on a platform with NSA back doors. So if you choose it, then you choose to have no security at all, only an illusion of it. Why does the article paint Windows issues as pertaining to MySQL?]
    Tales from the honeypot: this time a MySQL-based attack. Old tricks still work, because we're still making old mistakes - here's what to do. [...] As regular readers will know, one of the popular vehicles for malware crooks at the moment is Windows RDP, short for Remote Desktop Protocol.
  • How Screwed is Intel without Hyper-Threading?
    As it stands Microsoft is pushing out OS-level updates to address the four MDS vulnerabilities and you’ll get those with this month's Windows 10 1903 update. However, this doesn’t mitigate the problem entirely, for that we need motherboard BIOS updates and reportedly Intel has released the new microcode to motherboard partners. However as of writing no new BIOS revisions have been released to the public. We believe we can test a worst case scenario by disabling Hyper-Threading and for older platforms that won’t get updated this might end up being the only solution.
  • SandboxEscape drops three more Windows 10 zero-day exploits

    SandboxEscaper also indicated that she was in the market to sell flaws to "people who hate the US", a move made in apparent response to FBI subpoenas against her Google account.

  • Huawei can’t officially use microSD cards in its phones going forward

    The SD Association is also by no means the first to cut ties: Google, ARM, Intel, Qualcomm, and Broadcom are also among the companies that have stopped working with Huawei due to the ban. The Wi-Fi Alliance (which sets Wi-Fi standards across the industry) has also “temporarily restricted” Huawei’s membership due to the US ban, and Huawei has also voluntarily left JEDEC (a semiconductor standards group best known for defining RAM specifications) over the issues with the US as well, according to a report from Nikkei Asian Review. All this could severely hamper Huawei’s ability to produce hardware at all, much less compete in the US technology market.

  • Huawei barred from SD Association: What’s that mean for its phones and microSD cards?

    As such, companies that aren’t on the SD Association’s list of members can’t officially produce and sell devices with SD card support that use the SD standards. According to SumahoInfo, the member page showed Huawei a few weeks ago, but no longer lists the firm this week.