Language Selection

English French German Italian Portuguese Spanish

Fedora Family / IBM and Red Hat Leftovers

Filed under
Red Hat

  • Downstream automation is here | Packit

    As the first step on our way to Fedora users, we need to get the new upstream release to the Fedora dist-git.

  • 5 tips to prevent IT team burnout

    During the pandemic shutdown, the concept of 24/7 employee availability became normalized – especially for IT professionals, many of whom who found themselves within reach of their laptops at all times. This new normal led many IT folks to experience burnout, with stress and frustration negatively impacting the quality of their work, their personal relationships, and even their mental health.

    As a leader, you can help prevent your IT team from succumbing to burnout. Here are five tips to help ensure that your team stays happy, healthy, and productive.

  • Hybrid work: 3 technology questions CIOs should be asking [Ed: More buzzwords (about working from home and centrralised office space)]

    Hybrid work is here to stay, as workers around the globe are now insisting on that flexibility. According to a Frost & Sullivan survey of global IT decision-makers, 93 percent of business leaders expect one-quarter or more of their employees to work from home moving forward, with most likely moving between home and the office.

    As we look to assess the impact of this new way of working, CIOs need to set guidelines for what their hybrid workplace will look like and determine how they can help employees and employers navigate new workflows effectively and productively. Here are some questions to help start that process.

  • Use this open source screen reader on Windows [Ed: Red Hat promoting Microsoft Windows stuff]
  • Near zero marginal cost societies and the impact on why we work

    I have read Jeremy Rifkin's book The Zero Marginal Cost Society: The Internet of Things, the Collaborative Commons, and the Eclipse of Capitalism, which has a strong connection to open organization principles, particularly community building. Rifkin also writes about the future of green energy generation and energy use in logistics. This is the second of three articles in this series. In my previous article, I examined the Collaborative Commons. In this article, I look at its impact on energy production and supply.

    Within the next 25 years, Rifkin believes most of our energy for home heating, running appliances, powering businesses, driving vehicles, and operating the whole economy will be nearly free with on-site power solar, wind and geothermal energy generation. This is starting already, through both individual and micropower plants. The payback is around two to eight years.

  • Manage JMX credentials on Kubernetes with Cryostat 2.1

    Cryostat is a tool for managing JDK Flight Recorder data on Kubernetes. If you have Java Management Extensions (JMX) authentication enabled on your containerized Java Virtual Machines (JVMs), Cryostat will prompt you to enter your JMX credentials before it can access the JDK flight recordings on your target JVMs. On the Cryostat console, the Automated Rules, Recordings, and Events tabs will require you to enter your JMX credentials if you want to view existing flight recordings or perform a recording operation on a target with JMX authentication enabled. When monitoring multiple target JVMs with Cryostat features such as automatic rules, you may want Cryostat to remember and reuse your JMX credentials for each target connection.

  • Approaches to implementing multi-tenancy in SaaS applications

    The SaaS architecture checklist is a series of articles that cover the software and deployment considerations for Software as a Service (SaaS) applications. This article discusses architectural approaches for separating and isolating SaaS tenants to provide multi-tenancy, the provisioning of services to multiple clients in different organizations. For the approaches, the type and level of isolation provided are compared, along with their tradeoffs.

    The approaches laid out in different sections of the article are not mutually exclusive and can be combined to provide the levels of separation and isolation necessary to satisfy the requirements of your SaaS customers and markets. We'll also discuss how to incorporate existing single-tenant applications into a SaaS environment.

More in Tux Machines

Proprietary Systems: Chromebooks, Windows, and Microsoft’s xClown

New GNU Releases and FSF Spring "Bulletin"

  • June GNU Spotlight with Amin Bandali: Twelve new GNU releases! [Ed: Much respect to Amin Bandali for stepping up and helping the FSF a lot when it needed it the most]
  • Spring "Bulletin": Verifying licenses, free software in education, and more!

    Software freedom needs our advocacy, our words and voices, and our generosity to spread. The biannual Free Software Foundation Bulletin is an item made for sharing, its articles from FSF staff and community members help facilitate the conversation about the importance of free software in daily life. It is a great tool to help people find their reason to support free software, to contribute to free software, or -- for the many who are just learning about it -- to take their next steps up the ladder to freedom.

pgAdmin 4 v6.11 Released

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 6.11. This release of pgAdmin 4 includes 20 bug fixes and new features. For more details please see the release notes. pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see the website. Read more Also: PostgreSQL: Announcing the release of AgensGraph 2.12

today's leftovers

  • The Month in WordPress – June 2022 – WordPress News

    With WordPress 6.1 already in the works, a lot of updates happened during June. Here’s a summary to catch up on the ones you may have missed.

  • Join the LibreOffice Team as a Web Technology Engineer (m/f/d), 10-20h per week, remote

    To provide high quality tools for our contributors, together working on office productivity for over 200 million users around the globe, we are searching for a Web Technology Engineer (m/f/d) to start work as soon as possible.

  • Unravelling complexity in a software-defined vehicles industry | Ubuntu

    Vehicles are becoming more connected, autonomous, shared and electric (the famous CASE acronym). While customers expect new features and upgradability, the software and hardware components enabling such innovations require a different system architecture to function. This is a major change for the automotive industry as it requires new software skills, methodologies and business models. At the same time, automotive manufacturers need to adhere to complex and strict industry standards, and uphold safety-critical functions. In this post, we will focus on the different challenges the industry is facing in terms of hardware and software complexity, cybersecurity and safety. We will also discuss how Original Equipment Manufacturers (OEMs) can learn from software companies to survive this transition towards software-defined vehicles and succeed. [...] On top of this, regulations are becoming very strict, forcing OEMs to provide patches and fixes to common vulnerabilities and exposures (CVE). Taking into account the previously detailed system complexity, it is becoming increasingly necessary to move towards a software-defined holistic context. Only a software-defined approach can provide the required flexibility and scalability that allows companies to comply with regulatory requirements while providing UX updates and handling hardware complexity. Of course, cybersecurity never only relies on software. Hardware vulnerabilities can also occur and usually lead to even worse consequences. Some hardware issues can be patched via software, but usually these CVEs remain valid throughout the system’s lifetime. For example, Meltdown and Spectre, two of the most widespread hardware vulnerabilities in the world, are still present and affecting tons of devices. This means that during hardware conception, cybersecurity must be taken into account in the specifications and system architecture in order to limit these vulnerabilities.