Language Selection

English French German Italian Portuguese Spanish

IBM/Red Hat Leftovers

Filed under
Red Hat
  • Fugaku Retains Official #1 Spot on TOP500

    Summit, which is an IBM-built system installed at the Oak Ridge National Laboratory (ORNL) in Tennessee, remains the fastest system in the United States.

  • Modernizing Enterprise Java: A cloud native guide for developers

    Looking for a quick guide to migrating and modernizing your organization's Java-based applications? Modernizing Enterprise Java walks you through the journey. Download the free e-book today.

    Java has been one of the most popular programming language choices for developers since its release 25 years ago. It is backed by an open source ecosystem of contributors and a growing number of companies who rely on Java for their core business workloads.

  • Build lightweight and secure container images using RHEL UBI

    Deploying applications in lightweight container images has practical benefits because container images pack all of the dependencies required for your application to function properly. However, you could lose the benefits of containerization if the container images are too large, and thus take several minutes to boot up the application. In this article, I guide you through how to use Red Hat Universal Base Images (UBI) as the foundation to build lightweight and secure container images for your applications.

  • Automate dependency analytics with GitHub Actions [Ed: IBM's Red Hat boosting Microsoft's proprietary software and vendor lock-in]
  • 20 Years of Red Hat Product Security: From inception to customer experience (Part 1)

    From its inception in 2001, the Product Security team has been focused on providing Red Hat’s customers value in the form of hardened and streamlined security updates and testing across the entire product line, including managed services and, most recently, our own open source software supply chain.

    But more than that, they’ve also been essential members of the wider open source security community, helping ensure the openness and transparency of security vulnerability information, aiding in the fight against open source fear, uncertainty, and doubt (FUD), and being key contributors in the response to a wide array of high profile security incidents and vulnerabilities.

    So, let’s take a look at how Product Security has evolved at Red Hat over the past 20 years, and at what the future might look like.

  • Skills gap proves a growing barrier for digital transformation initiatives

    In this year’s Red Hat 2022 Global Tech Outlook report, skill-set or talent gaps emerged as the top barrier organizations believe will prevent them from achieving their digital transformation goals. This was also reflected in organizations’ non-IT funding priorities for the next 12 months.

    Red Hat develops a Global Tech Outlook report every year, and from June through August 2021, we surveyed 1,341 information technology (IT) leaders and decision makers to learn about their digital transformation journeys, their IT and non-IT funding priorities for the coming year, and the types of infrastructure they’re using to run their applications.

  • U.S. Government issues directive to prioritize fixing exploited CVEs: How Red Hat Insights can help

    In November 2021, the U.S. federal government published a Cybersecurity and Infrastructure Security Agency’s Binding Operational Directive. This Department of Homeland Security (DHS) directive mandates federal agencies within the U.S. act to protect themselves from "...increasingly sophisticated malicious cyber campaigns that threaten the public sector, private sector, and ultimately the American people’s security and privacy."

    The directive requires United States federal agencies to patch known, "publicly exploited'' vulnerabilities. The list of these vulnerabilities is cataloged and updated by the Cybersecurity & Infrastructure Security Agency (CISA) (on their website) periodically.

  • Digital transformation: How to beat the challenges of a federated organization | The Enterprisers Project

    In early 2019, I started my role as business transformation executive for the Federal Reserve System, responsible for leading the digital transformation of finance, human resources, and procurement.

    As the central bank of the United States, the Federal Reserve is a federated organization made up of 22,000 employees across the 12 Reserve banks. Each bank is its own separate legal entity with its own board of directors, CEO, CFO, CIO, and senior HR and procurement officers.

    Over the years, technology was consolidated while processes and capabilities remained disparate, and it became increasingly challenging to deliver even basic capabilities. With over 40 disjointed, mostly homegrown legacy applications and a high degree of customization supporting proprietary business processes, the system was costly and challenging to maintain. New employees were frustrated by the poor user experience and difficulty accessing data, and collaboration and innovation were hampered.

  • Digital transformation: 4 questions CIOs should ask now | The Enterprisers Project

    One of the things CIOs have learned during the past eighteen months is that when you have the business behind you, the momentum for transformation is turbocharged. Top CIOs are capitalizing on this lesson to further integrate technology strategy with business strategy. And the first place they’re starting is with the people.

    How well are you doing on the people front of digital transformation? Here are four questions to ask yourself, based on my recent conversations with the CIOs of CarMax, Dow, and Johnson & Johnson.

  • Virtual Machine Secure Boot Database Updates Made Easy with Oracle Linux

