# Filesystems Published articles for Filesystems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 [...] ## 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... ## 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. ## Your Agent Speaks MCP. Give It a Computer. DevFeed: [Your Agent Speaks MCP. Give It a Computer.]() Original publisher: [Read original article]() Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [The Fly Blog]() Topics: [MSP MCP](), [AI Bots]() Tags: [agents](), [api](), [auth](), [cdn](), [claude](), [claude-code](), [cli](), [close-to-users](), [cloud](), [codex](), [cursor](), [deploy-app-servers](), [docker](), [elixir](), [filesystems](), [fly](), [fly-io](), [gemini](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [mcp](), [mcp-server](), [networking](), [postgresql-clusters](), [servers](), [skills]() ### AI overview The article presents Sprites as disposable cloud computers for coding agents and explains using their API through MCP. It argues that MCP transport and progressive capability disclosure can work together, including through plugins and skills. ### Source excerpt Sprites are disposable cloud computers. They appear instantly, always include durable filesystems, and cost practically nothing when idle. They're the best and safest place on the Internet to run agents and we want you to create dozens of them. Sprites are a place to run agents; the first thing you should think to do with a new Sprite is to type claude (or gemini or codex). We've put a lot of effort into making sure coding agents feel safe and happy when they're on Sprites, because, to (probably) quote John von Neumann, "happy agents are productive agents." What's less obvious about Sprites is that they're great tools for agents. Want three different versions of a new feature? A test environment? An ensemble of cooperating services? It's super handy to be able to start your prompts, "On a new Sprite, do...". The Sprites API is simple, discoverable, and designed for this use case. The only real question is how your agent reaches it. For most of you the answer is MCP, and the setup is already written. You Don't Have To Pick There's an argument going around that MCP is the wrong way to extend an agent, and that command line tools and discoverable APIs are the Right Way. Half of that argument is correct, and it's the important half, so let's take it seriously. Dumping thirty tool descriptions into a context window is a bad way to teach anything. Not every Sprite command matters in every session, and cramming them all in signals to the model that they all matter to you. If you're not using network policies, gemini shouldn't burn a single token learning to configure them. Capabilities should reveal themselves progressively, the way they do when an agent works out a CLI one subcommand at a time. The wrong half is treating that as a case against MCP. Progressive disclosure is a question of what you say to the model. MCP is a question of how the bytes get there: transport, auth, structured results, a tool the model can call instead of a command whose flags it has to guess. Tho ## 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 ## 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 ## AgentFS in the Browser DevFeed: [AgentFS in the Browser]() Original publisher: [Read original article]() Author: Glauber Costa Published: 2025-12-22T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [AI Bots](), [Local AI]() Tags: [agents](), [ai-agents](), [browser](), [filesystems](), [git](), [persistence](), [privacy](), [server](), [sqlite](), [sync](), [tools](), [turso](), [wasm]() ### AI overview A tutorial on using AgentFS to give browser-based agents a filesystem abstraction backed by Turso, including in-memory, OPFS-backed persistent, and synchronized storage options. ### Source excerpt Run a full POSIX-style filesystem for AI agents inside the browser, backed by Turso WASM and OPFS. Clone git repos and run shell tools with no server. ## From Linux Primitives to Kubernetes Security Contexts DevFeed: [From Linux Primitives to Kubernetes Security Contexts]() Original publisher: [Read original article]() Author: Dave Altena Published: 2025-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Learnk8s]() Topics: [Kubernetes](), [Security](), [Linux](), [Containers](), [Kernel]() Tags: [cgroups](), [config](), [containers](), [filesystems](), [how-to](), [kernel](), [kubernetes](), [kubernetes-security](), [learn](), [linux](), [security]() ### AI overview This tutorial explains how Kubernetes Security Contexts control container privileges and how those settings map to underlying Linux primitives. It covers running containers as non-root users, managing capabilities, using read-only filesystems, and blocking privilege escalation. ### Source excerpt Dive deep into Kubernetes Security Contexts and learn how to manage security settings for your pods and containers. ## How to Fix USB Sticks Mounted as Read-Only DevFeed: [How to Fix USB Sticks Mounted as Read-Only]() Original publisher: [Read original article]() Author: Samuel Njuguna Karanja Published: 2025-06-06T07:56:19Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [USB](), [Linux](), [mount](), [Hardware]() Tags: [administration](), [administration-filesystems-hardware-mount-usb](), [errors](), [filesystem](), [filesystems](), [flash](), [hardware](), [how-to](), [linux](), [mount](), [storage](), [tutorial](), [usb]() ### AI overview This Linux tutorial explains why USB flash drives may be mounted as read-only, including filesystem errors, read-only mount options, physical write protection, and failing flash storage. It also introduces checking the current mount mode with the mount command. ### Source excerpt Learn how to identify and diagnose undesired USB flash drive read-only mounts. The post How to Fix USB Sticks Mounted as Read-Only first appeared on Baeldung on Linux. Related Stories SMB mount Security Modes and Fixing mount error(13): Permission denied in Linux What Is SELinux? Removing Log Files with a Cron Job in Linux ## How fsync and Linux write paths affect data durability DevFeed: [How fsync and Linux write paths affect data durability]() Original publisher: [Read original article]() Published: 2025-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Linux](), [Filesystems](), [Kernel](), [Operating system](), [systems]() Tags: [filesystems](), [fsync](), [kernel](), [linux](), [operating-systems](), [storage]() ### AI overview This technical explainer follows a Linux write from user space through kernel buffers, the virtual file system, and storage. It describes how buffering, lazy flushing, filesystems, and sync-related options affect whether data and metadata reach disk, while noting that behavior varies by filesystem and operating system. ### Source excerpt . [How Safe Is Your fsync... ## Case-insensitive filesystems considered harmful (to me) DevFeed: [Case-insensitive filesystems considered harmful (to me)]() Original publisher: [Read original article]() Published: 2021-06-04T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Filesystems](), [Compose](), [ci](), [Kotlin Multiplatform](), [Kotlin](), [Development]() Tags: [bugs](), [ci](), [compose](), [filesystems](), [kotlin](), [kotlin-multiplatform](), [linux](), [macos](), [open-source](), [windows]() ### AI overview The article investigates recurring CI test failures in projects using Jetpack Compose and Kotlin Multiplatform. It traces the failures to class-name casing differences caused by case-insensitive versus case-sensitive filesystems. ### Source excerpt Having been burned by case-insensitive filesystem bugs one too many times, I long ago switched my development folder to a case-sensitive filesystem partition on my otherwise case-insensitive Mac. Unfortunately this can actually work against me as I interact with the computers of coworkers and service providers which use the default. Well I was burned again, and this is the tale! I've been working on two projects based on Jetpack Compose1 which require me to recompile its sources. Despite building them unmodified, I still run its tests against my compiled version to ensure this core functionality of my project behaves as expected. However, both of my projects recently started experiencing test failures on CI, and it was the same, single test failing on both projects. The first project failed about a month ago when I added a MacOS worker in addition to the Linux worker to build a JNI library. Being so focused on the JNI compilation, I figured the Compose failure was a flake or something wrong with my setup. Its failure was: androidx.compose.runtime.CompositionTests[jvm] > testInsertOnMultipleLevels[jvm] FAILED java.lang.NoClassDefFoundError: androidx/compose/runtime/CompositionTests$testInsertOnMultipleLevels$1$item$1 (wrong name: androidx/compose/runtime/CompositionTests$testInsertOnMultipleLevels$1$Item$1) at java.base/java.lang.ClassLoader.defineClass1(Native Method) ⋮ at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) at androidx.compose.runtime.CompositionTests$testInsertOnMultipleLevels$1.invokeSuspend$Item(CompositionTests.kt:2055) Like I said I didn't look too closely at this output and assumed it was my own fault. The second project (which is not open source yet) started failing yesterday when I added a Windows worker to publish new targets for its Kotlin multiplatform library. Notably, the project already had a MacOS worker, and the PR to add the Windows worker did see both workers succeed. The merge commit, however, failed with an exception ## November 2020 round-up DevFeed: [November 2020 round-up]() Original publisher: [Read original article]() Author: Samuel Dionne-Riel Published: 2020-12-01T00:00:00Z Content type: news Language: en Sources: [Mobile NixOS news]() Topics: [Boot Process](), [Filesystems](), [Kernel](), [Mobile]() Tags: [boot](), [boot-process](), [feature](), [filesystems](), [kernel](), [keyboard]() ### AI overview The November 2020 Mobile NixOS project roundup describes merged improvements to the stage-1 boot process, including boot progress reporting, clearer and interactive error handling, reboot and power-off controls, and support for decrypting LUKS-encrypted root filesystems. The on-screen and physical keyboard interface is limited to the US QWERTY layout. ### Source excerpt This update is the twelfth in a series of regular updates on the state of the project. Only changes that have been accepted and merged in Mobile NixOS are chronicled here. There's always more work currently in-progress. Notable changes During the month 13 pull requests were merged. Some major improvements landed, let's take a peek. Progress in stage-1 The boot splash utility now shows the progress of the boot. This is done with a simple progress bar shows how much of the tasks have been handled. Long-running tasks can provide a message to show so the user knows things aren't necessarily hung. Speaking of hung tasks. Our init now detects when no tasks resolved in a given amount of time. When this happens, the boot is being failed with, hopefully enough context in the error message to help the user. Speaking of error messages. Error messages are now less of a dead-end for our users. The interface has been reviewed to put the text message front and center. Previously we were showing a big image because we didn't even have text rendering at this state. Now that we do, let's use it. In addition to that, the error applet is now somewhat interactive. There is now a cancellable countdown; when the time is elapsed the kernel is crashed, which allows the platform to do its default action (generally reboot). When canceled, the user can select different options, either through the touch screen, using a mouse, a keyboard or using volume-keys navigation. The user can select to power off their device, which default action (so mashing the power key will power off the device). Depending on whether the platform supports it, the usual different reboot options are given. Encrypted root filesystem support Thought we were done with stage-1 updates? No! What if it was now able to decrypt LUKS encrypted filesystems? Well it can! For now, this is mainly the plumbing to make it all work. Getting a LUKS encrypted filesystem on your device is left as an exercise to the reader. Our stage-1 can ## Threat Model Thursday: Files DevFeed: [Threat Model Thursday: Files]() Original publisher: [Read original article]() Author: Adam Published: 2020-01-23T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Filesystems](), [Security](), [integrity](), [Linux]() Tags: [bugs](), [filesystems](), [fsync](), [integrity](), [linux](), [mental-models](), [postgres]() ### AI overview This commentary examines how filesystem abstractions leak through interactions between performance, reliability, and fsync behavior. It argues that unexpected storage behavior reflects bugs and design issues rather than an operating-system tampering threat, while threat modeling remains useful for identifying security and integrity concerns. ### Source excerpt Have you considered the idea that "Files are Fraught With Peril" lately? Maybe you should... ## ReactOS 0.4.11 released DevFeed: [ReactOS 0.4.11 released]() Original publisher: [Read original article]() Published: 2019-03-04T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [version](), [Filesystems](), [btrfs]() Tags: [btrfs](), [filesystems](), [free](), [kernel](), [memory-leak](), [open-source](), [os](), [processors](), [react](), [reactos](), [release](), [version](), [win32](), [winapi]() ### AI overview The ReactOS team announces version 0.4.11, describing kernel, storage, filesystem, and application-loading changes intended to improve system stability and compatibility. The release includes fixes for a cache-controller issue, BTRFS memory leaks, Skylake AHCI incompatibility, and manifest support. ### Source excerpt The ReactOS team is pleased to announce the release of version 0.4.11. This version has seen substantial work done to the kernel, helping improve overall system stability. Kernel Improvements While the term kernel is used as a sort of catch-all term, in truth the range of functionality that it encapsulates is quite wide. One case in point is the kernel's responsibility for managing file I/O. A mistake here can cause subtle data corruption to more obvious hard crashes. ## GSoC 2018 - boot sector finished DevFeed: [GSoC 2018 - boot sector finished]() Original publisher: [Read original article]() Published: 2018-07-10T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [btrfs](), [boot](), [Filesystems](), [x86](), [Emulator](), [Development](), [Refactoring](), [Testing]() Tags: [boot](), [bootloader](), [btrfs](), [emulator](), [filesystems](), [free](), [gsoc](), [open-source](), [os](), [react](), [reactos](), [refactoring](), [testing](), [time](), [win32](), [winapi](), [x86]() ### AI overview A GSoC 2018 progress update reports that the ReactOS BTRFS boot-sector code can load freeldr.sys into memory and transfer control to it. The work still needs refactoring and testing on larger filesystems, while second-stage BTRFS support in freeldr.sys is in progress. ### Source excerpt Hi all! Sorry, haven't written anything for a while. Let me tell you what have been done since last post. BTRFS boot sector TL;DR: It works! I've been able to load main bootloader code from freeldr.sys into memory, transfer control to it and get on error message (freeldr.sys can't find its config file - I haven't written second-stage BTRFS code yet). It was not that easy because we are in x86 real mode when running boot sector thus only about 1mb of memory is available. ## ReactOS 0.4.2 Released DevFeed: [ReactOS 0.4.2 Released]() Original publisher: [Read original article]() Published: 2016-08-16T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [releases](), [Filesystems](), [version](), [interoperability](), [Unix](), [WINE]() Tags: [filesystems](), [free](), [interoperability](), [open-source](), [os](), [react](), [reactos](), [release](), [releases](), [update](), [version](), [win32](), [winapi](), [wine]() ### AI overview ReactOS 0.4.2 is an incremental release focused on refining the graphical shell and file explorer, updating external dependencies including Wine and UniATA, and adding native support for mounting and reading several Unix filesystems. ### Source excerpt The ReactOS Project is pleased to announce the release of version 0.4.2, again within three months of the previous release. The team sincerely hopes that this new rapid release cycle will hold for future releases as well. If there is one word to describe progress on the project, it would be steady. The project is reaching a point where rapid releases are viable, where disruption from introduction of major components or restructuring has been greatly reduced from the tumultuous early years and even as recently as the late 0. ## Tweaking ASUS Zenbook UX305CA on Linux DevFeed: [Tweaking ASUS Zenbook UX305CA on Linux]() Original publisher: [Read original article]() Author: Tom Published: 2016-04-21T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [ASUS](), [Linux](), [Ubuntu](), [configuration](), [Kernel](), [Filesystems](), [cpu](), [VLC]() Tags: [asus](), [battery](), [benchmark](), [configuration](), [cpu](), [debian](), [filesystems](), [grub](), [hardware](), [kernel](), [laptop](), [linux](), [performance](), [remote-work](), [thinkpad](), [ubuntu](), [update]() ### AI overview A practical account of configuring an ASUS Zenbook UX305CA running Ubuntu 16.04, covering SSD filesystems, swap, CPU and battery power management, touchpad behavior, and video acceleration with VD-PAU and VA-API. ### Source excerpt Lately I was searching for mobile notebook that I could use for remote work. I checked f ThinkPad series but they were huge bricks that have nothing in common with 'mobile' word. Then I saw ASUS Zenbook that I didn't take into account before and it was exactly what I was searching for. Configuration of Skylake based notebook right now is not straightforward - there are still glitches and small bugs that are waiting to be fixed. I want to sum up what I've done after installation. I started with fresh Ubuntu 16.04 to get Debian based distro with possibly latest kernel and patches. ## Developer Contract for Jerome Gardou DevFeed: [Developer Contract for Jerome Gardou]() Original publisher: [Read original article]() Published: 2014-10-20T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Filesystems](), [Java](), [Chrome](), [Network](), [Development](), [Microsoft]() Tags: [chrome](), [developer](), [development](), [filesystems](), [free](), [java](), [microsoft](), [network](), [office](), [open-source](), [os](), [react](), [reactos](), [win32](), [winapi]() ### AI overview A project news update reports that Jérôme Gardou worked under a ReactOS development grant in October 2014. His work addressed the memory manager, Java runtime compatibility, filesystem support, and network stability, including fixes related to Chrome. ### Source excerpt This is somewhat belated, but for the past month Jérôme Gardou has been working under a development grant issued by ReactOS Deutschland e.V. Jerome has been active working on the memory manager and his fixes were instrumental to getting a modern Java runtime to work. Other efforts with the Common Cache will help pave the way for adding support for more advanced and modern filesystems to ReactOS. Jerome's contract saw him pay special attention to the three applications, Chrome, Java, and Microsoft Office, voted on for support in the Community Edition, and several fixes were made to the network stack as he sought to stabilize Chrome. ## Building a Unix-Based System for Encrypted, Two-Way File Synchronization DevFeed: [Building a Unix-Based System for Encrypted, Two-Way File Synchronization]() Original publisher: [Read original article]() Author: Graham King Published: 2014-05-24T04:49:59Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Unix](), [Encryption](), [Filesystems](), [Bash](), [Self-hosted]() Tags: [bash](), [encfs](), [encryption](), [filesystems](), [self-hosted](), [software](), [sshfs](), [sync](), [unison](), [unix]() ### AI overview This tutorial describes a modular, Unix-based approach to synchronizing and backing up files across machines. It combines sshfs for remote storage exposed as a local filesystem, encfs for encryption, Unison for two-way synchronization, and a Bash script to simplify setup after reboot. ### Source excerpt "Unlock the power of Unix-style modular syncing and encryption." ## ReactOS NewCC Cache Implementation Addresses Filesystem Mapping Limitations DevFeed: [ReactOS NewCC Cache Implementation Addresses Filesystem Mapping Limitations]() Original publisher: [Read original article]() Published: 2011-04-09T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Caching](), [Filesystems](), [unit tests]() Tags: [cache](), [filesystems](), [free](), [open-source](), [os](), [react](), [reactos](), [structure](), [unit-tests](), [win32](), [winapi]() ### AI overview The article reports on ReactOS work to replace its existing common cache implementation. It describes efforts to resolve dependencies between the cache and memory manager, unit-test crashes, and a 4GB offset-mapping limitation affecting some filesystems. The NewCc branch reportedly addressed the mapping issue and could install and boot on an ext3 partition. ### Source excerpt NewCC Status A while back Art Yerkes merged in a significant part of his new common cache implementation into trunk. This merge was intended to lay the foundation for the eventual replacement of the current common cache, which will happen once Art clears up some inconsistencies in how the sections data structure is treated by the memory manager and the common cache. Sections management is the responsibility of the memory manager but provide functionality the common cache relies on. ## Fsync or Swim Part 1: Error Handling DevFeed: [Fsync or Swim Part 1: Error Handling]() Original publisher: [Read original article]() Author: Square Engineering Published: 2011-03-17T16:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Android](), [Filesystems](), [Persistence](), [Programming](), [POSIX]() Tags: [android](), [engineering](), [error-handling](), [errors](), [filesystems](), [kernel](), [persistence](), [posix](), [writing]() ### AI overview This first article in a series explains why applications must handle fsync errors, particularly on Android. It distinguishes filesystem operation atomicity from durability and describes how library, kernel, and hardware buffers can delay writes. It discusses using FileDescriptor.sync() or FileChannel.force() to explicitly flush data to storage. ### Source excerpt Heed fsync errors, especially on Android ## Newsletter 80 DevFeed: [Newsletter 80]() Original publisher: [Read original article]() Published: 2011-02-03T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Testing](), [Filesystems](), [Caching](), [Kernel]() Tags: [cache](), [filesystems](), [free](), [io](), [kernel](), [open-source](), [os](), [react](), [reactos](), [testing](), [win32](), [winapi]() ### AI overview This ReactOS newsletter reports on testing filesystem components with Microsoft's FASTFAT driver. The current common cache implementation blocks the effort, while a replacement implementation progresses further but still has bugs and missing functionality. The article also discusses related kernel and I/O manager issues. ### Source excerpt Component Testing As more components relating to filesystems sees implementation in ReactOS, they need to be tested. Pierre Schweitzer decided to try using Microsoft's FASTFAT driver to help in the effort, as using it successfully in ReactOS would indicate development is on the right track. Unfortunately, ReactOS' current common cache implementation effectively blocks that attempt due to its sorry state. The common cache has been touched upon in the past and mention was made of its problems. ## Navigating the Linux Kernel DevFeed: [Navigating the Linux Kernel]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2010-08-15T21:52:58Z Content type: tutorial Language: en Sources: [Nelson Elhage]() Topics: [Kernel](), [Linux](), [Git](), [Filesystems]() Tags: [filesystem](), [filesystems](), [git](), [linux](), [linux-kernel]() ### AI overview This article offers practical advice for navigating and source-diving the Linux kernel. It discusses learning the kernel source-tree layout and using Git to investigate source code, including filesystem, memory-management, core, networking, and architecture-specific areas. ### Source excerpt In response to my query last time, ezyang asked for any tips or tricks I have for finding my way around the Linux kernel. I'm not sure I have much in the way of systematic advice for tracking down the answers to questions about the Linux kernel, but thinking about what I do when posed with a patch to Linux that I need understand, or question I need to answer, I've come up with a collection of tips that will hopefully be helpful to others looking to source-dive Linux for whatever reason. ## ReactOS 0.3.8, FOSDEM 2009 DevFeed: [ReactOS 0.3.8, FOSDEM 2009]() Original publisher: [Read original article]() Published: 2009-02-04T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Operating system](), [Development](), [FOSDEM]() Tags: [bugfixes](), [changes](), [compiler](), [exception](), [filesystems](), [fosdem](), [free](), [git](), [io](), [kernel](), [linux](), [open-source](), [os](), [process](), [react](), [reactos](), [release](), [win32](), [winapi](), [windows]() ### AI overview ReactOS released version 0.3.8, a Windows-compatible operating system release that includes kernel bug fixes and enhancements, a new Portable Structured Exception Handling mechanism, driver improvements, and other system changes. The article also announces a ReactOS booth at FOSDEM 2009 and notes that the 0.3.x series remains alpha-quality software. ### Source excerpt ReactOS 0.3.8 Released Our development team is proud to present a new version of ReactOS, a Windows®-compatible operating system. It has been three months since the 0.3.7 release date. Much of the work has been done and only some minor changes remain in order to make the release cycle faster and less time consuming for developers and release engineers. Besides development of the operating system, a number of organizational and administrative changes were done to make the development process easier and more enjoyable.