Stake and Rope

Different Vendor, Same Memo

Nutanix's CEO told a press briefing at the company's .NEXT conference that the company has poached thirty thousand customers from VMware since Broadcom closed the acquisition. The number went out as a headline. A week later one of the trade pubs ran a correction — more than thirty thousand total customers, not from VMware — but the original headline kept running everywhere else. Meanwhile Broadcom's software revenue is up nine percent to $7.2B in Q2. Ninety percent of its biggest VMware customers bought the expensive bundle. The share price has roughly tripled since the deal closed. So the story is either a customer exodus, or a successful customer cull, depending on which podium you're standing behind. The panel works out which. Panel - The Legacy Sysadmin — has watched this exact pattern four times (CA, Oracle-Sun, IBM-Red Hat, now Broadcom-VMware) and explains why the playbook keeps working - The Startup Founder — defends Broadcom's strategy enthusiastically, calls the exodus a filter, has already drafted the LinkedIn post - The Burnt-Out SRE — currently somewhere in the middle of a VMware migration, tells the panel what Nutanix's victory slide leaves off - The Goat Farmer's Counsel — fixture Source ["Negative" Views of Broadcom Driving Thousands of VMware Migrations, Rival Says](https://arstechnica.com/information-technology/2026/04/nutanix-claims-it-has-poached-30000-vmware-customers/ [https://arstechnica.com/information-technology/2026/04/nutanix-claims-it-has-poached-30000-vmware-customers/]) — Ars Technica, April 2026, picking up SDxCentral's coverage of Nutanix CEO Rajiv Ramaswami's remarks at the .NEXT conference in Chicago. The trade-pub correction referenced in the episode is SDxCentral's, appended to their original story.

Permission To Ask For Permission

