Fedora, Red Hat and IBM
-
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.
- Login or register to post comments
- Printer-friendly version
- 3483 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
More on Fedora 31
Fedora 31 Should Be Out Around The End of November
Draft Fedora 31 schedule available