Ubuntu 26.10 daily builds now available to download

Ubuntu logo behind stingray in the ocean.Daily builds of Ubuntu 26.10 ‘Stonking Stingray’ are now available for download, as development on the distro’s next major release kicks in to gear. As the name suggests, new ISOs are produced from development code on a (mostly) daily basis, giving those keen to test October’s release in advance the ability to do so. However, because package updates can break the ability for a bootable image to be created, it’s not unusual for there to be temporary gaps between new daily builds being available. Daily builds will continue to be produced for remainder of the Ubuntu 26.10 development cycle, right […]

You’re reading Ubuntu 26.10 daily builds now available to download, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingUbuntu 26.10 daily builds now available to download

Alpine Linux Experiments with Systemd Compatibility While Keeping Its Lightweight Identity

Alpine Linux Experiments with Systemd Compatibility While Keeping Its Lightweight Identity

Alpine Linux, one of the most recognizable non-systemd Linux distributions, is reportedly experimenting with an optional systemd compatibility layer, a move that has sparked intense discussion across the Linux community.

For years, Alpine has stood apart from mainstream Linux distributions by avoiding both glibc and systemd, instead relying on:

  • musl libc
  • BusyBox
  • OpenRC as its init system

Now, growing software compatibility pressures, especially around desktop applications, containers, and enterprise tooling, appear to be pushing Alpine developers to explore new approaches.

Why Alpine Linux Avoided Systemd for So Long

Alpine Linux built its reputation around simplicity, security, and minimalism. Unlike many mainstream distributions, Alpine intentionally avoided systemd in favor of the lighter and more modular OpenRC init system.

This design philosophy made Alpine extremely popular for:

  • Containers and Docker images
  • Embedded systems
  • Lightweight virtual machines
  • Security-focused deployments

Its tiny footprint and reduced dependency chain became major advantages in cloud and container environments.

The Compatibility Problem Is Growing

Despite Alpine’s popularity, avoiding systemd has increasingly created compatibility challenges.

Many modern Linux applications now assume the presence of:

  • libsystemd
  • systemd APIs
  • glibc-specific behaviors

This has become particularly problematic for:

  • Desktop software
  • Proprietary enterprise applications
  • Monitoring agents
  • Certain gaming and multimedia tools
  • AI and container orchestration software

Historically, Alpine users often relied on:

  • Compatibility layers like gcompat
  • Flatpak containers
  • Docker workarounds
  • Manually patched packages

The growing complexity of those workarounds appears to be one reason compatibility discussions are intensifying.

What the Experimental Compatibility Layer Actually Means

Importantly, Alpine Linux is not replacing OpenRC with systemd.

Instead, the project appears to be exploring:

  • Optional compatibility packages
  • libsystemd support
  • Improved API compatibility for software expecting systemd components

Experimental efforts already exist in the broader ecosystem. For example, unofficial projects have packaged portions of systemd, particularly libsystemd, for Alpine systems specifically to satisfy software dependencies without running full systemd services.

Continue ReadingAlpine Linux Experiments with Systemd Compatibility While Keeping Its Lightweight Identity

Debian Experiments with AI-Assisted Bug Triage as Open-Source Projects Face Growing Report Overload

Debian Experiments with AI-Assisted Bug Triage as Open-Source Projects Face Growing Report Overload

The Debian project has begun exploring AI-assisted bug triage workflows, joining a broader movement across the open-source world to manage the rapidly increasing volume of software bug reports and vulnerability submissions.

While Debian developers are approaching the idea cautiously, the effort reflects a growing reality for large open-source projects: modern software ecosystems are producing more bugs, duplicate reports, and security findings than human maintainers can efficiently process alone.

The discussion arrives during a period of intense debate within Linux and open-source communities about how artificial intelligence should be integrated into software development and maintenance.

Why Debian Is Looking at AI-Assisted Triage

Debian is one of the largest and most complex Linux distributions in existence, maintaining tens of thousands of software packages across multiple architectures and release branches. Managing bug reports at that scale has always been challenging.

