# Filesystems A computing concept that provides persistent storage and organizes files through directories. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Persistent Databases in the Browser with DuckDB-Wasm and OPFS DevFeed: [Persistent Databases in the Browser with DuckDB-Wasm and OPFS]() Original publisher: [Read original article]() Author: Carlo Piovesan, Geertjan Wielenga Published: 2026-09-18T00:00:00Z Content type: tutorial Language: en Sources: [DuckDB]() Topics: [DuckDB](), [wasm](), [Filesystems](), [browser](), [Databases]() Tags: [browser](), [cli](), [databases](), [duckdb](), [file-system](), [npm](), [parquet](), [python](), [using-duckdb](), [wasm]() ### AI overview This tutorial explains how DuckDB-Wasm can persist browser databases in the Origin Private File System (OPFS), including version requirements, reload behavior, database files, and checkpointing. ### Source excerpt DuckDB-Wasm can open a persistent database file in the browser's Origin Private File System (OPFS). This post shows how, and when data reaches disk. ## Laravel Scalpel Scans for Filesystem Intrusion Evidence DevFeed: [Laravel Scalpel Scans for Filesystem Intrusion Evidence]() Original publisher: [Read original article]() Author: Yannick Lyn Fatt Published: 2026-09-17T01:38:29Z Content type: article Language: en Sources: [Laravel]() Topics: [Laravel](), [Filesystems](), [Security](), [backdoor](), [PHP]() Tags: [backdoor](), [filesystem](), [laravel](), [laravel-packages](), [php](), [security](), [sha-256]() ### AI overview Laravel Scalpel is an intrusion-evidence scanner that runs inside Laravel applications. It checks filesystems for rogue PHP files, obfuscated code, altered server directives, environment issues, and changes from a trusted baseline. ### Source excerpt Laravel Scalpel scans Laravel filesystems for rogue PHP files, obfuscated backdoors, altered directives, environment issues, and file changes. The post Laravel Scalpel Scans for Filesystem Intrusion Evidence appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions DevFeed: [Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions]() Original publisher: [Read original article]() Author: Nispriha Jagan; Neeraj Krishna Gopalakrishna Published: 2026-09-16T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [mount](), [Filesystems](), [chmod](), [Unix]() Tags: [chmod](), [container](), [containers](), [filesystem](), [hardening](), [kubernetes](), [linux](), [mount](), [permissions](), [storage](), [volume](), [volumes]() ### AI overview Kubernetes v1.37 adds bind mount options and emptyDir permission modes to strengthen storage security. The article explains how noexec, nosuid, nodev, Unix permissions, and the sticky bit can help enforce security policies on writable volumes. ### Source excerpt Kubernetes v1.37 brings important storage security features: emptyDir permission modes and bind mount options. They help application programmers and security professionals implement rigorous security policies, for example, prohibiting deletion of files across containers or execution of arbitrary binaries from writable volumes, directly in Kubernetes without any complicated circumvention. Linux storage and permission fundamentals Before diving into the new Kubernetes features, let us briefly review the low-level Linux security mechanisms that make them possible. Bind mount flags When Linux mounts or remounts a directory, Virtual File System (VFS) flags control what actions are permitted on that filesystem: noexec: Do not permit direct execution of any binaries on the mounted filesystem. nosuid: Do not allow set-user-identifier or set-group-identifier bits to take effect. nodev: Do not interpret character or block special devices on the file system. Directory permissions and the sticky bit Standard Unix permissions regulate access across three scopes: Owner, Group, and Others (e.g., 0755 or 0777). Beyond standard read, write, and execute bits, Linux supports the sticky bit (as in mode 01777). When applied to a directory, the sticky bit ensures that a file inside that directory can only be deleted or renamed by the file's owner or root. This is essential for shared writable directories like /tmp. Motivation for the improvements Why does Kubernetes need bind mount options and emptyDir permissions? The primary goal of these features is to increase the security of Kubernetes workloads by allowing security-related bind mount options on volume mounts. By default, volumes are bind-mounted into containers by the container runtime and kubelet without noexec, nosuid, or nodev flags. This default can undermine security. For example, with noexec missing, a compromised process can use any writable volume (emptyDir, PersistentVolume, etc.) to download, chmod +x, and execute arbitra ## Crash-Safe & Copy-On-Write GEFS As The "Good Enough File-System" For OpenBSD DevFeed: [Crash-Safe & Copy-On-Write GEFS As The "Good Enough File-System" For OpenBSD]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T13:42:00Z Content type: article Language: en Sources: [Phoronix]() Topics: [Filesystems](), [file]() Tags: [crash](), [desktop-linux](), [file](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [porting](), [preview](), [production](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Ori Bernstein announced an early preview of GEFS, a crash-safe, snapshotting, copy-on-write file system originally developed for 9front and now being ported to OpenBSD. The OpenBSD port is not yet production-ready or submitted for inclusion in the OpenBSD tree. ### Source excerpt Ori Bernstein announced an early preview of his Good Enough File-System "GEFS" for OpenBSD. GEFS is a crash-safe, snapshotting, copy-on-write file-system that he wrote initially for 9front and now porting to OpenBSD... ## Announcing Fedora Linux 45 Beta DevFeed: [Announcing Fedora Linux 45 Beta]() Original publisher: [Read original article]() Author: Aoife Moloney Published: 2026-09-15T14:05:00Z Content type: release Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Linux](), [dnf](), [podman](), [pandas](), [Python](), [gcc](), [Go Language](), [MariaDB](), [MySQL](), [Filesystems]() Tags: [2026](), [dnf](), [fedora-project-community](), [filesystems](), [gcc](), [go](), [linux](), [mysql](), [pandas](), [partitioning](), [podman](), [pre-release](), [python](), [release](), [toolchains]() ### AI overview Fedora Linux 45 Beta is available for download or upgrade on September 15, 2026. The release includes changes to the kernel console, package signature verification, desktop secret management, software versions, Atomic Desktop image builds, Fedora CoreOS swap support, Anaconda installation flows, and Stratis filesystem partitioning. ### Source excerpt Fedora Linux 45 Beta is here! On Tuesday, 15 September 2026 you can download or upgrade your systems from your usual spots to start enjoying what F45 has to offer early. How to get the beta release You can download F45 Beta, or our pre-release edition versions, from any of the following places: You can [...] ## Just 4.4% of Enterprise NAS Capacity Is Active, CTERA Cold Data Storage Report Finds DevFeed: [Just 4.4% of Enterprise NAS Capacity Is Active, CTERA Cold Data Storage Report Finds]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-15T12:00:00Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [data](), [Filesystems](), [Security](), [Replication](), [Artificial Intelligence]() Tags: [data](), [enterprise](), [enterprise-nas](), [enterprise-storage](), [nas](), [report](), [security](), [storage]() ### AI overview StorageReview reports on CTERA's Cold Data Storage Report, which analyzed 16 petabytes of production data from 856 enterprise NAS file-share discovery scans. The report found that 4.4% of stored capacity was actively used within 90 days, while most files were cold or inactive. The article discusses the resulting storage, data-protection, security, and AI-retrieval implications. ### Source excerpt CTERA has published The Cold Data Storage Report, an analysis of 16 petabytes of live production data across 856 file-share discovery scans in enterprise NAS environments, including regulated industries, and the headline number is that just 4.4% of stored capacity is actively used, which the report page defines as modified within a 90-day window. The The post Just 4.4% of Enterprise NAS Capacity Is Active, CTERA Cold Data Storage Report Finds appeared first on StorageReview.com. ## GNU Coreutils 9.12 Released With Performance Optimizations, New uname Option DevFeed: [GNU Coreutils 9.12 Released With Performance Optimizations, New uname Option]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T17:45:05Z Content type: news Language: en Sources: [Phoronix]() Topics: [systems](), [Filesystems](), [Optimization](), [bug](), [chmod](), [ls]() Tags: [bug](), [chmod](), [core](), [desktop-linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [ls](), [open-source-graphics](), [optimization](), [performance](), [phoronix](), [phoronix-test-suite](), [release](), [systems](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview GNU Coreutils 9.12 fixes recursive traversal failures when files are removed concurrently, adds FailFS and NULLFS support to stat and tail, and introduces new uname labeling options. It also improves performance in cut, uniq, and sort, adds a copy fallback for cp, install, and mv, and includes additional bug fixes and warnings. ### Source excerpt GNU Coreutils 9.12 released today with a mix of fixes, some new options, and various performance improvements to these widely-used set of core system utilities... ## Why didn't ReadDirectoryChangesW provide a way to correlate the two sides of a rename operation? DevFeed: [Why didn't ReadDirectoryChangesW provide a way to correlate the two sides of a rename operation?]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-14T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Filesystems](), [systems]() Tags: [concurrent](), [events](), [files](), [ids](), [implementation](), [information](), [old-new-thing](), [other](), [post](), [systems]() ### AI overview The article explains why ReadDirectoryChangesW did not explicitly provide a mechanism for correlating the two events generated by a file rename. It suggests that the events were expected to occur consecutively, but that assumption was never documented and could fail when concurrent renames or disk activity interleave events. File IDs provide the information needed to correlate the two sides reliably. ### Source excerpt Perhaps it wasn't necessary, or perhaps it didn't occur to them that this a problem. The post Why didn't ReadDirectoryChangesW provide a way to correlate the two sides of a rename operation? appeared first on The Old New Thing. ## BFS File-System Being Removed For Linux 7.4 DevFeed: [BFS File-System Being Removed For Linux 7.4]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T11:03:26Z Content type: news Language: en Sources: [Phoronix]() Topics: [Filesystems](), [Linux](), [kernels](), [Unix](), [boot]() Tags: [boot](), [bootloader](), [desktop-linux](), [filesystem](), [filesystems](), [kernels](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [os](), [phoronix](), [phoronix-test-suite](), [systems](), [technical](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview BFS, the obsolete UnixWare boot-partition filesystem, is slated for removal from the Linux kernel in version 7.4. The article cites its extremely limited functionality, lack of likely users, and broader efforts to reduce maintenance burdens from rarely used filesystems. ### Source excerpt The latest upstream file-system to be removed from the mainline Linux kernel is... BFS... ## EROFS Disables LZ4 Rolling Decompression Due To Data Corruption Possibility DevFeed: [EROFS Disables LZ4 Rolling Decompression Due To Data Corruption Possibility]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T00:33:00Z Content type: news Language: en Sources: [Phoronix]() Topics: [Filesystems](), [systems](), [Optimization](), [Linux](), [data](), [Containers]() Tags: [containers](), [data](), [desktop-linux](), [embedded](), [embedded-systems](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [memory](), [open-source-graphics](), [optimization](), [phoronix](), [phoronix-test-suite](), [reduce](), [systems](), [ubuntu-benchmarks](), [ubuntu-hardware](), [x86]() ### AI overview EROFS has temporarily disabled LZ4 rolling decompression because a rare interaction with the upstream LZ4 implementation could produce corrupted data. The change prioritizes data correctness in production but increases runtime memory usage. ### Source excerpt The EROFS read-only file-system popular for embedded systems, containers, and other use-cases has resorted to temporarily disabling its LZ4 rolling decompression support due to data corruption concerns... ## Backblaze B2 x Suite Studios: S3 Native File Streaming Turns B2 Cloud Storage Into a High-Performance Drive DevFeed: [Backblaze B2 x Suite Studios: S3 Native File Streaming Turns B2 Cloud Storage Into a High-Performance Drive]() Original publisher: [Read original article]() Author: Dave Simon Published: 2026-09-10T14:04:38Z Content type: article Language: en Sources: [Backblaze Blog | Cloud Storage & Cloud Backup]() Topics: [Amazon S3](), [Cloud](), [Streaming](), [Filesystems](), [mount](), [data](), [migration]() Tags: [architecture](), [automation](), [b2cloud](), [cloud](), [cloud-storage](), [data](), [featured](), [featured-cloud-storage](), [media](), [media-workflow](), [migration](), [mount](), [nas](), [object-storage](), [s3](), [storage](), [streaming]() ### AI overview Backblaze B2 integrates with Suite Studios' S3 Native File Streaming to provide drive-like, high-performance access to cloud-stored data. Teams can mount B2 buckets, stream only the file portions applications need, and use standard S3-compatible objects without duplicating or relocating datasets. The integration supports media production and other workflows involving large cloud datasets. ### Source excerpt Backblaze B2 now integrates with Suite Studios S3 Native File Streaming, giving teams high-performance, drive-like access to cloud data. Work directly with standard S3-compatible objects across media, scientific, geospatial, and engineering workflows without duplicating datasets or creating new storage silos. The post Backblaze B2 x Suite Studios: S3 Native File Streaming Turns B2 Cloud Storage Into a High-Performance Drive appeared first on Backblaze Blog | Cloud Storage & Cloud Backup ## Improving Lakebase Postgres compute cache DevFeed: [Improving Lakebase Postgres compute cache]() Original publisher: [Read original article]() Author: David Wein; Sunil Kamath; Haoyu Huang Published: 2026-09-10T13:47:03Z Content type: article Language: en Sources: [Databricks]() Topics: [Caching](), [databricks](), [Databases](), [autoscaling](), [Amazon S3](), [Filesystems](), [cloud-infrastructure]() Tags: [autoscaling](), [cache](), [caching](), [data](), [data-engineering](), [databricks](), [engineering](), [filesystem](), [latency](), [low-latency](), [memory](), [s3](), [storage]() ### AI overview This Databricks article describes improvements to compute-side caching for Lakebase Postgres, a disaggregated storage system backed by object storage such as Amazon S3. It explains PostgreSQL shared buffers, the operating system page cache, and the planned use of dynamically autoscaling shared buffers consuming up to 75% of compute memory. It also introduces a local file cache as an incremental solution for fixed compute instances. ### Source excerpt The disaggregated storage model of Lakebase Postgres provides a feature rich, flexible... ## What algorithm did Windows XP use to choose your initial user picture? DevFeed: [What algorithm did Windows XP use to choose your initial user picture?]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-09T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Algorithm](), [Randomizer](), [Windows](), [Filesystems]() Tags: [algorithm](), [files](), [history](), [old-new-thing](), [random](), [recursion](), [windows]() ### AI overview The article explains that Windows XP selected an initial user picture randomly from the Default Pictures directory using the current time as the random seed. It describes a one-pass reservoir-sampling algorithm, including its efficiency and behavior when files change during selection, with a 100-picture safety limit. ### Source excerpt It's random, really. The post What algorithm did Windows XP use to choose your initial user picture? appeared first on The Old New Thing. ## Laravel August product updates DevFeed: [Laravel August product updates]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-09-03T20:30:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [cloud-infrastructure](), [Filesystems](), [AI search](), [Database](), [Authorization](), [changelog]() Tags: [api](), [changelog](), [cloud](), [compute](), [database](), [filesystems](), [laravel](), [product](), [search](), [ubuntu](), [updates](), [vector]() ### AI overview Laravel's August update announces framework, Cloud, and Forge changes, including read-through filesystems, semantic search, vector support, managed queue options, scoped API tokens, and Ubuntu 26.04 rollout. ### Source excerpt Here's everything that shipped in August. ## Rootless Jailbreak Detection: Updating the Signals, Not the Claim DevFeed: [Rootless Jailbreak Detection: Updating the Signals, Not the Claim]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Jailbreak](), [integrity](), [iOS](), [Filesystems](), [mount](), [Processes]() Tags: [filesystem](), [images](), [integrity](), [ios](), [jailbreak](), [mount](), [process]() ### AI overview Codename One updated its iOS integrity checks to detect current rootless jailbreak layouts. The changes cross-check potentially hooked APIs, inspect mounts and loaded images, and rerun detection when the application returns to the foreground. ### Source excerpt Codename One's iOS integrity checks now detect current rootless jailbreak layouts, cross-check hooked APIs, inspect mounts and loaded images, and rerun on foreground entry. ## What makes a good AI coworker? With OpenAI's Codex product lead DevFeed: [What makes a good AI coworker? With OpenAI's Codex product lead]() Original publisher: [Read original article]() Author: info@1password.com (Chris Fowler) Published: 2026-08-25T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Artificial Intelligence](), [codex](), [OpenAI](), [long-context](), [Filesystems](), [coding](), [cursor]() Tags: [agent](), [agentic](), [agents](), [ai](), [ai-coding](), [autonomous](), [codex](), [context-window](), [cursor](), [dev](), [developers](), [engineering](), [filesystems](), [memory](), [openai](), [podcast](), [podcasts]() ### AI overview An episode featuring OpenAI Codex product lead Rohan Varma explores what makes AI agents effective coworkers. It focuses on shared context, durable memory and state outside the context window, filesystem-based task continuity, and steerability so people can understand and guide agent output. ### Source excerpt Zero-Shot Learning is a podcast about how AI is built, secured, and deployed. Hosted by Nancy Wang, 1Password CTO, and Dev Tagare, Senior Director of Engineering at Google Gemini, it offers a builder's view of the architecture and complex decisions involved in shipping AI. In this episode, Rohan Varma, Product Lead for Codex at OpenAI, described what happens when teams move from using agents for one-off tasks to enabling autonomous coworkers. Having worked on AI coding products at Cursor and OpenAI, Ro understands what people need to work effectively with agents and what agents need to work effectively with people. What makes a good (agentic) coworker? With any coworker, collaboration works best when everyone is working from the same context, toward a shared goal. Human coworkers are accustomed to working toward shared goals. With proper context and resources, they can divide work without losing sight of how their contribution affects the team. The difference between teams of people and agents is that people don't need to be told how to remember things. Everything they do carries historical context. When a team works together, their shared knowledge expands exponentially. Agents work within context windows, a temporary working memory that fills as a task continues. When the window is full, the system has to summarize the work without losing decisions and constraints that could cause the agent to miss crucial directives. State is a fundamental building block for making an agent feel more like a coworker. Without memory, every time you prompt an agent, it's kind of like its first day on planet Earth." -Rohan Varma, Codex Product Lead, OpenAI To be a useful long-term collaborator, an agent's memory has to exist outside its context window. The system has to preserve the work durably to understand which files were changed, which decisions were made, which results were gathered, and which tasks are yet to be completed. That shared state lets one agent resume a task, anoth ## Migrating a Synology NAS to a UniFi UNAS Pro 8 with Robocopy and SMB Multichannel DevFeed: [Migrating a Synology NAS to a UniFi UNAS Pro 8 with Robocopy and SMB Multichannel]() Original publisher: [Read original article]() Published: 2026-08-23T19:23:42Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [migration](), [UniFi UNAS Pro](), [Synology](), [Filesystems](), [Windows](), [Network]() Tags: [files](), [filesystem](), [migration](), [multichannel](), [musings](), [nas](), [network](), [performance](), [smb](), [synology](), [synology-nas](), [unas](), [unifi](), [unifi-unas](), [unifi-unas-pro](), [windows]() ### AI overview A personal technical account of migrating files from a Synology NAS to a Ubiquiti UniFi UNAS Pro 8. It describes SMB-based copying with Windows and Robocopy, file-transfer errors, Windows error 665, and troubleshooting that isolates a filesystem limitation on the UNAS. ### Source excerpt I've had a Synology NAS for a very long time, and recently I started moving its contents to a new Ubiquiti UniFi UNAS Pro 8. This seemed like it ought to be a fairly boring operation. Both devices speak SMB, I have a fast network (recently upgraded to 10 gigabit internally), and Windows has had tools for copying files reliably between machines for decades. Naturally, it turned into a whole evening of learning things I thought I already knew, which is why I started a blog lol. There was a nice bit of history here for me because back in 2007 (good lord!) I wrote a post called "XCopy considered harmful - Robocopy or XXCopy or SyncBack." My argument at the time was basically that once you are moving enough files, Explorer stops being the move and Robocopy starts looking pretty good. I even used /Z, Robocopy's restartable mode, because being able to resume a partially transferred file was useful on unreliable connections. Almost twenty years later, /Z turned out to be one of the most important things I needed to remove because it made everything hella slow. The migration The basic job was straightforward. I had shares on the Synology such as: \\server\music and matching shares on the UNAS: \\UNAS-Pro-8\music I initially used Explorer, mostly because it was there and because sometimes the easy thing really is the easy thing. That lasted until Explorer started producing errors on individual files: The requested operation could not be completed due to a file system limitation My first thought was filenames. NAS migrations are full of opportunities to discover that one filesystem is more permissive than another, and there were filenames with parentheses and other punctuation in them. Then this failed: \\server\music\Athlete\Tourist\05 Wires.m4p There is nothing especially exotic about 05 Wires.m4p, so I moved over to Robocopy to get a little more information. It consistently got to 92% and returned Windows error 665: 92% New File 4.3 m 05 Wires.m4p ERROR 665 (0x00000299) Cop ## Running YOLO-Mode Coding Agents in a Sandbox for Infrastructure Work DevFeed: [Running YOLO-Mode Coding Agents in a Sandbox for Infrastructure Work]() Original publisher: [Read original article]() Author: Engin Diri Published: 2026-08-04T00:00:00Z Content type: opinion Language: en Sources: [Pulumi]() Topics: [Claude Code](), [Security](), [coding](), [Claude](), [Filesystems](), [codex](), [cursor](), [Amazon Web Services]() Tags: [agent](), [ai](), [ai-agents](), [autonomous](), [aws](), [best-practices](), [claude](), [claude-code](), [codex](), [coding](), [cursor](), [docker](), [files](), [infrastructure](), [infrastructure-as-code](), [permission](), [sandbox](), [security]() ### AI overview This opinion article argues that coding agents should retain autonomous YOLO-mode operation inside a sandbox rather than rely on repeated command approvals. It discusses risks to local files, AWS credentials, Kubernetes configurations, and Pulumi access tokens, and presents sandboxing as a way to limit the blast radius during infrastructure work. ### Source excerpt Claude Code calls the flag --dangerously-skip-permissions, and the community long ago renamed it YOLO mode. It lets your coding agent run any command it wants without ever asking for permission. Every agent has some version of it, Codex and Cursor included, and if you use these tools seriously, you are probably running one of them every day. I am. YOLO mode is also what makes a coding agent worth having. An agent that stops for approval before every command is not autonomous; it's a slow pair programmer. But you cannot let it run wild on your machine without real guardrails either. You have heard the horror stories: wiped databases, deleted home directories, vanished git history. The odds on any given day are low, and it's tempting to conclude it will never happen to you. It only has to happen once. My version of this problem is worse than most, because the code in my working directory is infrastructure code. My laptop holds more than source files. It holds AWS credentials, kubeconfigs that point at real clusters, and Pulumi access tokens. This post walks through what an unsandboxed agent can actually do, why prompt guardrails fail exactly when you need them, and how a sandbox lets you keep full YOLO-mode autonomy anyway. Then I will show you the kit I built for doing infrastructure work this way. Approving every command is not a security model Let me get one thing out of the way first: the answer is not to turn YOLO mode off. A real working session involves hundreds of commands, and nobody reviews the hundredth npm install any better than the first. You are not evaluating at that point; you are pressing enter. Approval fatigue turns the permission prompt into a formality while destroying the one thing you wanted from the agent, which is that it works while you do something else. The goal instead is to run YOLO mode somewhere it cannot hurt you. That somewhere is a sandbox: an isolated environment where the agent has full autonomy and your machine is no longer part ## Serverless ICYMI Q2 2026 DevFeed: [Serverless ICYMI Q2 2026]() Original publisher: [Read original article]() Author: Julian Wood Published: 2026-07-20T16:40:00Z Content type: article Language: en Sources: [AWS Compute Blog]() Topics: [Serverless](), [Amazon Web Services](), [AWS Lambda](), [Firecracker](), [Amazon S3](), [Filesystems](), [Linux](), [virtualization](), [mount](), [Latency]() Tags: [2026](), [amazon-eventbridge](), [amazon-s3](), [amazon-simple-storage-service-s3](), [aws](), [aws-lambda](), [aws-step-functions](), [ci-cd](), [firecracker](), [latency](), [linux](), [mount](), [serverless](), [virtualization]() ### AI overview A Q2 2026 recap of AWS serverless launches and resources, focusing on AWS Lambda MicroVMs and Amazon S3 Files integration with Lambda. ### Source excerpt In this 33rd quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q2 2026 that you might have missed. Stay current with the latest serverless innovations that can improve your applications. In case you missed our last ICYMI, read about what happened in Q1 2026. AWS Lambda MicroVMs AWS Lambda [...] ## ln Command in Linux: Hard Links vs. Symlinks DevFeed: [ln Command in Linux: Hard Links vs. Symlinks]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-07-17T14:57:25Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Filesystems]() Tags: [blog](), [filesystem](), [guide](), [how-to](), [linux](), [pitfalls](), [sysadmins]() ### AI overview This practical Linux guide explains how hard links and symbolic links use the ln command but behave differently. It describes inodes, hard-link persistence after deleting an original name, and restrictions such as same-filesystem requirements and limits on linking directories. ### Source excerpt Hard links and soft links in Linux both use the ln command but behave very differently. This practical guide explains exactly how each works, when to use which, and how to avoid the common pitfalls that catch even experienced sysadmins. Continue reading... ## Mastering Linux Administration: 20 Powerful Commands to Know DevFeed: [Mastering Linux Administration: 20 Powerful Commands to Know]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-07-06T03:56:38Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Command-line interface](), [Monitoring](), [Filesystems](), [IO](), [cpu]() Tags: [administration](), [automated](), [backup](), [blog](), [command-line](), [commands](), [cpu](), [examples](), [files](), [https-linuxblog-io-tag-commands](), [io](), [linux](), [memory](), [monitoring](), [ncurses](), [sysadmins]() ### AI overview A tutorial introducing 20 Linux commands for system administrators, with examples and explanations of their uses. The supplied text specifically discusses vmstat for monitoring system and memory statistics, inotifywait for tracking filesystem events, and ncdu for analyzing disk usage. ### Source excerpt Linux is a powerful and versatile operating system that can be used for a wide range of purposes. For many system administrators, the command line interface is the primary way to interact with the system. Continue reading... ## Vercel Sandbox now supports FUSE-based filesystems DevFeed: [Vercel Sandbox now supports FUSE-based filesystems]() Original publisher: [Read original article]() Author: Brandon Tuttle Published: 2026-07-03T01:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Filesystems](), [mount](), [Amazon S3](), [Network](), [datasets]() Tags: [data](), [datasets](), [driver](), [filesystems](), [mount](), [network](), [object-storage](), [remote](), [s3](), [vercel]() ### AI overview Vercel Sandbox now supports FUSE-based filesystems, allowing remote storage and custom filesystems to be mounted as regular paths inside a running Sandbox. This includes S3 buckets, network filesystems, and other FUSE-compatible drivers, enabling direct access to large datasets without copying them into the Sandbox. ### Source excerpt Vercel Sandbox now supports FUSE, letting you mount remote storage and custom filesystems inside a running Sandbox. Use it to attach S3 buckets, network filesystems, or any other FUSE-compatible driver as a regular path. This makes it possible to stream large datasets directly from object storage, share state across Sandboxes through a common filesystem, or run tools that expect POSIX paths against remote sources without copying data into the Sandbox first. Learn more about remote storage mounts in the documentation. Read more ## Vercel Open Source Program: Spring 2026 cohort DevFeed: [Vercel Open Source Program: Spring 2026 cohort]() Original publisher: [Read original article]() Author: Amy Egan Published: 2026-06-29T13:00:00Z Content type: news Language: en Sources: [Vercel News]() Topics: [Open Source](), [Vercel](), [Maintainers](), [Next.js](), [React](), [Model Context Protocol (MCP)](), [TypeScript](), [MCP](), [Filesystems](), [CSS](), [Framer Motion](), [SVG]() Tags: [2026](), [ascii](), [browser](), [maintainers](), [mcp](), [model-context-protocol](), [next-js](), [open-source](), [react](), [real-time](), [typescript](), [vercel]() ### AI overview Vercel announces the Spring 2026 cohort of its Open Source Program, providing selected maintainers with platform credits, third-party service credits, and guidance. The cohort includes projects for ASCII video rendering, React UI components, MCP server development, animated icons, design systems, and abstract syntax tree exploration. ### Source excerpt The world runs on open source software. The frameworks, libraries, and tools we rely on are made possible by communities that share ideas and build in the open. At Vercel, we want to help those communities thrive. That's why we run the Vercel Open Source Program: a developer initiative that gives maintainers the resources and support they need to keep shipping and growing their projects. Four times a year, we welcome a new cohort of open source projects into the program. Maintainers receive $3,600 in Vercel platform credits, a starter pack with credits from third-party services, and guidance from Vercel and the community. Today, we welcome a new cohort into the program. Spring 2026 cohortASCII Studio A browser-based tool that converts video frames in real time into precise ASCII representations using an optimized rendering pipeline. Users can adjust density, contrast, and character sets to produce customized ASCII animations. Creator: Vansh Nagar View the project View GitHub repository Sync UI A free, open-source React UI library offering 125+ animated components, 13+ pre-built blocks, and 3 premium templates. Built with Material UI and Motion (motion/react), designed for design engineers building landing pages and Next.js projects. Creator: Abhi Varde View the project View GitHub repository xmcp A TypeScript framework for building and deploying MCP (Model Context Protocol) servers, featuring file-system routing, hot reloading, middleware support, and flexible deployment options including zero-config Vercel support. Creator: Valentina Bearzotti View the project View GitHub repository Componentry An open-source collection of animated, interactive React UI components styled with Tailwind CSS and Framer Motion, designed to be copied and pasted into apps rather than installed as a dependency. Creator: Harsh Jadhav View the project View GitHub repository AnimateIcons A library of 281 animated SVG icons for React, built on motion/react with hover and imperative triggers p ## Quick: An internal hosting platform for the AI era DevFeed: [Quick: An internal hosting platform for the AI era]() Original publisher: [Read original article]() Author: Daniel Beauchamp Published: 2026-06-10T12:49:23Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [hosting](), [Shopify](), [Artificial Intelligence](), [API](), [Cloud](), [nginx](), [HTML](), [Filesystems](), [Web Development]() Tags: [ai](), [api](), [cloud](), [hosting](), [html](), [server](), [shopify](), [storage]() ### AI overview Shopify's Quick is an internal hosting platform that lets employees publish folders of HTML and assets to secure, employee-only URLs without frameworks, deployment pipelines, or configuration files. The article describes its Google Cloud Storage and NGINX architecture, Identity-Aware Proxy authentication, local-folder upload workflow, and planned API capabilities for data, file storage, and AI-related functionality. ### Source excerpt Quick lets anyone at Shopify ship a site in seconds. It has changed the culture of how we build and share. [Next page]()