news
Copr, Slop, and Red Hat's Slopfest
-
Copr: Give your Copr profile a README
If you use Copr a lot, your project list grows fast. Personal experiments, scratch builds, one-off test repos, they all pile up next to the number of projects you actually care about. Pinned projects already assist with that; you can keep up to four projects visible in your profile by pinning them. But four is a hard limit, and a handful of icons at the top of the page is the only way it can highlight it.
-
Tomas Tomecek: How Hey Hi (AI) agents rekindled passion for my open source projects [Ed: Fedora and slop in bed together]
This is a short story of how thanks to Hey Hi (AI) agents, I am again passionate about my open source projects, namely pretty-git-prompt (p-g-p in short).
-
Techstrong Group Inc ☛ Red Hat Readies an MCP Server to Help LLMs Manage Kubernetes [Ed: Red Hat wastes efforts pumping up a bubble; this will imperil this company's future]
Red Hat is building an open source MCP server extension to help developers and administrators manage Kubernetes and Red Hat’s own OpenShift Kubernetes distribution. The extension can help Hey Hi (AI) assistants like Visual Studio Code, Abusive Monopolist Microsoft Copilot, and Cursor control and interact with Kubernetes clusters. It is one of a number
-
Red Hat ☛ The tokenomics of self-hosted LLMs [Ed: IBM peddling slop plagiarism in Red Hat's name]
Paying a cloud API per million tokens is straightforward until the invoice arrives. But when you move to self-hosted large language models (LLMs), the economics flip upside down: you pay for raw compute regardless of whether your GPUs are processing requests or idling.
For platform engineers and machine learning operations (MLOps) leads, tokenomics, the economics of how tokens are produced and what they effectively cost, requires looking at both what you spend and how much you serve.
Calculating cost per token for self-hosted LLMs comes down to controlling 2 main levers: spending less and serving more.
-
Red Hat ☛ Accelerate automation with Hey Hi (AI) and the Ansible development tools MCP servers [Ed: Ditto]
Ask an Hey Hi (AI) assistant how to lint an Ansible playbook today, and you'll likely get a helpful but generic answer: "Use ansible-lint. Install it with pip install ansible-lint, then run it against your playbook." Correct. But not useful when you already have
ansible-lintinstalled, your team has a custom linting profile, and what you wanted was for the tool to run and fix the violations. -
Red Hat Official ☛ Scaling agentic AI: How llm-d enables infrastructure sovereignty [Ed: IBM Red Hat selling slop plagiarism under the guise of "infrastructure sovereignty"]
For many organizations, this creates a new kind of dependency. They've embraced open models and retained ownership of their data, yet their AI strategy still depends on a single hardware ecosystem.
-
Red Hat Official ☛ From experiment to production: A reliable architecture for version-controlled MLOps [Ed: Some more mindless buzzwords for slop]
But, there’s good news. If you’re working in a Red Hat environment, our new AI quickstart helps address this exact problem. It combines the orchestration power of Red Hat OpenShift AI with the "Git-for-data" versioning capabilities of lakeFS.
-
HPC Wire ☛ CIQ Opens Direct Purchase of Enterprise Linux and Removes Procurement from the Path to Production
The CIQ portal now takes a team from first look to production in one place. Users browse the full product portfolio and download ISOs, VM and cloud images, container images, and packages. They claim free or developer licenses, evaluate commercial products, and buy them directly. Licenses, credentials, organizations, team roles, and permissions are managed from the same interface, alongside CIQ documentation and support. Free software is available the moment an account is created, and commercial products are available to anyone ready to buy one.
-
Best Linux Hosting 2026: Everything Runs on Linux. Here's Who Runs It Best [Ed: Seems like promotional spam though]