# Filesystem Published articles for Filesystem. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## Kernel prepatch 7.3-rc3 DevFeed: [Kernel prepatch 7.3-rc3]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-13T22:32:53Z Content type: news Language: en Sources: [LWN.net]() Topics: [Kernel](), [Testing]() Tags: [filesystem](), [kernel](), [release](), [testing]() ### AI overview The Linux kernel 7.3-rc3 prepatch has been released for testing. Linus Torvalds described it as a relatively large release candidate with a larger-than-usual filesystem footprint. ### Source excerpt The 7.3-rc3 kernel prepatch is out for testing. Linus said: "Another fairly large rc release, and again one with a bigger filesystem footprint that we usually see." ## Linux 7.3-rc3 Released: "Another Fairly Large RC" DevFeed: [Linux 7.3-rc3 Released: "Another Fairly Large RC"]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T22:00:23Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Large Language Model](), [LLMs]() Tags: [desktop-linux](), [drivers](), [filesystem](), [gpu](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [llms](), [networking](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Linux 7.3-rc3 is described as a relatively large release candidate, with substantial filesystem, driver, networking, and core-kernel fixes. The update includes an EROFS change disabling LZ4 rolling decompression because of potential data corruption, along with fixes affecting XFS, the SMB client, netfs, AFS, btrfs, sound drivers, GPU drivers, and several architectures. ### Source excerpt Out today is the third weekly release candidate of Linux 7.3 as this next kernel version works its way toward a stable release in the second half of October... ## 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... ## 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... ## CodeSOD: Asynchronous Directories DevFeed: [CodeSOD: Asynchronous Directories]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-09T06:30:00Z Content type: article Language: en Sources: [The Daily WTF]() Topics: [Vala](), [async/await](), [Library](), [Programming]() Tags: [async](), [asynchronous](), [await](), [codesod](), [exceptions](), [filesystem](), [writing-code]() ### AI overview This article examines implementing an asynchronous version of Vala's directory-creation method when the core library provides only a synchronous version. The proposed function walks up the directory tree, then creates missing directories in reverse order, using exceptions for control flow. ### Source excerpt Eri has a mix of a "true confession" and a "wait, really?" today. The programming language Vala bills itself as a C# like language that compiles into something pretty close to C performance, designed specifically for writing code against Gnome and its associated libraries. One of the C#-isms in brings in is async/await type semantics. You can yield someAsyncFunction(), which returns control to the caller, allowing it to proceed until the yielded function returns an actual value. Because it has asynchronous functions, many library functions for handling I/O are already async. So you can make_directory_async, which yields control so you can keep executing while waiting for the filesystem to make your directory. There are also synchronous versions of those methods. And then there's create_directory_with_parents, which will create a chain of directories for you. That's the synchronous version, and Vala's core library has decided not to provide an asynchronous version of it, which is my "wait, really?" I suspect it's really about the race conditions involved and the risks of things going wrong while doing it asynchronously; all solvable problems, but tricky ones to solve. But it's the problem Eri had, and this is their solution: /// Note: does not throw if target already exists async void create_directory_with_parents_async(File file, Cancellable? cancellable = null) throws Error { var to_create = new File[0]; var? current_target = file; while(current_target != null) { try { yield current_target.make_directory_async(Priority.DEFAULT, cancellable); } catch(IOError.NOT_FOUND e) { to_create += current_target; current_target = current_target.get_parent(); continue; } catch(IOError.EXISTS e) { break; } break; } for (int i = to_create.length - 1; i >= 0; --i) { try { yield to_create[i].make_directory_async(Priority.DEFAULT, cancellable); } catch(IOError.EXISTS e) { // Created by another process } } } If I'm reading this correctly, we start by trying to create the full path to ## 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. ## 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 ## Cline is now available in the AI SDK harness layer DevFeed: [Cline is now available in the AI SDK harness layer]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-08-18T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [Code](), [Shell](), [Command-line interface]() Tags: [agent](), [agents](), [ai](), [claude-code](), [codex](), [filesystem](), [opencode](), [remote](), [sandbox](), [sdk]() ### AI overview Vercel's AI SDK harness layer now supports Cline through the official @ai-sdk/harness-cline adapter. Cline uses the shared HarnessAgent interface, runs in the host process, and accesses the sandbox as a remote filesystem and shell. ### Source excerpt The AI SDK harness layer lets you run established coding-agent runtimes through one unified interface, so you can switch runtimes without changing your application code. Today we are adding Cline, which runs through the same HarnessAgent interface as other supported harness. @ai-sdk/harness-cline is the official harness adapter for Cline, implemented in collaboration with the Cline team. Cline runs fully in the host process and uses the sandbox as a remote filesystem and shell, so only its tools operate in the sandbox. No bridge process is installed inside the sandbox, similar to the existing Pi harness. Read the Cline harness documentation to get started. The full supported list of harnesses is now: Claude Code, Cline, Codex, Deep Agents, Grok Build, OpenCode, and Pi, with more coming soon. Read more ## A Guide to Linux /proc Filesystem DevFeed: [A Guide to Linux /proc Filesystem]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-08-17T10:34:50Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Kernel](), [Processes](), [cpu](), [Network]() Tags: [blog](), [cpu](), [desktop](), [examples](), [filesystem](), [guide](), [kernel](), [linux](), [network](), [process](), [processes](), [server](), [sysadmins]() ### AI overview A practical guide to the Linux /proc virtual filesystem, explaining how it exposes live kernel state such as running processes, memory, CPU information, network statistics, and hardware details. It also describes how standard tools read this data and introduces useful files and per-process directories. ### Source excerpt The /proc filesystem is a live window into the Linux kernel: process state, memory layout, CPU counters, network stats, and writable kernel tunables, all accessible with nothing but cat and grep. This guide walks through the most useful files and per-process directories with practical examples. Continue reading... ## Inside Appwrite's new build cache: 4x faster dependency installs DevFeed: [Inside Appwrite's new build cache: 4x faster dependency installs]() Original publisher: [Read original article]() Author: Torsten Dittmann Published: 2026-08-13T00:00:00Z Content type: article Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Caching](), [Cache](), [Deployment](), [Next.js](), [Package manager](), [Compression](), [cloud-infrastructure]() Tags: [cache](), [compression](), [dependencies](), [deployment](), [engineering](), [filesystem](), [next-js](), [object-storage](), [pnpm](), [production]() ### AI overview Appwrite's build network caches dependencies between builds for sites and functions. The cache is restored before installation and saved after successful builds, with snapshots isolated per resource. The article explains how Appwrite uses SquashFS images to efficiently store and unpack package-manager data, reporting faster installs for example Next.js applications. ### Source excerpt A deep dive into how Appwrite now caches your dependencies between builds, and what it means for your deployment times. ## Faster Appwrite Sites deployments powered by SquashFS DevFeed: [Faster Appwrite Sites deployments powered by SquashFS]() Original publisher: [Read original article]() Author: Luke B. Silver Published: 2026-08-12T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Deployment](), [mount](), [Cloud]() Tags: [announcements](), [cloud](), [deployment](), [filesystem](), [mount](), [work]() ### AI overview Appwrite is moving new Sites and Functions deployments on Appwrite Cloud to SquashFS. The compressed, read-only filesystem is mounted directly instead of being fully extracted, reducing cold-start work and improving startup predictability, especially for larger Sites. ### Source excerpt Appwrite Sites now packages new deployments with SquashFS, removing archive extraction and cutting the format-dependent cold-start path by up to 51% on larger sites. ## Connect to and manage Sandboxes from the dashboard DevFeed: [Connect to and manage Sandboxes from the dashboard]() Original publisher: [Read original article]() Author: Marc Codina Segura Published: 2026-07-23T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [dashboards](), [Vercel](), [browser]() Tags: [browser](), [filesystem](), [sandbox](), [sandboxes](), [snapshots](), [vercel]() ### AI overview Vercel now lets users connect to running Sandboxes from the dashboard to run commands, browse files, transfer files, and inspect open ports. Users can also take snapshots and stop or resume persistent sandboxes from the same interface. ### Source excerpt You can now connect to any running Sandbox from the Vercel dashboard. Run commands, browse the filesystem, upload and download files, and inspect open ports without leaving the browser. From the same view, you can also manage the sandbox lifecycle: take snapshots, and stop or resume persistent sandboxes. Open the Connect tab on any sandbox to try it out. Learn more about Vercel Sandboxes in the documentation. Read more ## 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... ## Creating an environmental logger - Part 1 DevFeed: [Creating an environmental logger - Part 1]() Original publisher: [Read original article]() Author: John Lee Published: 2026-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [ESP-IDF](), [Logging](), [Terminal](), [Internet of things](), [data](), [Library]() Tags: [article](), [blog](), [esp-idf](), [esp32](), [filesystem](), [how-to](), [i2c](), [iot](), [logging](), [sensor](), [vs-code]() ### AI overview This tutorial explains how to build an environmental logger with an ESP32-C61-Devkit-C, a DHT20 temperature and humidity sensor, and ESP-IDF. Part 1 covers reading the sensor over I2C and storing measurements in a little_fs filesystem on the module's flash memory. ### Source excerpt This article shows how to create a simple environmental logger using the DHT20 sensor and store the data on a little_fs filesystem on the module's flash memory. ## Reclaim Ceph Capacity Through CephFS Transcoding DevFeed: [Reclaim Ceph Capacity Through CephFS Transcoding]() Original publisher: [Read original article]() Author: Anthony D'Atri Published: 2026-07-01T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [Transcodings](), [Software](), [data]() Tags: [2026](), [4k](), [article](), [blog-post](), [ceph](), [cephfs](), [dram](), [efficiency](), [en-article](), [en-blog-post](), [enterprise](), [enterprise-storage](), [filesystem](), [fujitsu](), [git](), [hardware](), [performance](), [software](), [space](), [storage](), [tentacle]() ### AI overview This article addresses rising storage demands and hardware costs by discussing CephFS capacity efficiency. It describes replicated pools, Erasure Coding, and Fast EC in Ceph Tentacle, while the title identifies CephFS transcoding as the article's focus. ### Source excerpt Data expands to fill available storage (and beyond)! ¶ It used to be that enterprise storage meant 6RU rackmount Fujitsu 2351 Eagles, each holding a mind-boggling 380 MiB of data: enough for a whole company! Today that 380 MiB can't even hold a 4k pickleball video. Enterprises, educational instutitions, and really just about anyone these days demand storage capacities that start on the order of hundreds of tebibytes and rapidly grow to pebibytes. As this article is written in the spring of 2026, the memory market, which includes DRAM, SSDs, and legacy HDDs, has experienced a dramatic escalation of pricing. It is not uncommon to be quoted a price four times what the same hardware cost a year ago, and there are signs that it is going to get worse before it gets better. What's a poor ammonite to do?? Cephers find themselves between the Charybdis of quotes approaching Disaster Area's hypermathematics and the Scylla of hungry users armed with torches and git forks. Git forks, pitchforks. Get it? Sigh. Tough room. Anyway... Short of nuking the site from orbit, how do we make everyone happy, or at worst mildly discontented? Efficiency! CephFS ¶ CephFS is a popular, highly available and scalable software-defined POSIX-style distributed filesystem that can easily store tens of pebibytes of precious data. Or, alternately, cat videos. Ceph deployments often begin small, with replicated pools for perceived performance needs. As the cluster grows to more nodes and more data, it may become feasible and desirable to switch to Erasure Coding (EC) to make more efficient use of raw capacity. An EC pool thus can require substantially less raw storage for a given amount of user data, or store gobs more user data on a given amount of raw capacity This EC overhead table presents efficiency (space amplification) factors for a spectrum of EC profiles. Replicated pools usually maintain three copies of data, so for comparison they manifest an overhead factor of 3.0. EC 4+2 or 6+3 presents a ## Vercel Sandbox now support Custom Images DevFeed: [Vercel Sandbox now support Custom Images]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [toolchain](), [Docker](), [boot]() Tags: [boot](), [compute](), [container-registry](), [dependencies](), [docker](), [documentation](), [filesystem](), [images](), [os](), [performance](), [registry](), [sandbox](), [sandboxes](), [snapshots](), [toolchain](), [vercel]() ### AI overview Vercel Sandboxes now support custom images in public beta. Users can provide a custom root filesystem with their own operating system, toolchain, and dependencies. Images are pulled from Vercel Container Registry, and the feature is designed to preserve cold start performance through precompiled snapshots. ### Source excerpt Vercel Sandboxes now supports custom images. Launching in public beta today, images allow Sandboxes to start with your own custom root filesystem. Images are pulled from Vercel Container Registry, so anything you docker push is immediately available. Bring your own OS, toolchain and dependencies into the Sandbox without needing to spin up compute and create Snapshots. Images in the background for Fluid Compute and boot from a precompiled snapshot in the same format as our Sandbox Snapshots - so you get the convenience of a custom filesystem without sacrificing cold start performance. Read more about running images with Sandbox in the documentation. Read more ## Coding Challenge #124 - Du DevFeed: [Coding Challenge #124 - Du]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-06-13T08:01:14Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [POSIX](), [Unix](), [Utility Software](), [Programming]() Tags: [coding](), [exercise](), [filesystem](), [posix](), [programming](), [programming-language](), [run](), [unix](), [utilities]() ### AI overview A coding challenge asks readers to build their own POSIX-compatible du utility. It covers recursively traversing directories, calculating disk usage, handling hard links and symbolic links, and presenting results in multiple formats. ### Source excerpt This challenge is to build your own du. ## Linux tmpfs for Speed and Temporary Storage DevFeed: [Linux tmpfs for Speed and Temporary Storage]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-06-08T15:17:17Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [mount]() Tags: [blog](), [boot](), [desktop](), [filesystem](), [how-to](), [linux](), [mount](), [performance](), [server](), [storage](), [sysadmins]() ### AI overview A practical guide to Linux tmpfs, a filesystem backed by virtual memory that can use RAM and swap. It explains how Linux uses tmpfs, how to create and verify mounts, how to make them persistent, and when temporary storage is useful. ### Source excerpt tmpfs lets you mount a filesystem entirely in RAM. Here is how Linux already uses it, how to create your own mounts, and where it actually makes sense to use one. Continue reading... ## Sandbox persistence is now GA DevFeed: [Sandbox persistence is now GA]() Original publisher: [Read original article]() Author: Harpreet Arora Published: 2026-05-26T00:01:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Persistence](), [Vercel](), [Command-line interface](), [SDKs]() Tags: [cli](), [compute](), [filesystem](), [fork](), [network](), [persistence](), [sandbox](), [sdk](), [snapshots](), [storage](), [upgrade](), [vercel](), [workflow]() ### AI overview Vercel Sandboxes now provide generally available persistence. Filesystem state is automatically saved and restored between sessions, with persistence enabled by default and sandboxes addressable by durable names. Users can opt out for ephemeral workloads, while persistent sandboxes resume from the latest snapshot automatically. ### Source excerpt Vercel Sandboxes now automatically save and restore filesystem state between sessions. Persistence is on by default, meaning no snapshots to manage or state to track manually. Each sandbox has a durable, customizable name that acts as a unique reference in your project. You can create, retrieve, or resume a sandbox by name. Vercel spins sessions up and down automatically, without interrupting your workflow. Create a persistent sandbox When you call Sandbox.create(), persistence is enabled by default: Each automatic snapshot consumes snapshot storage, which is billed separately from compute. For ephemeral workloads, opt out of persistence to minimize storage costs: To opt out of persistence with the CLI, pass --non-persistent to sandbox create. Non-persistent sandboxes discard their filesystem when the session ends. Resume a persistent sandbox Resuming is automatic. Any call on a stopped sandbox, like runCommand() or writeFiles(), starts a new session from the most recent snapshot. Other improvements Sandbox.fork(): Create a new sandbox from an existing one Sandbox.getOrCreate(): Idempotent retrieve-or-create for long-lived sandboxes Sandbox.delete(): Permanently delete a sandbox Richer sandbox.stop(): Returns snapshot metadata plus active-CPU and network-transfer totals Lifecycle hooks: onCreate and onResume hooks for create, get, and getOrCreate Tags: Assign custom properties to sandboxes for multi-tenant tracking Get started Upgrade to the latest version to create persistent sandboxes by default: pnpm install @vercel/sandbox@latest # SDK pnpm install -g sandbox@latest # CLI Learn more about persistent sandboxes in the documentation. Read more ## Where SQLite Gives Up - Locks, Writers, and the Single-File Problem DevFeed: [Where SQLite Gives Up - Locks, Writers, and the Single-File Problem]() Original publisher: [Read original article]() Published: 2026-05-12T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [SQLite](), [benchmarking](), [Concurrency](), [file]() Tags: [benchmark](), [concurrency](), [embedded](), [filesystem](), [locks](), [python](), [sql](), [sqlite]() ### AI overview This article examines three production limitations of SQLite: unfair lock acquisition, globally serialized write transactions, and scaling constraints from its single-file, single-machine design. It uses small benchmarks and compares these trade-offs with the server-based deployment costs of Postgres and MySQL. ### Source excerpt . [Where SQLite Gives Up](where-sqlite-gives-up-cover... ## How we built a virtual filesystem for our Assistant DevFeed: [How we built a virtual filesystem for our Assistant]() Original publisher: [Read original article]() Author: Dens Sumesh Published: 2026-03-24T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Filesystems](), [Retrieval Augmented Generation (RAG)](), [Database](), [Bash](), [Unix](), [TypeScript]() Tags: [ai](), [developer](), [engineering](), [filesystem](), [github](), [latency](), [pricing](), [rag](), [typescript](), [unix](), [vercel](), [virtual]() ### AI overview The article explains how Mintlify built ChromaFs, a virtual filesystem for its documentation assistant. ChromaFs translates UNIX commands into queries against an existing Chroma database, allowing the assistant to search, read, and traverse documentation without cloning a repository into a sandbox. ### Source excerpt We replaced expensive sandboxes with ChromaFs, a virtual filesystem over Chroma, to give our docs AI assistant the ability to explore documentation like a developer would. ## Introducing the SPIFFS component DevFeed: [Introducing the SPIFFS component]() Original publisher: [Read original article]() Author: John Lee Published: 2026-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Filesystems](), [Streams](), [C](), [POSIX](), [ESP32]() Tags: [article](), [beginner](), [blog](), [c](), [esp-idf](), [filesystem](), [guide](), [posix](), [spiffs](), [storage](), [tutorial]() ### AI overview This practical guide introduces the SPIFFS component bundled with ESP-IDF for storing files on SPI NOR flash. It explains how SPIFFS works with the VFS layer and standard C and POSIX file APIs, describes features such as wear levelling, consistency checks, and format-on-mount, and outlines a basic flow for mounting, writing, renaming, and reading files. It also points to SPIFFSgen and an official working example. ### Source excerpt Learn what the ESP-IDF SPIFFS component is, how it works with the VFS layer and standard C file APIs, and how to use the SPIFFSgen tool to embed files. This article is a practical guide with references to the official example. [Next page]()