# Disk image A disk image is a file that contains data from a disk or other storage device and can be restored to another volume. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Hobby projects now retain fewer deployments to free up storage DevFeed: [Hobby projects now retain fewer deployments to free up storage]() Original publisher: [Read original article]() Author: Pranav Kanchi Published: 2026-09-16T18:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Deployment](), [Disk image]() Tags: [3](), [deployments](), [retention](), [storage](), [upgrade]() ### AI overview Vercel has changed Deployment Retention for Hobby teams. Each Hobby project now keeps its three most recent production deployments and three most recent deployments of any type, while some protected deployments remain exempt. Deployments outside the exceptions are deleted immediately when a team exceeds the 10GB storage limit. ### Source excerpt Hobby projects now retain fewer deployments past the 30-day retention window. Hobby teams get 10GB of Deployment Storage. Every deployment you keep uses some of it, and going over the limit can block you from deploying until you free some up. Deployment Retention for Hobby teams now deletes old deployments sooner, so dormant projects stop holding storage that your active projects need. Each Hobby project now keeps its 3 most recent production deployments, plus its 3 most recent deployments of any type, regardless of age. Preview deployments no longer get their own protection. Your current production deployment is still never deleted, and aliased and active-branch deployments are still protected. See the full list of exceptions in the docs. If your team is over the 10GB limit, deployments outside those exceptions are now deleted immediately instead of after 30 days. To stay under the limit, see how to optimize your Deployment Storage usage, or upgrade to Pro, where storage is billed at $0.10 per GB per month. Read more ## LTO Tape Shipments Up 57% in Q1 2026 as AI and Archive Demand Accelerate DevFeed: [LTO Tape Shipments Up 57% in Q1 2026 as AI and Archive Demand Accelerate]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-02T15:22:26Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [data](), [Disk image](), [Resilience](), [data centers](), [Artificial Intelligence](), [ibm]() Tags: [2026](), [ai](), [architectures](), [data](), [data-center](), [datasets](), [enterprise](), [enterprise-storage](), [hardware](), [ibm](), [report](), [resilience](), [retention](), [storage](), [training](), [upgrade]() ### AI overview LTO tape capacity shipments rose 57% year over year in Q1 2026, driven by continued LTO-9 adoption, the rollout of LTO-10, and growing enterprise data and archival needs. The article explains how tape supports economical cold storage, long-term retention, AI training datasets, and data center power constraints. ### Source excerpt The Linear Tape-Open (LTO) Program Technology Provider Companies, comprising Hewlett Packard Enterprise, IBM Corporation, and Quantum Corporation, have released their annual tape media shipment report. Following sustained enterprise data expansion, the report highlights a strong start to 2026, driven by continued LTO-9 adoption and the rollout and initial capacity ramp-up of LTO-10 media. According to The post LTO Tape Shipments Up 57% in Q1 2026 as AI and Archive Demand Accelerate appeared first on StorageReview.com. ## Introducing ReactOS 0.4.16 DevFeed: [Introducing ReactOS 0.4.16]() Original publisher: [Read original article]() Published: 2026-08-29T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [boot](), [Disk image](), [Graphics](), [OpenGL](), [Nvidia]() Tags: [boot](), [free](), [graphics](), [images](), [installation](), [networking](), [nvidia](), [open-source](), [opengl](), [os](), [react](), [reactos](), [release](), [storage](), [win32](), [winapi]() ### AI overview ReactOS 0.4.16 is announced after a year and a half of development. The release adds a graphical installer, combines the bootcd and livecd images, and includes improvements to video, audio, networking, storage, installation, and third-party code synchronization. ### Source excerpt We are pleased to announce the release of ReactOS 0.4.16! After a year and a half of development, we're excited to showcase the improvements we've made between a new graphical installer; a unified bootcd and livecd image; video, audio, networking, and storage stack improvements; a new installation type; and third-party code syncs. ## August 2026 Updates #2 for XCP-ng 8.3 LTS DevFeed: [August 2026 Updates #2 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: Samuel Verschelde Published: 2026-08-27T14:03:02Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [migration](), [Disk image](), [Kubernetes]() Tags: [2026](), [bug](), [bug-fixes](), [disk-space](), [kubernetes](), [lts](), [migration](), [storage](), [update](), [updates]() ### AI overview This article announces cumulative maintenance updates for XCP-ng 8.3 LTS. The release fixes storage-management bugs, including QCOW2 leaf-coalesce failures and LVM metadata corruption, and improves sparse QCOW2 virtual disk migration by reducing transfers and preserving VDI tags. ### Source excerpt New updates published: bug fixes related to storage management. ## August 2026 Updates #1 for XCP-ng 8.3 LTS DevFeed: [August 2026 Updates #1 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: Samuel Verschelde Published: 2026-08-18T16:22:04Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [Disk image](), [cloud-infrastructure](), [Software]() Tags: [bug-fixes](), [lts](), [maintenance](), [maintenance-updates](), [openssh](), [performance](), [storage](), [update](), [updates]() ### AI overview This article announces maintenance updates for XCP-ng 8.3 LTS. It explains the required rolling update process and highlights storage improvements, including live leaf coalescing for QCOW2, faster QCOW2 storage repository scans, and improved responsiveness for LINSTOR storage repositories. ### Source excerpt Maintenance updates for XCP-ng: storage performance and fixes, configurable OpenSSH, and much more. ## XCP-ng 8.3 LTS: Refreshed Installation ISOs DevFeed: [XCP-ng 8.3 LTS: Refreshed Installation ISOs]() Original publisher: [Read original article]() Author: Gaël Duperrey Published: 2026-08-14T08:09:13Z Content type: release Language: en Sources: [XCP-ng Blog]() Topics: [Server](), [Hardware](), [networking](), [Disk image]() Tags: [amd](), [drivers](), [hardware](), [improvements](), [installation](), [iso](), [linux](), [lts](), [networking](), [numa](), [performance](), [release](), [security](), [server](), [storage](), [update](), [updates]() ### AI overview XCP-ng 8.3 LTS has refreshed installation ISOs containing updates released since the previous installer, installer improvements, enhanced hardware support, and other fixes. The article notes that existing up-to-date hosts already include these changes. ### Source excerpt Refreshed ISOs for XCP-ng 8.3 LTS featuring the latest security updates, improvements, and QCOW2 support. ## Backblaze Drive Stats: How an Open Dataset Powers Academic and AI/ML Research DevFeed: [Backblaze Drive Stats: How an Open Dataset Powers Academic and AI/ML Research]() Original publisher: [Read original article]() Author: Stephanie Doyle Published: 2026-08-13T15:08:38Z Content type: article Language: en Sources: [Backblaze Blog | Cloud Storage & Cloud Backup]() Topics: [dataset](), [DRIVE](), [Machine learning](), [Transformer](), [Disk image]() Tags: [ai-ml](), [articles](), [b2cloud](), [cloud-storage](), [data](), [drive](), [featured](), [featured-cloud-storage](), [hard-drive-stats](), [ml](), [research](), [source](), [storage]() ### AI overview The article explains how Backblaze Drive Stats evolved from an internal hard-drive reliability tool into an open dataset used in academic and AI/ML research. It describes the dataset's real-world scale, quarterly publication, SMART attributes, labeled failures, broad manufacturer coverage, and use in hard-drive failure prediction research. ### Source excerpt Backblaze Drive Stats has been cited in more than 105 academic papers and AI/ML projects since 2018. Explore the research it powers and download the dataset. The post Backblaze Drive Stats: How an Open Dataset Powers Academic and AI/ML Research appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## UniFi Cloud Gateway Fiber: One Year Later DevFeed: [UniFi Cloud Gateway Fiber: One Year Later]() Original publisher: [Read original article]() Author: Rob Andrews Published: 2026-08-07T16:00:17Z Content type: opinion Language: en Sources: [NAS Compares]() Topics: [UniFi cloud gateway](), [Ubiquiti](), [networking](), [Routing (disambiguation)](), [Disk image](), [systems]() Tags: [10gbe](), [best-unifi-router-2026](), [cloud-gateway-fiber-vs-gateway-fiber](), [cloud-gateway-industrial-vs-ucg-fiber](), [cloud-gateway-max-vs-ucg-fiber](), [cloud-gateway-ultra-vs-ucg-fiber](), [dream-machine-beast-vs-ucg-fiber](), [dream-machine-pro-max-vs-ucg-fiber](), [dream-machine-pro-vs-ucg-fiber](), [dream-machine-se-vs-ucg-fiber](), [dream-router-5g-max-vs-ucg-fiber](), [dream-router-7-vs-ucg-fiber](), [efg-vs-ucg-fiber](), [enterprise-fortress-gateway-vs-ucg-fiber](), [gateway-fiber-vs-cloud-gateway-fiber](), [no-categories-best-unifi-gateway](), [routing](), [storage](), [systems](), [ubiquiti](), [ubiquiti-10g-router](), [ubiquiti-gateway-review](), [ubiquiti-ucg-fiber](), [ucg-fiber-2026](), [ucg-fiber-hardware-acceleration](), [ucg-fiber-nvme](), [ucg-fiber-one-year-later](), [ucg-fiber-performance](), [ucg-fiber-port-5-issue](), [ucg-fiber-pppoe](), [ucg-fiber-protect](), [ucg-fiber-review](), [ucg-fiber-sfp-plus](), [ucg-fiber-temperature](), [uncategorised](), [unifi-cloud-gateway]() ### AI overview A one-year review of the UniFi Cloud Gateway Fiber, a compact 10GbE gateway from Ubiquiti. The article describes its multi-gigabit routing, integrated UniFi controller, optional M.2 storage, and position between smaller desktop consoles and larger rackmount Dream Machine systems. ### Source excerpt UniFi Cloud Gateway Fiber - Still Great Value 1 Year On... The UniFi Cloud Gateway Fiber arrived in early 2025 as a compact 10GbE gateway positioned between Ubiquiti's smaller desktop consoles and its larger rackmount Dream Machine systems. It combined multi-gigabit routing, an integrated UniFi controller, optional M.2 storage and support for the wider UniFi [...] ## I Tried MX Linux on Raspberry Pi: Here's How to Install It DevFeed: [I Tried MX Linux on Raspberry Pi: Here's How to Install It]() Original publisher: [Read original article]() Author: Dhairya Parikh Published: 2026-08-06T03:06:03Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Linux](), [xfce](), [Disk image](), [Hardware](), [GUI](), [ssh]() Tags: [flash](), [guide](), [hardware](), [how-to-tutorials](), [linux](), [monitor](), [os](), [pi-4](), [raspberry-pi](), [raspberry-pi-os](), [ssh](), [storage](), [tools](), [tutorial]() ### AI overview A hands-on guide to installing MX Linux on supported Raspberry Pi models. It covers the required hardware and software, downloading the MX Linux image, flashing it to an SD card or USB stick, completing the first boot, and performing initial setup. The distribution is based on Raspberry Pi OS and uses XFCE as its desktop environment. ### Source excerpt I've wanted to try MX Linux on a Raspberry Pi for a long time, but until recently there simply wasn't an official way to install it. Now that that's changed, it's finally possible to see if this distribution is a good fit for the Pi. In this guide, I'll show you how to get it... ## Seamless Crash Protection That Symbolicates Native Crashes DevFeed: [Seamless Crash Protection That Symbolicates Native Crashes]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [GitHub Issues](), [Cloud](), [Disk image](), [Android](), [iOS](), [Linux](), [macOS](), [Windows](), [tvOS](), [watchOS]() Tags: [android](), [cloud](), [crash](), [data](), [github-issues](), [ios](), [linux](), [macos](), [native](), [protection](), [retry](), [storage](), [watchos](), [win32](), [windows]() ### AI overview The article describes the new com.codename1.crash client, which captures crashes on devices, removes personal data before transmission, stores reports until upload succeeds, retries failed uploads, and uses cloud-side symbolication to file deduplicated reports as GitHub issues. It covers native crash support across multiple platforms and deobfuscation of Android exceptions. ### Source excerpt The new com.codename1.crash client captures crashes on device, scrubs personal data before anything is sent, retries reliably through a storage-first queue, and lets the build cloud symbolicate native crashes and file them as GitHub issues instead of emails. ## Why we chose Turso to secure AI credentials DevFeed: [Why we chose Turso to secure AI credentials]() Original publisher: [Read original article]() Author: Devon Tietjen Published: 2026-06-16T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Turso](), [Disk image](), [Databases](), [API](), [cloud-infrastructure](), [Deployment](), [Latency](), [Artificial Intelligence]() Tags: [ai](), [api](), [databases](), [deployment](), [embedded](), [embedded-replicas](), [encryption](), [infrastructure](), [latency](), [local](), [on-prem](), [rust](), [security](), [telemetry](), [turso]() ### AI overview Eden uses Turso's encrypted embedded storage to keep sensitive control-plane state while deploying its infrastructure gateway close to the databases, APIs, AI endpoints, and internal tools it governs. This embedded approach reduces latency, network hops, external dependencies, and operational overhead, while supporting private, on-premises, air-gapped, and low-latency environments without requiring a separate Postgres deployment. ### Source excerpt How Eden uses Turso's encrypted embedded storage to hold sensitive control-plane state, so its gateway can run close to the databases, APIs, and AI endpoints it governs without standing up a separate Postgres. ## QCOW2 is now GA in XCP-ng DevFeed: [QCOW2 is now GA in XCP-ng]() Original publisher: [Read original article]() Author: Damien Thenot Published: 2026-05-05T17:29:49Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [Disk image](), [cloud-infrastructure]() Tags: [new-feature](), [news](), [production](), [qemu](), [release](), [standard](), [storage](), [test](), [update]() ### AI overview XCP-ng 8.3 makes QCOW2 production-ready for virtual disks up to 16 TiB, addressing the 2 TiB limit of VHD. VHD remains the default for smaller disks, while Xen Orchestra automatically selects QCOW2 for new disks larger than 2040 GiB. The release emphasizes stability, testing, and compatibility with existing storage repositories. ### Source excerpt QCOW2 is now GA in XCP-ng 8.3, supporting VM disks up to 16 TiB and replacing the 2 TiB VHD limit. Production-ready, stability-focused, with performance optimizations coming soon. ## Self-growing NixOS appliance images with systemd-repart DevFeed: [Self-growing NixOS appliance images with systemd-repart]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2025-10-03T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [systemd](), [Linux](), [Disk image](), [systems]() Tags: [boot](), [build](), [how-to](), [linux](), [partitions](), [systemd]() ### AI overview This tutorial explains how to build small, bootable NixOS appliance images with systemd-repart that expand to use the available disk during the first boot. It introduces the approach as part of a series covering image minimization, OTA updates, and cross-compilation. ### Source excerpt How to build small, self-inflating NixOS images with systemd-repart that automatically repartition to use the full disk on the first boot. ## Jupyter Notebooks on Heroku with Persistent Storage DevFeed: [Jupyter Notebooks on Heroku with Persistent Storage]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2025-04-02T06:54:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [jupyter](), [Disk image](), [PostgreSQL](), [Security](), [Retrieval Augmented Generation (RAG)]() Tags: [ai](), [cloud](), [cloud-infrastructure](), [data-analytics](), [developer-tools](), [heroku](), [jupyter](), [jupyter-notebooks](), [managed-inference-and-agents](), [news](), [open-source](), [pgvector](), [postgresql](), [python](), [rag](), [security](), [storage]() ### AI overview Heroku introduces Heroku-Jupyter, an open-source solution for running Jupyter Notebooks with persistent PostgreSQL storage, deployment support, password protection, and customizable environments. The article also describes using Heroku-Jupyter with pgvector and Heroku Managed Inference and Agents for retrieval-augmented generation applications. ### Source excerpt We're excited to introduce Heroku-Jupyter, an open-source, production-ready solution for running Jupyter Notebooks on Heroku with persistent storage, seamless deployment, and built-in security. Whether you're a data scientist, educator, or developer, you can now spin up a cloud-based Jupyter environment in minutes. Why Jupyter on Heroku? Jupyter Notebooks provide an interactive computing environment ideal for [...] The post Jupyter Notebooks on Heroku with Persistent Storage appeared first on Heroku. ## Database corruption in PostgreSQL: our journey to improving our upgrade process DevFeed: [Database corruption in PostgreSQL: our journey to improving our upgrade process]() Original publisher: [Read original article]() Author: Adyen Published: 2025-01-24T18:42:23Z Content type: article Language: en Sources: [Adyen Tech]() Topics: [PostgreSQL](), [Database](), [upgrade](), [Disk image](), [Transactions]() Tags: [adyen](), [backup](), [clusters](), [database-corruption](), [postgresql](), [scale](), [storage](), [toast-storage](), [transactions](), [upgrade]() ### AI overview Adyen engineers describe how corrupted PostgreSQL TOAST data surfaced after a database upgrade from version 9.6 to 13. The corruption affected millions of rows, could not be restored from a pre-upgrade backup, and led to a nearly year-long investigation into data access, detection, and upgrade-process improvements. ### Source excerpt by Cagri Biroglu & Derk van Veen, Database Engineers, Adyen PostgreSQL is a core component of Adyen's payment platform, enabling high-throughput, low-latency transaction processing on a global scale. Its stability, scalability, and extensibility make it a critical part of our infrastructure, supporting the reliability required for financial operations. A few years ago, we upgraded our PostgreSQL fleet from version 9.6 to 13. Upgrades are always long and tedious, but we prepared well for them, and the upgrade on even the hardest clusters with an extremely high number of TPS(transactions per second) and a size of multiple hundreds of TB(terabytes) went without major difficulties. But a few years later, we suddenly saw occasional errors related to transactions not being visible or invalid x_min or x_max. We tried to analyze the issue but didn't have much time, as transaction wraparound is always just around the corner in this environment. We had some quiet weeks, where no error was seen, and we thought that whatever it was, it was now behind us. We were wrong. TOAST storage The errors became a frequent nuisance, and we had no other option but to figure out what was happening. As it turned out, we had an issue with corrupted TOAST data entered in a table in the two weeks before we did the upgrade from 9.6 to 13 on this table's cluster. After the first analysis, we realized: This corruption affected millions of rows. We couldn't restore this table from a backup before the upgrade. If possible, we want to regain access to our data. We only knew about this corruption because of a clean-up job. It was unclear how many other tables were affected by the same issue. TOAST storage is not something we have understood and mastered yet. Transaction logic on TOAST is even more complicated than transaction logic on main tables. This is the start of a journey that will last almost a year. Background on TOAST storage Let's start with some background on TOAST data, as the corruptions a ## Migrating from 2 TByte SSD with MBR to 4 TByte with GPT DevFeed: [Migrating from 2 TByte SSD with MBR to 4 TByte with GPT]() Original publisher: [Read original article]() Author: Schakko Published: 2024-12-19T11:04:54Z Content type: tutorial Language: en Sources: [Schakko]() Topics: [Windows](), [UEFI](), [Disk image]() Tags: [boot](), [microsoft](), [partitioning](), [storage](), [uefi](), [uncategorized](), [upgrade](), [windows]() ### AI overview The article documents upgrading a Windows system from a 2 TByte SSD using MBR to a 4 TByte SSD using GPT. It explains that MBR's 2 TByte limit prevented full resizing and that UEFI booting required an EFI System Partition and an MSR partition. ### Source excerpt Yesterday I wanted to replace my 2 TByte SSD with a 4 TByte model as I was running out of hard drive space. My last upgrade two years ago from 1 TByte to 2 TByte went smoothly: I cloned the old SSD to the new SSD and then extended the [...] The post Migrating from 2 TByte SSD with MBR to 4 TByte with GPT appeared first on schakko.de. ## netlab 1.8.4: vrnetlab Containers, Catalyst 8000v DevFeed: [netlab 1.8.4: vrnetlab Containers, Catalyst 8000v]() Original publisher: [Read original article]() Published: 2024-06-24T05:43:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [releases](), [Containers](), [container images](), [Disk image](), [Testing](), [VXLAN](), [MPLS VPN]() Tags: [container](), [container-images](), [containers](), [mpls-vpn](), [netlab](), [release](), [releases](), [ssh](), [testing](), [vxlan]() ### AI overview The netlab 1.8.4 release adds support for vrnetlab containers for supported devices with available disk images, including Catalyst 8000v. It also introduces unified readiness checks and a handler for interruptions during long-running commands. VXLAN support for Catalyst 8000v is temporarily disabled, and MPLS/VPN was not tested. ### Source excerpt I don't think I ever created two netlab releases in a week, but last week, I stumbled upon a motherlode of goodies, and it would be a shame not to make them available. Someone tried to use netlab with vrnetlab containers for CSR 1000v and Nexus 9300v. We got it to work, but when I started integrating his changes into the development branch, I wanted to test them, so I installed vrnetlab to create my own container images. vrnetlab is an excellent tool, and building containers is a breeze (running them is a different story), so I added support for vrnetlab containers for every device supported by that tool and netlab for which I happened to have a disk image. Read more ... ## The Mythical Use Cases: Traffic Engineering for Data Center Backups DevFeed: [The Mythical Use Cases: Traffic Engineering for Data Center Backups]() Original publisher: [Read original article]() Published: 2024-06-11T10:41:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [datacenter](), [Disk image]() Tags: [backups](), [cisco](), [data-center](), [fabric](), [ipv6](), [network](), [routing](), [server](), [storage](), [tcp](), [traffic-engineering]() ### AI overview This commentary argues that high-volume in-band backups are an overstated justification for complex traffic-engineering features in data center fabrics. It explains that backup-server and storage performance, TCP session distribution, link ratios, dynamic load balancing, and routing can limit or spread the resulting traffic. ### Source excerpt Vendor product managers love discussing mythical use cases to warrant complex functionality in their gear. Long-distance VM mobility was one of those (using it for disaster avoidance was Mission Impossible under any real-world assumptions), and high-volume network-based backups seems to be another. Here's what someone had to say about that particular unicorn in a LinkedIn comment when discussing whether we need traffic engineering in a data center fabric. When you're dealing with a large cluster on a fabric, you will see things like inband backup. The most common one I've seen is VEEAM. Those inband backups can flood a single link, and no amount of link scheduling really solves that; depending on the source, they can saturate 100G. There are a couple of solutions; IPv6 or eBGP SID has been used to avoid these links or schedule avoidance for other traffic. It is true that (A) in-band backups can be bandwidth intensive and that (B) well-written applications can saturate 100G server links. However: Read more ... ## Lambda Snapstart, and snapshots as a tool for system builders DevFeed: [Lambda Snapstart, and snapshots as a tool for system builders]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2022-11-29T00:00:00Z Content type: opinion Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [Amazon Web Services](), [systems](), [cloud-infrastructure](), [Disk image](), [distributed-systems](), [boot](), [JIT](), [tracing](), [Cryptography]() Tags: [aws](), [boot](), [cpu](), [cryptography](), [distributed-systems](), [jit](), [memory](), [sandboxes](), [snapshots](), [storage](), [systems](), [tracing]() ### AI overview This article examines AWS Lambda Snapstart, which uses microVM snapshots taken after function initialization to reduce cold start times. It explains how cloned snapshots create multiple initialized sandboxes and discusses challenges around preserving uniqueness in systems that rely on random or unique values. ### Source excerpt Lambda Snapstart, and snapshots as a tool for system builders Clones. Yesterday, AWS announced Lambda Snapstart, which uses VM snapshots to reduce cold start times for Lambda functions that need to do a lot of work on start (starting up a language runtime3, loading classes, running static code, initializing caches, etc). Here's a short 1 minute video about it: Or, for a lot more context on Lambda and how we got here5: Snapstart is a super useful capability for Lambda customers. I'm extremely proud of the work the team did to make it a reality. We've been talking about this work for over two years, and working on it for longer. The team did some truly excellent engineering work to make Snapstart a reality. Beyond Snapstart in Lambda, I'm also excited about the underlying technology (microVM snapshots), and the way they give us (as system builders and researchers) a powerful tool for building new kinds of secure and scalable systems. In this post, I talk about some interesting aspects of Snapstart, and how they point to interesting possible areas for research on systems, storage, and even cryptography. What is Snapstart? Without snapstart, the cold start time of a Lambda function is a combination of time time taken to download the function (or container), to start the language runtime3, and to run any initialization code inside the function (including any static code, doing class loading, and even JIT compilation). The cold start time doesn't include MicroVM boot, because that time is not specialized to the application, and can be done in advance. A cold start looks like this1: With snapstart, a snapshot of the microVM is taken after these initialization steps (including all the memory, device state, and CPU registers). This snapshot can be used multiple times (also called cloned), to create multiple sandboxes that are initialized in the same way. Cloning like this has two benefits: The work of initialization is amortized over many sandboxes, rather than being done on ## Lightweight Linux Kernel Development with KVM DevFeed: [Lightweight Linux Kernel Development with KVM]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2013-12-30T02:11:45Z Content type: tutorial Language: en Sources: [Nelson Elhage]() Topics: [Development](), [kernels](), [Kernel](), [Disk image](), [Debian](), [Ubuntu](), [networking]() Tags: [debian](), [development](), [features](), [image](), [kernels](), [kvm](), [linux](), [linux-kernel](), [networking](), [ubuntu](), [virtio]() ### AI overview A practical workflow for Linux kernel development using lightweight virtual machines with KVM. It covers minimal kernel configuration, building a Debian userspace disk image, booting the guest with virtio, and configuring networking, with notes for different architectures. ### Source excerpt I don't do a ton of Linux kernel development these days, but I've done a fair bit in the past, and picked up a number of useful techniques for doing kernel development in a relatively painless fashion. This blog post is a writeup of the tools and techniques I use when developing for the Linux kernel. Nothing I write here is "the one way" to do it, but this is a workflow I've found to work for me, that I hope others may find useful. ## Newsletter 21 DevFeed: [Newsletter 21]() Original publisher: [Read original article]() Published: 2007-04-02T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Disk image](), [Kernel]() Tags: [compiler](), [free](), [news](), [open-source](), [os](), [project-news](), [react](), [reactos](), [storage](), [vmware](), [win32](), [winapi]() ### AI overview ReactOS Newsletter 21 reports project updates including a new storage stack based on NT4-DDK examples, SVN improvements, planned Google Code backups, contributor news, and work on native Structured Exception Handling support. ### Source excerpt Another newsletter I am glad I am able to bring you the latest news about ReactOS through this newsletter. It is the purpose of this newsletter to inform everyone of the recent work and notable highlights of this great project. It is my hope that you will find it useful and informative. (Insert license agreement indicating no particular usefulness, assorted legal wording and notices here... Just kidding!) Project News New storage stack based on NT4-DDK examples implemented in trunk, fixes booting on VmWare and several other nasty bugs.