中文 English Français Русский Español العربية

Buildroot 2026.08 released

jzb LWN.net 2026-09-07 21:18 20 views

Version 2026.08 of the Buildroot embedded Linux system builder has been released. Buildroot 2026.08 includes nearly 1,000 changes from 100 contributors; some of the notable changes include support for Linux 7.1.x, Binutils 2.46.1, GCC 16.2.0, glibc 2.44, as well as adding the M68K and IBM Power 10/11 architectures.

Read original: https://lwn.net/Articles/1092913/

My Favorites →

← Previous Security updates for Monday Next → Browser-side chaos testing with a Service Worker

Upgrading a Locked-Down Linux Fleet with Nothing but kubectl

Say you're running a fleet of machines on an immutable operating system — root filesystem read-only, nothing drifts, and you upgrade the whole OS as a single artifact instead of patching it in place. Great for reliability. But now you need to do something mundane: rotate a login password across eve

DevOps 09-15 53 Dev.to (EN Zone)

PasteSwitch: 108 crypto-theft ads on a hijacked HBO Max Reddit account

Attackers hijacked the official verified HBO Max account on Reddit, u/hbomax, and used it to run 108 distinct malicious advertisements over roughly 48 hours. The ads promoted an "HBO Max for macOS" application that does not exist. Reddit administrators paused the affected ads and opened an internal

DevOps 09-15 39 DEV Community

Code Hosting vs CI/CD: GitHub Actions, GitLab CI, Jenkins, CircleCI, Argo Workflows and More — What Actually Fits Your Stack?

I used to think GitHub Actions, GitLab CI, Jenkins, CircleCI and TeamCity were basically the same thing with different YAML syntax. They're not. The bigger distinction is: Code hosting ≠ CI/CD ≠ workflow orchestration. GitHub → GitHub Actions GitLab → GitLab CI/CD Bitbucket → Bitbucket Pipelines Az

DevOps 09-14 40 Dev.to (EN Zone)

My build finished in 0 seconds and thirteen test suites passed. They had run yesterday's binary.

The verification step for this project cannot run where the source lives. The toolchain is unusable on that filesystem, so the pipeline mirrors the tree onto a Linux volume and builds there, then runs the control suites against what it built. That day the log read: BUILD exit=0 seconds=0 T

DevOps 09-14 37 DEV Community

Comments0

No comments yet — be the first