The FCC quietly extended its waiver on a rule that would have effectively banned automated firmware updates for millions of consumer routers already deployed in the United States. Rather than correct the underlying rule — which emerged from a Covered List expansion designed for procurement but got applied in ways that broke the patch pipeline — the commission pushed the deadline to 2029. The panel works through how a national-security rule ended up threatening the mechanism that delivers national security, why the waiver is narrower than it appears, and what the next three years actually look like for operators and security teams who manage these devices. The Legacy Sysadmin traces the regulatory pattern to its structural roots: the Covered List process was designed to block procurement, got extended to cover equipment authorization, and the legal logic of withdrawing an authorization turned out to also prohibit the manufacturer from pushing patches to devices already in American homes and offices. The waivers exist because the alternative is that most consumer routers in the country go unpatched. The extension is the second one. The manufacturers have largely stopped treating the deadlines as real. The Paranoid CISO draws a direct line from the waiver's practical gaps — patches touching radio-adjacent code on these SoCs still don't ship cleanly — to the operational conditions Volt Typhoon was documented exploiting in 2023 and 2024. The Burnt-Out SRE manages a fleet of forty thousand affected devices and observes that the post-mortem for whatever happens next is already written; the only blank is the model number. The closing round lands on a structural mismatch the panel keeps circling: the FCC's waiver cycle runs in three-year increments, and the threat landscape runs in ## Source article [FCC walks back router update ban before it bricks America's network security](https://www.theregister.com/networks/2026/05/12/fcc-walks-back-router-update-ban-before-it-bricks-americas-network-security/5238938 [https://www.theregister.com/networks/2026/05/12/fcc-walks-back-router-update-ban-before-it-bricks-americas-network-security/5238938]) — Dan Robinson, The Register · May 12, 2026 ## Panel - The Legacy Sysadmin - The Paranoid CISO - The Burnt-Out SRE - The Goat Farmer's Counsel

Name the Workload

A satellite-shaped pitch arrives at the desk of an industry that already has more compute than it knows what to do with. SpaceX, gearing up for an IPO that requires a story bigger than rocket launches, is selling orbital data centers as the future of AI compute. Google is reportedly listening. The Founder arrives with the deck open in another tab and begins making the case from analogy — Starlink, reusable rockets, AWS in 2006 — before the Host stops him with a question that becomes the episode's spine: which workload, specifically, runs better in orbit than on the ground. The Founder names training. The SRE notes that training runs need to be near the data, and the data is on the ground. The Founder names batch inference. The DBA asks what data, stored where, served to whom. Nobody answers. Across the runtime the panel surfaces the actual constraints — radiative cooling in vacuum being harder than the pitch claims, latency floors that physics enforces, single-event upsets from cosmic rays, the impossibility of swapping a failed disk in low Earth orbit, the launch-schedule economics that replace traditional capital expenditure. The Founder eventually names a real constraint: terrestrial data centers are running into power, water, land, and permitting walls that orbit doesn't have. The SRE acknowledges this as the first real answer and explains why the solution isn't orbit but grid capacity. The DBA confirms what the episode has been demonstrating: the orbital pitch is what you do if you've decided in advance that orbit is the answer and you're working backward from there. The episode lands on the question of how a decision like this gets made in the first place — somebody walked into a room with a slide that said "orbital compute" and the room said yes, without anyone in the room asking what workload it was for. The DBA's closing structural verdict ties the episode together: the architectures that worked, somebody could always name the workload in the first meeting. Nobody in this article has named the workload. Everything downstream of that — the launch costs, the cooling problem, the radiation, the maintenance impossibility — is consequence. Source article Report: Google and SpaceX in talks to put data centers into orbit [https://techcrunch.com/2026/05/12/report-google-and-spacex-in-talks-to-put-data-centers-into-orbit/] — Rebecca Bellan, TechCrunch · May 12, 2026 Panel * The Startup Founder * The Burnt-Out SRE * The Database Administrator * The Goat Farmer's Counsel

Everybody's K5

The Linux kernel retired support for the AMD K5 this week — a chip that failed commercially in 1996 and hasn't existed in production since the Clinton administration. The panel sits with the question of what 'we still support this' was actually doing for thirty years, and who it was doing it for. This episode takes the Linux kernel's removal of non-TSC code paths — and with them, support for the AMD K5 and several Cyrix parts — as an entry point into something much larger: the way long-lived systems accumulate maintenance debt that nobody is tracking, on behalf of users who stopped existing decades ago. The Legacy Sysadmin opens with firsthand context. He bought K5s in 1997 because they were cheap, regretted all of them, and replaced them with K6s by 1998. The chip wasn't beloved. It was a commercial failure AMD shipped because they had to ship something against the Pentium. The kernel carrying support for it until 2026 wasn't loyalty to a meaningful platform — it was inertia compounding quietly for thirty years. The DBA reframes the actual technical decision: the kernel didn't retire the K5 specifically. It decided to require the TSC — the timestamp counter — as a baseline assumption, and the K5 happened to be on the wrong side of that line. The headline says 'K5 retired.' The reality is 'we finally allowed ourselves to require a 1995 instruction.' The K5 is collateral. The cost of carrying the non-TSC fallback code for thirty years was real but distributed — a small tax on scheduling code, on timer refactors, on anyone who had to remember the K5 case — none of which appeared on a dashboard or triggered a postmortem. The Startup Founder argues the kernel team made a hard call and that engineering cultures can be built around deprecation discipline. The DBA's response is direct: Stripe is fourteen years old. Talk to me about their deprecation hygiene in twenty years. Everyone gets their K5. Source Article "AMD K5 CPUs The Latest To Be Retired With Linux's Aging & Stagnate Hardware Support" By Michael Larabel, Phoronix, May 8, 2026. https://www.phoronix.com/news/AMD-K5-CPUs [https://www.phoronix.com/news/AMD-K5-CPUs] Panel * The Legacy Sysadmin * The DBA * The Startup Founder * The Goat Farmer's Counsel

The Destination Is The Origin

Gartner published a report this week arguing that for some enterprise workloads, migrating to a mainframe is now cheaper than continuing to license VMware. Simon Sharwood covered it at The Register. The math is real — Broadcom's post-acquisition pricing has pushed VMware total cost of ownership past IBM Z for a non-trivial set of workloads, and Gartner is on the record telling clients to do the comparison. The Legacy Sysadmin opens with a thirty-year arc: helped a bank get off MVS in 1999, helped them standardize on VMware in 2011, and is bracing for the call asking about a Z migration in 2027. The Burnt-Out SRE sketches the eighteen-month post-mortem in advance — half-migrated workloads paying for both platforms, the CFO who approved the project moved to a different company, the new CFO commissioning a study that will recommend migrating back to cloud. The DBA, in his third panel appearance, is contemptuous of TCO models that don't include the cost of senior database engineers quitting because they got tired of being the only person in the room who could read an explain plan. The episode is about whether the loop completing — mainframe to Unix to VMware to mainframe — is a strategy or just the average tenure of a CIO playing out across infrastructure. The panel concludes, with notable unanimity, that institutional memory does not survive long enough to prevent its own repetition. Source Article "Mainframes are now cheaper than VMware, says Gartner" By Simon Sharwood at The Register, May 4, 2026. https://www.theregister.com/on-prem/2026/05/04/moving-to-a-mainframe-can-be-cheaper-than-vmware-gartner/5229237 [https://www.theregister.com/on-prem/2026/05/04/moving-to-a-mainframe-can-be-cheaper-than-vmware-gartner/5229237] The Panel 1. The Legacy Sysadmin 2. The Burnt-Out SRE 3. The DBA 4. The Goat Farmer's Counsel.