Now, AI-assisted vulnerability scanning and automated testing tools are dramatically increasing report volumes across open-source projects. Maintainers are increasingly facing:

  • Duplicate vulnerability reports
  • Low-quality automated submissions
  • Massive triage backlogs
  • Security mailing list overload
  • Increasing maintainer burnout

AI-assisted bug triage systems are being explored as a way to help organize, prioritize, and categorize incoming reports before human maintainers review them.

What AI-Assisted Bug Triage Actually Means

Importantly, Debian is not handing software maintenance over to AI systems.

Instead, AI-assisted triage generally focuses on repetitive administrative tasks such as:

  • Detecting duplicate bug reports
  • Categorizing issues by severity
  • Routing bugs to appropriate maintainers
  • Summarizing lengthy reports
  • Identifying missing reproduction details
  • Prioritizing security-related submissions

The goal is to reduce the amount of manual sorting work maintainers must perform before actual debugging begins.

The Open-Source Community Is Divided

Debian’s experiments come during an ongoing debate about AI’s role in open-source development.

Some maintainers view AI-assisted tooling as necessary because software complexity has outpaced human review capacity. Others worry about:

  • Low-quality AI-generated reports
  • Maintainer overload
  • False positives
  • Loss of contributor accountability
  • “Drive-by” AI contributions with little human understanding

The Debian community itself has spent months discussing how AI-assisted contributions should be handled, but no final project-wide policy has yet been adopted.

Continue ReadingDebian Experiments with AI-Assisted Bug Triage as Open-Source Projects Face Growing Report Overload

GNOME Sushi spacebar preview fix coming to Ubuntu 26.04

