Language Selection

English French German Italian Portuguese Spanish

Fedora, Red Hat and IBM

Filed under
Red Hat
  • Fedora 30 Will Get Bash 5.0 But Yum's Death Sentence Postponed To F31

    Fedora's Engineering and Steering Committee approved new work around the in-development Fedora 30. 

    Originally Fedora 29 was going to drop the old Yum package manager bits now that the DNF package manager has been in good shape for years and is largely a drop-in replacement to Yum. That didn't happen for Fedora 29 and just recently was proposed to drop Yum 3 for Fedora 30, but with that change coming in late and some tooling bits not ready in time, that has been diverted to Fedora 31. FESCo approves of dropping Yum 3 for Fedora 31 and is hoping it will be removed right after Rawhide branches for F30, giving plenty of time to fix any issues that may come up or other unexpected problems. 

  • Measuring user experience success with building blocks

    PatternFly is an open source design system used by Red Hat to maintain visual consistency and usability across the product portfolio. When the PatternFly team started work on PatternFly 4, the next major version of the system, they focused a large part of their effort on evolving the visual language. But how would users respond to the new look and feel?

    To get the raw and unfiltered feedback the team needed, Sara Chizari, a UXD user researcher, planned a reaction study with a fun twist and then headed to Red Hat Summit in San Francisco.

  • Backup partners target Red Hat Ceph Storage

    Red Hat Ceph Storage provides object, block and file data services for organizations modernizing their hybrid-cloud and data analytics infrastructures. With the release of Red Hat Ceph Storage 3.2, improved performance and functionality is driving new storage use cases in the modernized datacenter.

    In addition to data security and integrity, organizations must consider their strategy around data protection, backup and archiving. Whether you are backing up your enterprise application data as part of a disaster recovery strategy, or you are performing deep archives of sensitive records, rich media, or regulated data, Red Hat works with industry-leading backup, recovery and archiving partners to certify Ceph as a backup target for your most important data.

  • Effortless API creation with full API lifecycle using Red Hat Integration (Part 1)

    Nowadays, API development with proper lifecycle management often takes days if not weeks to get a simple API service up and running. One of the main reasons behind this is there are always way too many parties involved in the process. Plus there are hours of development and configuration.

  • Announcing Kubernetes-native self-service messaging with Red Hat AMQ Online

    Microservices architecture is taking over software development discussions everywhere. More and more companies are adapting to develop microservices as the core of their new systems. However, when going beyond the “microservices 101” googled tutorial, required services communications become more and more complex. Scalable, distributed systems, container-native microservices, and serverless functions benefit from decoupled communications to access other dependent services. Asynchronous (non-blocking) direct or brokered interaction is usually referred to as messaging.

    Managing and setting up messaging infrastructure components for development use was usually a long prerequisite task requiring several days on the project calendar. Need a queue or topic? Wait at least a couple weeks. Raise a ticket with your infrastructure operations team, grab a large cup of coffee, and pray for them to have some time to provision it. When your development team is adopting an agile approach, waiting days for infrastructure is not acceptable.

  • Settling In With IBM i For The Long Haul

    If nothing else, the IBM i platform has exhibited extraordinary longevity. One might even say legendary longevity, if you want to take its history all the way back to the System/3 minicomputer from 1969. This is the real starting point in the AS/400 family tree and this is when Big Blue, for very sound legal and technical and marketing reasons, decided to fork its products to address the unique needs of large enterprises (with the System/360 mainframe and its follow-ons) and small and medium businesses (starting with the System/3 and moving on through the System/34, System/32, System/38, and System/36 in the 1970s and early 1980s and passing through the AS/400, AS/400e, iSeries, System i, and then IBM i on Power Systems platforms.

    It has been a long run indeed, and many customers who have invested in the platform started way back then and there with the early versions of RPG and moved their applications forward and changed them as their businesses evolved and the depth and breadth of corporate computing changed, moving on up through RPG II, RPG III, RPG IV, ILE RPG, and now RPG free form. Being on this platform for even three decades makes you a relative newcomer.

More on Fedora 31

  • Fedora 31 Should Be Out Around The End of November

    While Fedora 31 was once talked about to never happen or be significantly delayed to focus on re-tooling the Linux distribution, they opted for a sane approach not to throw off the release cadence while working on low-level changes around the platform. A draft of the release schedule for Fedora 31 has now been published and it puts the release date at the end of November.

    Rather than delaying or cancelling the Fedora 31 release, it will go on like normal and the developers will need to work in their changes to the confines of their traditional six month release cadence.

  • Draft Fedora 31 schedule available

    It’s almost time for me to submit the Fedora 31 schedule to FESCo for approval. Before I do that, I’m sharing it with the community for comment. After some discussion before the end of the year, we decided not to go with an extended development cycle for Fedora 31. After getting input from teams within Fedora, I have a draft schedule available.

    The basic structure of the Fedora 31 schedule is pretty similar to the Fedora 30 schedule. You may notice some minor formatting changes due to a change in the tooling, but the milestones are similar. I did incorporate changes from different teams. Some tasks that are no longer relevant were removed. I added tasks for the Mindshare teams. And I included several upstream milestones.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

HTTP Vs. HTTPS

The internet runs on protocols. Rules and norm defined so that there is some form of standardization. One such protocol is the HyperText Transfer Protocol(HTTP). Read more

5 of the Best Linux Distros for Developers and Programmers

One of the reasons Linux is great is because of how flexible it is. For example, it can run on everything from servers to your old laptop to a Raspberry Pi. For this reason, it’s also a fantastic platform for developers. Whether you’re a seasoned developer or just using Linux to learn to program, you still have to choose a distribution. You could just choose Ubuntu and run with it, but there are plenty of “other options available to you.” Read more

How To Automatically Change GNOME Background In Intervals Using BASH

Have you ever wanted to have that automatic background switching feature on your GNOME Linux distro? I missed that feature after I switched from Cinnamon to GNOME :( Searched for apps in the software center and alas there is none that I could find. However, today I’m happy to let you know that there is a workaround to this missing feature through the use of BASH scripting language. Read more

Arm-based IoT gateway runs on Moxa Industrial Linux

Moxa announced a -40 to 85°C tolerant “UC-8200” IoT gateway that runs Moxa Industrial Linux on a dual-core, -A7 SoC and offers dual GbE, RS-232/422/485, and mini-PCIe links, plus a CAN port, WiFi/BT, and optional 4G LTE. Moxa, which announced its Cortex-A8-based UC 2100 series of Industrial IoT gateways last April, partially unveiled a new IIoT gateway called the UC-8200. The system features an unnamed dual-core, Cortex-A7 SoC that “has been optimised for use in energy monitoring systems but is widely applicable to a variety of industrial solutions,” according to the PR-like Control Engineering story that announced the product along with a shorter Industrial Ethernet Book post. Eventually, a product page should appear with missing details such as RAM and storage. Yet, even the product page for the similar UC-8100 series fails to describe the Cortex-A8 SoC. Other specs are complete, however, such as the earlier model’s 256MB to 512MB DDR3 and 8GB eMMC. (Update: LinuxGizmos reader Arnd Bergmann spotted the earlier UC-8100’s SoC family in the firmware image’s device tree. It’s a TI Sitara AM33x, perhaps one of the AM335x family, which runs on BeagelBone boards.) Read more Also: Arm Neoverse N1 & E1 Platforms Announced For Cloud To Edge Computing