<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Administration on The Coders Blog</title><link>https://thecodersblog.com/tag/system-administration/</link><description>Recent content in System Administration on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 16:59:24 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/system-administration/index.xml" rel="self" type="application/rss+xml"/><item><title>Reviving Sun Ray: Setting Up on OpenIndiana Hipster</title><link>https://thecodersblog.com/sun-ray-server-on-openindiana-hipster-2026/</link><pubDate>Wed, 06 May 2026 16:59:24 +0000</pubDate><guid>https://thecodersblog.com/sun-ray-server-on-openindiana-hipster-2026/</guid><description>&lt;p&gt;You’ve got a box of dusty Sun Ray clients, a lingering fondness for Solaris, and a hankering to make it all work on something modern. Welcome to the reality of setting up a Sun Ray server on OpenIndiana Hipster 2025.10. It’s a journey paved with good intentions, older software, and a surprising amount of manual intervention.&lt;/p&gt;
&lt;h3 id="the-core-problem"&gt;The Core Problem&lt;/h3&gt;
&lt;p&gt;The fundamental challenge is bringing a once-cutting-edge, now unsupported thin-client solution into the modern era. Oracle discontinued Sun Ray support in 2014, and while OpenIndiana Hipster has made strides in Sun Ray support, it’s far from a plug-and-play experience. You&amp;rsquo;re essentially resurrecting a proprietary, legacy system on an open-source, actively developed OS.&lt;/p&gt;</description></item><item><title>[Security Breakdown]: Ubuntu's 15+ Hour DDoS - Lessons for Every Developer [2026]</title><link>https://thecodersblog.com/ubuntu-s-extended-ddos-outage-2026/</link><pubDate>Fri, 01 May 2026 11:21:29 +0000</pubDate><guid>https://thecodersblog.com/ubuntu-s-extended-ddos-outage-2026/</guid><description>&lt;p&gt;April 30, 2026: 6 PM UK time. Ubuntu&amp;rsquo;s core services, the very bedrock for millions of developers, started crumbling under a sustained DDoS assault. This wasn&amp;rsquo;t just a hiccup; it was a &lt;strong&gt;15+ hour security breakdown&lt;/strong&gt;, a stark reminder that even the giants can be brought to their knees. This incident isn&amp;rsquo;t merely a cautionary tale for Canonical; it&amp;rsquo;s a blueprint for understanding and hardening your own defenses against the inevitable.&lt;/p&gt;</description></item><item><title>Linux 7.0: How a Kernel Preemption Bug Crippled PostgreSQL Performance in 2026</title><link>https://thecodersblog.com/linux-kernel-7-0-preemption-regression-impact-on-postgresql-2026/</link><pubDate>Wed, 29 Apr 2026 16:57:18 +0000</pubDate><guid>https://thecodersblog.com/linux-kernel-7-0-preemption-regression-impact-on-postgresql-2026/</guid><description>&lt;p&gt;In April 2026, the Linux Kernel 7.0 release promised evolutionary advancements, but for PostgreSQL users, it delivered a brutal, silent performance regression, abruptly halving throughput on critical production workloads without a single error message.&lt;/p&gt;
&lt;h2 id="the-silent-killer-how-linux-70-blindfolded-postgresql"&gt;The Silent Killer: How Linux 7.0 Blindfolded PostgreSQL&lt;/h2&gt;
&lt;p&gt;The eagerly awaited release of Linux Kernel 7.0 in early 2026 was met with the usual anticipation within the open-source community. Touted for its efficiency improvements and new hardware support, it was expected to be a solid, if not revolutionary, upgrade. Yet, for database administrators and cloud engineers managing high-performance PostgreSQL instances, it brought an unforeseen and devastating impact.&lt;/p&gt;</description></item></channel></rss>