DevOps’ish 308: Actively Exploited, Actively Litigated, Actively Useless
- 2.8 builds cleanly with recent glibc. Most notably, these include fixes for Linux kernel I/O vector array overrun (CVE-2015-1805) and OpenVZ container escape (CVE-2015-2925), glibc GHOST (CVE-2015-0235), OpenSSL FREAK (CVE-2015-0204), and BIND TKEY query DoS (CVE-2015-5477). New Owl safety updates can be found in the type of supply code, 78 win RPMs, ISOs, and OpenVZ container templates addressing CPU, https://djalexhino.com Linux kernel, and procps points. Your Container Is just not a Sandbox: https://ncrpad.com The State of MicroVM Isolation in 2026 – A transparent-eyed evaluation of how Rust-based mostly microVM monitors provide real hardware-isolated security boundaries, https://7ba.biz and why containers, which share a kernel, nonetheless fall quick for untrusted workload execution regardless of years of hardening.
Join IaCConf 2026 to listen to from the people building this shift on May 14th at 11 am ET. It’s 2026. Platform engineering is shifting. The “Negative Split” Software Engineering Effect – Drawing from marathon strategy, the argument is that engineering teams should intentionally begin slower to build better foundations. Join builders, platform engineers, DevOps practitioners, engineering leaders, and cloud fanatics for the third edition of Romania’s neighborhood-driven Cloud Native Days, bringing sensible Kubernetes use instances and fashionable cloud native systems to the stage.
LKRG 0.2 is out, with added support for loading at early boot stage (e.g., from initramfs), reduced efficiency influence, and bugs fastened.
This is a chance for HPC (High Performance Computing) hobbyists alike to program for a heterogeneous HPC platform. Do the performance benefits hold for other duties than counting upwards? What exactly does the loop counting upward seem like, and on what machine (32 or 64 bits) did you strive? No, 78win we have not even made any prereleases yet, but the essential bits have landed in master. The plan is to have the compiler emit some shuffles in this case, however I haven’t hit it but, and it was too tough to attempt to get proper in the bootstrapping phase.
Get began with Voxtral TTS! You know what number of arguments you get by the distinction between the stack pointer (SP) and the body pointer (FP). But how did Ruby’s rubbish collector know this, 78 win precisely? This meant all the new arrays were in actual fact nonetheless being used and Ruby’s garbage collector couldn’t reclaim their memory.
Let’s check out Ruby’s rubbish collection course of next.I’ve started working on a new version of Ruby Under a Microscope that covers Ruby 3.x. I’m engaged on this in my spare time, so it’s going to take some time. At the identical time, we’ve made the first pre-compiled snapshot of Owl 3.