GNOME Sushi.GNOME Sushi fans, rejoice: the spacebar preview feature is being fixed in Ubuntu 26.04. If you’re not familiar with it, GNOME Sushi is a file preview tool similar to Quick Look on macOS. Select a file in Nautilus, press space and a floating preview window appears. It works with images, video and audio files, PDFs, plain text files and more. GNOME’s Sushi isn’t preinstalled in Ubuntu but many users install it themselves as it makes it easier to find specific files when rooting through folders filled with samey-seeming documents, audio files and video clip. —Well, except it doesn’t (or rather, […]

You’re reading GNOME Sushi spacebar preview fix coming to Ubuntu 26.04, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingGNOME Sushi spacebar preview fix coming to Ubuntu 26.04

Implementing Secure Zero-Touch Provisioning in AI and Edge Infrastructure

By Juha Holkkola, FusionLayer Group

How DHCP Changed Connectivity

In the late 1990s, the DHCP (Dynamic Host Configuration Protocol) quietly catalyzed a revolution in digital connectivity. Before DHCP was introduced, connecting devices to a network involved manual entry of IP addresses, DNS servers, subnet masks, and gateways. Networks were fragile, prone to errors, and severely limited in scalability. The introduction of DHCP changed everything and became a game-changer for networking.

With widespread adoption across operating systems, DHCP made networking a plug-and-play experience. This fundamental change accelerated the adoption of Wi-Fi, standardized enterprise networks using DHCP-based addressing, and propelled the mobile Internet to viability. While DHCP simplified network connectivity by automating IP address assignments, it also introduced the world to the essence of effortless connectivity.

Fast forward to today, connectivity remains effortless, yet escalating threats continuously challenge digital trust. Just as DHCP revolutionized connectivity, we are primed for a transformation of equal magnitude concerning digital trust. The solution is clear: we must automate trust through Secure Zero-Touch Provisioning (SZTP).

SZTP: Secure Zero-Touch Provisioning

Modern digital infrastructure, spanning cloud nodes, edge systems, IoT sensors, industrial robotics, home gateways, and AI-centered factories, necessitates robust security measures. To maintain secure environments, each device in this extensive ecosystem must autonomously verify its needs. This includes self-authentication, receiving verified firmware, installing necessary credentials, and joining orchestrated environments without human intervention, which DHCP alone cannot accomplish.

Secure Zero-Touch Provisioning (SZTP), as defined in RFC 8572, steps up to address these needs in our complex digital reality. It builds trust by automating the exchange of essential artifacts and certificates required for seamless device bootstrapping: verifying hardware identity, delivering trusted firmware and OS images, applying patches, injecting cryptographic credentials, and setting up a complete runtime environment automatically, without manual interaction.

SZTP is based on open standards, making it vendor-neutral and ideal for large-scale deployments. As digital ecosystems grow in complexity, SZTP promises a future in which AI agents can autonomously request and deploy secure infrastructure within minutes, enhancing operational efficiency and security simultaneously.

Step-by-Step: Implementing SZTP in Your Infrastructure

  1. Device Identification and Authentication

Begin by integrating SZTP in your network infrastructure. Once a device powers on, it must first establish identity through a secure channel. This is typically done using hardware-based security measures, such as a TPM (Trusted Platform Module), to provide hardware attestation.

  1. Firmware Verification and Secure Image Delivery

Implement policies to verify firmware integrity. Use cryptographic signatures to ensure firmware authenticity. SZTP can fetch secure firmware and OS images from trusted repositories. For instance, create a policy that requires all devices to verify their firmware against a centralized manifest.

  1. Credential Injection and Environment Initialization

Devices securely receive cryptographic credentials and configuration files. Use automated scripts to distribute these credentials from a central management server. Next, deploy containerized workloads using tools such as Kubernetes to orchestrate the environment.

  1. Lifecycle Management and Patch Automation

With SZTP, configure automated patch management systems to apply security patches and software updates. Implement CI/CD pipelines that automatically redeploy updated firmware images, ensuring devices run the latest software versions.

SZTP is ideal for AI and Edge Clouds

AI factories rely on specialized processors, such as DPUs, to offload networking, storage, and security tasks from GPUs. Linux Foundation’s OPI project has adopted SZTP as a standard initialization method for these devices.

Here’s how SZTP simplifies AI and edge cloud deployment:

  • Device Identity and Trust Management

SZTP serves DPUs like DHCP did for laptops, answering questions crucial to trust: “Who are you?” and “Can you be trusted?” Use open-source libraries to develop trust protocols integrated with SZTP, enhancing the security posture.

  • Automated Secure Provisioning

Ensure your infrastructure is secure by default. Initiate hardware attestation, verify boot components, and use automated tools to deliver secure images and deploy cryptographic credentials. Platforms like HashiCorp Vault can manage secrets during this process.

  • Comprehensive Software Stack Deployment

SZTP allows for defining a device’s mission by automating the deployment of OS components, runtimes, and security agents. Leverage Docker and Kubernetes to handle container runtimes and orchestration, ensuring efficient management of service mesh layers and logging telemetries.

  • Scalable Client Implementations

Establish open-source client initiatives to enhance adoption. Encourage device manufacturers and OS vendors to integrate this client to promote SZTP adoption further and reduce integration complexity.

Conclusion

Open clients enabled DHCP to transform networking, and they will guide SZTP in defining secure, automated infrastructure’s next era for AI-enabled applications. Automate your edge and AI factory environments with SZTP, elevating digital trust to unprecedented levels.

By following these steps and leveraging SZTP technology, organizations can enhance their network security, automate deployment processes, and prepare their infrastructure for a future driven by AI and IoT.

The post Implementing Secure Zero-Touch Provisioning in AI and Edge Infrastructure appeared first on Linux.com.

Continue ReadingImplementing Secure Zero-Touch Provisioning in AI and Edge Infrastructure

From DHCP to SZTP – The Trust Revolution

By Juha Holkkola, FusionLayer Group

The Dawn of Effortless Connectivity

In the transformative years of the late 1990s, a quiet revolution took place, fundamentally altering how we connect to networks. The introduction of DHCP answered a crucial question, “Where are you on the network?”, by automating IP address assignment. This innovation eradicated the manual configuration nightmares, paving the way for seamless connectivity. Today, as digital trust becomes increasingly vital, a new revolution is emerging—one that demands an equally transformative approach: Secure Zero-Touch Provisioning (SZTP).

Trust: The Next Frontier

As we stand on the brink of this next wave of innovation, we recognize a pressing need to automate trust. Much like DHCP revolutionized connectivity, SZTP is poised to redefine security and trust in modern networking infrastructures. The digital landscape is evolving; spanning from cloud nodes and IoT sensors to AI-driven systems and intelligent robotics, the future of secure networking lies in our ability to trust devices automatically and unequivocally.

SZTP: Pioneering the Trust Paradigm

SZTP, as defined in RFC 8572, represents a groundbreaking shift in how we establish trust across diverse digital infrastructures. This open standard is vendor-neutral, heralding a universally adoptable solution fit for large-scale deployment. It automates trust by managing the exchange of secure artifacts and certificates, ushering in an era in which devices self-authenticate, receive verified firmware, and securely initialize without human intervention.

For organizations navigating the complexities of modern digital ecosystems, SZTP is more than a protocol; it’s a strategic approach equipped to handle the challenges of autonomous, scalable, and secure operations.

Unlocking Potential: AI and Edge Clouds

One of the most compelling use cases for SZTP is its application within AI data centers—environments now likened to future-ready AI factories. Here, devices such as DPUs (Data Processing Units) and IPUs (Infrastructure Processing Units) perform critical tasks by offloading networking and security operations from traditional GPUs, running complex, containerized workloads. With SZTP, these environments are provisioned and secured at unprecedented scales, aligning perfectly with the Linux Foundation’s Open Programmable Infrastructure (OPI) project’s standards.

Additionally, edge clouds represent a burgeoning frontier. As AI-driven applications demand lower latency, bringing operations geographically closer to end users becomes crucial. With SZTP, deployment at tens of thousands of sites becomes feasible, secure, and remarkably efficient, empowering next-generation applications from autonomous vehicles to immersive synthetic realities.

Strategic Pillars of SZTP Implementation

  1. From Addresses to Identity

Just as DHCP provides basic network connectivity, SZTP redefines the initial handshake with devices, answering the questions “Who are you?” and “What role do you play?” This trust-centric evolution reflects an essential shift towards identity verification and operational certainty from the outset.

  1. Secure-by-Default Provisioning

Establishing secure-by-default infrastructures is increasingly critical. SZTP ensures onboarding initiates with hardware attestation, swiftly evolving devices into secure nodes through verified boot processes, secure image delivery, and cryptographic credential injection.

  1. From Firmware to Mission-Centric Deployments

In advanced environments, SZTP delivers a complete software stack—it not only defines device roles across domains such as XR workloads and IoT pipelines but also simulates workloads pre-deployment to ensure readiness and optimal performance.

  1. Scaling Through Open Clients and Adoption

Industry-wide adoption of SZTP mirrors DHCP’s trajectory, necessitating robust open-source client solutions. The availability of open-source SZTP clients under permissive licenses is accelerating adoption across the ecosystem.

Driving the Secure Future

As digital networks extend their reach and capabilities, securing these environments becomes not just a priority but a necessity. SZTP shines as a beacon of innovation, demonstrating that with open standards and robust automation, trust can be as effortless as connectivity once was.

By nurturing open client ecosystems, SZTP doesn’t just promise enhanced digital trust; it actively defines what secure, automated infrastructure looks like in an AI-enabled world of applications. It lays the groundwork for what digital trust should be in future network paradigms, leading the charge into a new era of connectivity redefined by trust.

Moreover, adopting SZTP empowers organizations to innovate confidently, knowing their infrastructure is resilient and agile enough to handle growth and complexity. As businesses shift toward data-driven models and consumers demand more sophisticated digital interactions, SZTP ensures security and performance are uncompromised. Organizations embracing this strategy will secure operations and cultivate trust, enhancing customer relationships and accelerating digital transformation.

Looking ahead, SZTP is more than an implementation; it is pivotal for future-proofing the digital economy, setting new benchmarks for security, efficiency, and trust in the evolving technological ecosystem.

The post From DHCP to SZTP – The Trust Revolution appeared first on Linux.com.

Continue ReadingFrom DHCP to SZTP – The Trust Revolution