More in Tux Machines

Chile citizens: Support these constitutional proposals for free software and user privacy by Feb 1

Chile is in the midst of governmental changes, and with these changes comes the opportunity for the people of Chile to make their voices heard for long-term benefits to their digital rights and freedoms. Chilean activists have submitted three constitutional proposals relating to free software and user freedom, but they need signatures in order to have these proposals submitted to the constitutional debate. We encourage free software community members in Chile to have a look at these proposals, and sign those that uphold digital freedom and autonomy. The deadline for collecting signatures is February 1st. Some further explanation and other information gathered by one of our community members, Felix Freeman, is included below. The English version of Felix's message is provided below. Read more

GNU poke 2.0 released

I am happy to announce a new major release of GNU poke, version 2.0. This release is the result of a full year of development. A lot of things have changed and improved with respect to the 1.x series; we have fixed many bugs and added quite a lot of new exciting and useful features. See the complete release notes at https://jemarch.net/poke-2.0-relnotes.html for a detailed description of what is new in this release. We have had lots of fun and learned quite a lot in the process; we really wish you will have at least half of that fun using this tool! Read more

LWN Articles on Linux Kernel (Liberated Thursday)

  • Resurrecting fbdev [LWN.net]

    The Linux framebuffer device (fbdev) subsystem has long languished in something of a purgatory; it was listed as "orphaned" in the MAINTAINERS file and saw fairly minimal maintenance, mostly driven by developers working elsewhere in the kernel graphics stack. That all changed, in an eye-opening way, on January 17, when Linus Torvalds merged a change to make Helge Deller the new maintainer of the subsystem. But it turns out that the problems in fbdev run deep, at least according to much of the rest of the kernel graphics community. By seeming to take on the maintainer role in order to revert the removal of some buggy features from fbdev, Deller has created something of a controversy. Part of the concern within the graphics community is the accelerated timeline that these events played out on. Deller posted his intention to take over maintenance of the framebuffer on Friday, January 14, which received an ack from Geert Uytterhoeven later that day. Two days later, before any other responses had come in, Deller sent a pull request to Torvalds to add Deller as the fbdev maintainer, which was promptly picked up. On January 19, Deller posted reversions of two patch sets that removed scrolling acceleration from fbdev. In the meantime, those reversions had already been made in Deller's brand new fbdev Git tree.

  • The first half of the 5.17 merge window [LWN.net]

    As of this writing, just short of 7,000 non-merge commits have been pulled into the mainline kernel repository for the 5.17 release. The changes pulled thus far bring new features across the kernel; read on for a summary of what has been merged during the first half of the 5.17 merge window.

  • Struct slab comes to 5.17 [LWN.net]

    The page structure is at the core of the memory-management subsystem. One of these structures exists for every page of physical memory in the system; they are used to track the status of memory as it is used (and reused) during the lifetime of the system. Physical pages can adopt a number of different identities over time; they can hold user-space data, kernel data structures, DMA buffers, and so on. Regardless of how a page is used, struct page is the data structure that tracks its state. These structures are stored in a discontiguous array known as the system memory map. There are a few problems that have arisen with this arrangement. The page structure was significantly reorganized for 4.18, but the definition of struct page is still a complicated mess of #ifdefs and unions with no mechanisms to ensure that the right fields are used at any given time. The unlucky developer who needs to find more space in this structure will be hard put to understand which bits might be safe to use. Subsystems are normally designed to hide their internal data structures, but struct page is heavily used throughout the kernel, making any memory-management changes more complicated. One possible change — reducing the amount of memory consumed by page structures by getting rid of the need for a structure for every page — is just a distant dream under the current organization. So there are a lot of good reasons to remove information from struct page and hide what remains within the memory-management subsystem. One of the outcomes from the folio discussions has been a renewed desire to get a handle on struct page, but that is not a job for the faint of heart — or for the impatient. Many steps will be required to reach that goal. The merging of the initial folio patches for 5.16 was one such step; the advent of struct slab in 5.17 is another.

PETget now PKGget

The traditional package manager in Puppy Linux is the "Puppy Package Manager", often just known as the "PPM". EasyOS has a derivative of the PPM, named "PETget". However, I have never been entirely happy with that name, as the package manager can install virtually any type of package -- .deb, .rpm. .tgz, .tar.zst, .tar.xz, etc., as well as .pet packages. Read more