#file-system-interface

#file-system-interface

A new version of the next-generation copy-on-write snapshotting GPL filesystem for Linux is out: bcachefs 1.37.0 appeared just yesterday as we write. This release includes support for the forthcoming Linux kernel 7.0. It is expected next month - the latest release candidate, 7.0-rc4, appeared the same day as the new bcachefs release.

Both work with Linux's existing swapping mechanism. Swapping (called paging in Windows) is a way for the kernel to handle running low on available RAM. It chooses pages of memory that aren't in use right now and copies them to disk, then those blocks can be marked as free and reused for something else.

I began by creating a soft link locally from my blog's repo of posts to the src/pages/posts of a new Astro site. My blog currently has 6742 posts (all high quality I assure you). Each one looks like so: --- layout: post title: "Creating Reddit Summaries with URL Context and Gemini" date: "2026-02-09T18:00:00" categories: ["development"] tags: ["python","generative ai"] banner_image: /images/banners/cat_on_papers2.jpg permalink: /2026/02/09/creating-reddit-summaries-with-gemini description: Using Gemini APIs to create a summary of a subreddit. --- Interesting content no one will probably read here...

Modern Linux is powerful, flexible, stable, and secure. With the exception of some of the more lightweight Linux distributions, it's also far more resource-dependent (just like all modern operating systems). Also: 5 things to consider before leaping from one Linux distribution to another Consider this: The minimum system requirements for Ubuntu Desktop today include just 4GB of RAM. I've run Ubuntu on a virtual machine with only 3GB of RAM.

A few months ago, I decided to breathe new life into a 2019 Dell XPS 15 that had been collecting dust for a couple of years. Despite its (at the time) high-end Core i7 CPU and 32GB of RAM, Windows was frustratingly slow on it. The fan was constantly at full throttle even when the machine was idle, and it regularly failed to install updates.

But what happens when you need more granularity? How do you grant write access to a file to just one specific user who isn't the owner and isn't in the owning group? How do you allow two different groups read access, but only one of them write access? How do you ensure files created in a shared directory automatically get specific permissions for a certain team?

We have already discussed in the previous two articles about file and folder permissions along with special permissions that are supported in linux. The permissions are effective for many scenarios. But what happens when you need more granularity? How do you grant write access to a file to just one specific user who isn't the owner and isn't in the owning group?

Retail point-of-sale systems today offer a wide range of options for peripherals and hardware. Their technical specifications play a major role in selection, and big retailers often choose multiple vendors to reduce a single point of failure. This gives them an advantage to negotiate price or support as well. Technically, these peripherals also require updating with new models and may have new feature sets. This necessitates the redevelopment of point-of-sale applications, increasing development costs.

The reason for this is Snap - a Linux application packaging format - creates a local Trash folder for each VS Code version, one that's separate from the system-managed Trash, according to a VS Code bug report dating back to November 11, 2024. Not only that, but Snap keeps older versions of VS Code after updates, potentially multiplying the number of local Trash folders and the trashed-but-not-deleted files therein. Emptying the system Trash folder doesn't affect the local instances.

At that point, backpressure and load shedding are the only things that retain a system that can still operate. If you have ever been in a Starbucks overwhelmed by mobile orders, you know the feeling. The in-store experience breaks down. You no longer know how many orders are ahead of you. There is no clear line, no reliable wait estimate, and often no real cancellation path unless you escalate and make noise.