Transactional system upgrades without compromise
Source: Hugo's weblog on WhyNotHugo (雨果) ·
This article is about two desirable traits in system upgrades: atomicity and being able to roll back. Atomicity: the upgrade is either applied in full or not applied at all. The system is not left in a broken state because, e.g., “the package manager updated half of the files and then died”. This includes situations like a power failure mid-upgrade. Rollback-capable: if a system upgrade fails, or doesn’t work, it’s still possible to use the device in a previous system state. These two traits dramatically increase the reliability of a device that’s updated in the f
Frequently Asked Questions
What is Transactional system upgrades without compromise?
Transactional system upgrades without compromise is a article discovery curated from Hugo's weblog on WhyNotHugo (雨果). This article is about two desirable traits in system upgrades: atomicity and being able to roll back. Atomicity: the upgrade is either applied in full or not applied at all. The sy
How can I access or experience this?
You can experience this content directly on its original host (Hugo's weblog on WhyNotHugo (雨果)) by clicking the "Open Original" button.
Where does this content come from?
Curated from Hugo's weblog on WhyNotHugo (雨果) by the OnSuggest team to surface the most interesting and serendipitous content on the web.
More like this
All Article discoveries →9th November 2026 at 10:04
Equal parts mad and impressed at this ad Monzo inserted under my phone bill
Two Cents Off Pi
He told me this one as a joke he makes to himself, which is how you know it’s real. 312 is 314 after giving its two cents. Take pi, 3.14, subtract two hundredths, and you get 3.12. A throwaway line, the kind of thing you say to yourself in a grocery line.
Minimal WebRTC handshake
Author's note: drafted by Deepseek v4.1 Flash The 23-Byte WebRTC Handshake How small can a browser-to-browser WebRTC handshake get? I spent a weekend measuring it in Chromium 157 (Microsoft Edge) and Safari 26.2. The short answer: 23 bytes per direction, if you're willing to make a few very specific assumptions. The 2015 answer was 106 characters In 2015, Philipp Hancke wrote a great piece called The Minimum Viable SDP . The question was simple: how much do two browsers actually need to exchange before a DataChannel works? The answer was about 106 characters per direction: O,<ufrag>,<pwd>,<bas
Arlington National Cemetery
Podcast Transcript On a hillside overlooking Washington, DC, sits one of the most sacred sites in the United States. It is the final resting place of presidents, generals, and hundreds of thousands of Americans who served their country. Yet, its origins are deeply intertwined with slavery, the Civil War, and a bitter legal dispute involving ... Read more
$1bn start-up Rillet makes London its first European base
Rillet, a US start-up that makes accounting software with built-in AI agents, has opened an office in central London. It is the company’s first major move into Europe, Rillet said on Monday. Customers in the UK and the rest of Europe already account for 15% of Rillet’s new annual recurring revenue, the company said. They […] This story continues at The Next Web