# mount The Linux mount command and mount() system call attach filesystems to directories or files, with configurable filesystem and mount flags. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound DevFeed: [fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-11T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [container](), [mount](), [Security](), [Process]() Tags: [container](), [container-image](), [kubernetes](), [mount](), [network](), [performance](), [reliability](), [security](), [stateful](), [storage](), [waiting]() ### AI overview This article explains why a stateful pod can remain in ContainerCreating for fifteen minutes when fsGroup triggers a recursive chown across a large network-backed volume. It describes how fsGroupChangePolicy: OnRootMismatch can skip the recursive walk when the volume root group already matches, and discusses the setgid invariant that supports this behavior. ### Source excerpt Pod stuck in ContainerCreating from fsGroup recursive chown: fsGroupChangePolicy: OnRootMismatch, and why the setgid bit on the volume root makes it safe. ## FastAPI frontends and static files served from the CDN DevFeed: [FastAPI frontends and static files served from the CDN]() Original publisher: [Read original article]() Author: Daniel Park Published: 2026-09-10T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [FastAPI](), [Vercel](), [Front end](), [mount]() Tags: [cdn](), [frontend](), [mount](), [tool](), [vercel]() ### AI overview Vercel now promotes FastAPI frontends and static files served through app.frontend() or StaticFiles to the Vercel CDN at build time, allowing matching requests to bypass Vercel Functions. Route precedence is preserved, while dependency-protected frontends and middleware-protected static files remain on the function unless configured otherwise. ### Source excerpt FastAPI frontends and static files, served with app.frontend() or StaticFiles, are now promoted to the Vercel CDN at build time. Requests for those paths are served directly from the CDN, without invoking your Vercel Function. FastAPI evaluates routes in declaration order. A route declared before a StaticFiles mount takes priority over any CDN file at that path. This precedence is preserved. Promoted source directories remain in the function bundle so the app can read from them at runtime. To exclude them and serve only from the CDN, set tool.vercel.fastapi.static.exclude = true in pyproject.toml. Frontends guarded by dependencies are kept on the function as the CDN cannot run dependency checks. Similarly, static files which sit behind middleware are also kept on the function. To override this and always promote to CDN, set tool.vercel.fastapi.static.cdn = true. To opt out of the CDN entirely, set it to false instead. For more information see the Vercel FastAPI documentation. Read more ## 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 ## 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. ## 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. ## From a Large Allowlist to Three Denials: Permissions for a Coding Agent DevFeed: [From a Large Allowlist to Three Denials: Permissions for a Coding Agent]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-11T07:00:00Z Content type: opinion Language: en Sources: [Philipp Lehmann]() Topics: [coding](), [Bash](), [Linux](), [Authorization](), [Kernel](), [mount](), [Network](), [Command-line interface]() Tags: [agent](), [agents](), [coding](), [command-line](), [curl](), [kernel](), [linux](), [mount](), [network](), [permissions](), [sandboxing](), [security](), [shell]() ### AI overview The article argues that command allowlists are a poor security boundary for coding agents because the required command set continually expands and command names do not constrain effects. It proposes enforcing limits at the kernel level with Linux namespaces, a read-only root filesystem, scoped writable mounts, and dropped capabilities, allowing a shell to run while restricting its blast radius. ### Source excerpt bwrap --unshare-net --cap-drop ALL instead of a command allowlist: sandboxing a coding agent's shell so rm -rf and curl cannot leave the workspace. ## 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 [...] ## Don't bring exposed developer credentials to Black Hat DevFeed: [Don't bring exposed developer credentials to Black Hat]() Original publisher: [Read original article]() Author: info@1password.com (Eric Eddy) Published: 2026-07-09T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Cybersecurity](), [Security](), [ssh](), [Encryption](), [passwords](), [Command-line interface](), [SDKs](), [mount](), [Go](), [JavaScript](), [Python](), [make]() Tags: [ai](), [attacks](), [black-hat](), [cli](), [cryptography](), [cybersecurity](), [developer](), [developer-tools](), [developers](), [events](), [go](), [integrations](), [javascript](), [leaderboard](), [passwords](), [python](), [secrets](), [security](), [ssh](), [supply-chain]() ### AI overview This article urges developers attending Black Hat to secure locally stored credentials before the conference. It discusses exposed AWS credentials and SSH keys, plaintext secrets, outdated cryptography, and 1Password tools for discovering, securing, and accessing credentials. It also describes mounted environment variables, CLI and SDK integrations, developer demonstrations, and a credential-sprawl challenge. ### Source excerpt Black Hat is where the security industry gathers to compare notes on current cybersecurity topics. It brings together a diverse group of security experts, from C-suite executives to black-hat hackers. Some attendees see it as a target-rich environment for testing their latest hacks. Many hackers and supply chain attacks rely on the fact that local credentials are stored in predictable locations with standardized file names, in clear text. For example, AWS credentials usually live in ~/.aws/credentials because the CLI writes them there by default. SSH keys live in ~/.ssh. 1Password developer tools can secure these credentials. It's never a bad time to secure locally-stored developer credentials, but if you're attending Black Hat, this might be an especially good time. Secure your credentials in 1Password before the conference, and find us at the booth to get an exclusive sticker. Find and secure SSH keys Developer watchtower discovers SSH keys that are stored in plaintext or use outdated cryptography. Follow the documentation to discover and secure your local SSH keys, which you can then access from the terminal using biometrics, just the same way you do for your passwords. Secure environment variables (Beta) 1Password Environments make your Environment's variables available via locally mounted .env files, without writing your credentials to disk. You can securely share them with team members and access them programmatically in your terminal via our CLI or via our SDK in Go, JavaScript, or Python integrations. Follow the documentation to secure and mount your environment variables. Find us at booth 4735 Located in the main exhibit hall near the Bayside C escalators. If you're attending the conference please come say hello, pick up some stickers, and ask us all your questions about 1Password developer tools! Play our developer challenge, Credential Sprawl Capture the Flag to win exclusive swag and get your name on our leaderboard. We'll be running live demos and havin ## 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 ## Google Drive on Linux: A Fast rclone Mount (and Why Your Thumbnails Are Missing) DevFeed: [Google Drive on Linux: A Fast rclone Mount (and Why Your Thumbnails Are Missing)]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-06-12T10:00:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Google](), [Linux](), [mount](), [Ubuntu](), [systemd](), [Caching](), [xfce](), [OAuth](), [API]() Tags: [browser](), [caching](), [google](), [image](), [linux](), [mount](), [oauth](), [systemd](), [ubuntu](), [xfce]() ### AI overview A tutorial describing a personal setup for mounting Google Drive as a browsable folder on Ubuntu with XFCE using rclone. It covers OAuth authorization, a systemd user service, aggressive caching for faster browsing, and the problem of missing image thumbnails on the mount. ### Source excerpt How I finally got Google Drive working as a fast, normal folder on Linux with rclone -- and fixed the non-obvious problem of missing image thumbnails on FUSE mounts. ## 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... ## Drives for Vercel Sandbox in Private Beta DevFeed: [Drives for Vercel Sandbox in Private Beta]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-06-05T00:01:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [DRIVE](), [Vercel](), [mount](), [SDKs](), [Command-line interface]() Tags: [cli](), [dependencies](), [drive](), [mount](), [production](), [sandbox](), [sandboxes](), [sdk](), [storage](), [vercel]() ### AI overview Vercel Sandbox introduces Drives in private beta, providing persistent attachable storage that remains available across disposable sandbox lifecycles. Drives can preserve agent workspaces, repositories, dependencies, and build outputs, and can be managed through the beta SDK or CLI. ### Source excerpt Vercel Sandbox now supports drives in private beta. Drives are persistent, attachable storage with a lifecycle independent from any sandbox. Create a drive once, then mount it at a configurable path when starting a sandbox. When the sandbox stops, the drive remains available to attach to a later sandbox. Install the beta SDK (@vercel/sandbox@beta) or beta CLI (sandbox@beta), then create and mount a drive: Sandbox Drives are useful for: Keeping agent workspaces across disposable sandboxes Retaining cloned repositories, dependencies, and build outputs Managing data independently from the sandbox lifecycle During the private beta, a drive can be mounted read-write by one sandbox at a time. Sandbox drives should not be used for production data while in private beta. Sign up here to join the waitlist, learn more in the docs, or read the complete guide. Read more ## Kubernetes v1.36: User Namespaces in Kubernetes are finally GA DevFeed: [Kubernetes v1.36: User Namespaces in Kubernetes are finally GA]() Original publisher: [Read original article]() Author: Rodrigo Campos Catelin; Giuseppe Scrivano Published: 2026-04-23T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Linux](), [mount](), [Security](), [Containers](), [vulnerability]() Tags: [containers](), [kubernetes](), [linux](), [mount](), [performance](), [process](), [security](), [startup](), [vulnerability]() ### AI overview Kubernetes v1.36 brings User Namespaces to General Availability, enabling rootless security isolation for workloads. The Linux-only feature confines container privileges to the user namespace, while ID-mapped mounts translate ownership at mount time without rewriting files or incurring expensive recursive ownership changes. ### Source excerpt After several years of development, User Namespaces support in Kubernetes reached General Availability (GA) with the v1.36 release. This is a Linux-only feature. For those of us working on low level container runtimes and rootless technologies, this has been a long awaited milestone. We finally reached the point where "rootless" security isolation can be used for Kubernetes workloads. This feature also enables a critical pattern: running workloads with privileges and still being confined in the user namespace. When hostUsers: false is set, capabilities like CAP_NET_ADMIN become namespaced, meaning they grant administrative power over container local resources without affecting the host. This effectively enables new use cases that were not possible before without running a fully privileged container. The Problem with UID 0 A process running as root inside a container is also seen from the kernel as root on the host. If an attacker manages to break out of the container, whether through a kernel vulnerability or a misconfigured mount, they are root on the host. While there are many security measures in place for running containers, these measures don't change the underlying identity of the process, it still has some "parts" of root. The engine: ID-mapped mounts The road to GA wasn't just about the Kubernetes API; it was about making the kernel work for us. In the early stages, one of the biggest blockers was volume ownership. If you mapped a container to a high UID range, the Kubelet had to recursively chown every file in the attached volume so the container could read/write them. For large volumes, this was such an expensive operation that destroyed startup performance. The key enabler was ID-mapped mounts (introduced in Linux 5.12 and refined in later versions). Instead of rewriting file ownership on disk, the kernel remaps it at mount time. When a volume is mounted into a Pod with User Namespaces enabled, the kernel performs a transparent translation of the UIDs (us ## Top 10 Launches of Launch Week 15 DevFeed: [Top 10 Launches of Launch Week 15]() Original publisher: [Read original article]() Author: Wen Bo Xie Published: 2025-07-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [API keys](), [JSON Web Tokens](), [Apache Iceberg](), [OpenTelemetry](), [Security](), [Amazon S3](), [Deno](), [Figma](), [GitHub](), [mount](), [ui]() Tags: [2](), [apache-iceberg](), [api](), [api-keys](), [cryptographic](), [figma](), [github](), [launch](), [mount](), [npm](), [opentelemetry](), [s3](), [security](), [stripe]() ### AI overview Supabase's Launch Week 15 roundup presents ten product updates, including new API and JWT signing keys, analytics buckets with Apache Iceberg support, OpenTelemetry integrations, Figma Make connectivity, expanded storage limits, Deno 2 Edge Functions, GitHub-optional branching, Supabase UI components, and a Stripe-to-Postgres sync package. ### Source excerpt Highlights from Launch Week 15 ## Persistent Storage and 97% Faster Cold Starts for Edge Functions DevFeed: [Persistent Storage and 97% Faster Cold Starts for Edge Functions]() Original publisher: [Read original article]() Author: Lakshan Perera; Nyannyacha Published: 2025-07-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Amazon S3](), [Filesystems](), [mount](), [SQLite](), [Tokio](), [JavaScript](), [Internet of things](), [Database]() Tags: [boot](), [dependencies](), [environment-variables](), [files](), [iot](), [latency](), [mount](), [postgres](), [s3](), [sqlite](), [storage](), [tokio]() ### AI overview Supabase introduces persistent storage for Edge Functions by mounting S3-compatible buckets, including Supabase Storage Buckets, as directories. The release also reports up to 97% faster and more predictable cold starts by moving workers performing initial script evaluation to a dedicated blocking pool. ### Source excerpt Mount S3-compatible buckets as persistent file storage in Edge Functions with up to 97% faster cold start times. ## 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 ## Listing all mounts in all mount namespaces DevFeed: [Listing all mounts in all mount namespaces]() Original publisher: [Read original article]() Author: Christian Brauner Published: 2024-12-15T23:00:00Z Content type: tutorial Language: en Sources: [Personal blog of Christian Brauner]() Topics: [mount](), [Linux]() Tags: [api](), [introduction](), [linux](), [mount]() ### AI overview A technical explanation of Linux APIs and system calls for retrieving mount information, iterating through mounts and mount subtrees, and listing mounts in other mount namespaces. It also describes retrieving mount namespace IDs and iterating through mount namespaces. ### Source excerpt Introduction ## Mounting into mount namespaces DevFeed: [Mounting into mount namespaces]() Original publisher: [Read original article]() Author: Christian Brauner Published: 2023-02-27T23:00:00Z Content type: article Language: en Sources: [Personal blog of Christian Brauner]() Topics: [mount](), [kernels](), [file](), [coding]() Tags: [coding](), [filesystem](), [kernels](), [mount]() ### AI overview This article examines how to insert new mounts into a running container's mount namespace. It discusses the complexity of mount operations, a legacy userspace path-verification approach, and a newer approach intended to prevent symlink attacks by verifying paths and opening their final components before mounting. ### Source excerpt Introduction ## An excursion into a mount propagation bug DevFeed: [An excursion into a mount propagation bug]() Original publisher: [Read original article]() Author: Christian Brauner Published: 2023-01-04T23:00:00Z Content type: article Language: en Sources: [Personal blog of Christian Brauner]() Topics: [mount](), [bug](), [debugging]() Tags: [bug](), [data](), [debugging](), [mount](), [test]() ### AI overview An article examines a difficult-to-reproduce mount propagation bug involving a network namespace persisted by bind-mounting it in a separate mount namespace. It describes how the bug was reproduced and clarifies the shared, peer, master, and slave mount concepts used to understand the relevant code. ### Source excerpt Introduction ## AxiDraw Lego camera mount DevFeed: [AxiDraw Lego camera mount]() Original publisher: [Read original article]() Author: Stanko Published: 2020-10-17T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Raspberry Pi](), [mount]() Tags: [camera](), [lego](), [mount](), [plotting](), [raspberry-pi]() ### AI overview A project article describing a LEGO mount for a Raspberry Pi camera attached to an AxiDraw plotter. The mount provides adjustable height and rotation using a blue LEGO component connected to a glued rail. ### Source excerpt I already built a mount for my Raspberry Pi camera, but it was 3d printed. Meaning that it has one fixed position. I used it a couple of times, but I wasn't super satisfied. Then I stumbled on these images, and thought it was a great idea to use Lego to build a new, more versatile mount. A friend of mine had a bunch of spare Legos laying around, so he gave me two bags full of Legos to play around. I wasn't sure where to start, especially because I wanted to make both height and rotation adjustable. After fiddling with the blocks for about an hour, I came up with this: It is quite simple, but the secret is in the blue part. Because it can be connected with the black "rail" I glued on to the plotterI used double sided mounting tape, as it is stable enough and easy to remove if I want to This allows me to change the height of the mount, by inserting the blue part into the different hole. And to make things even better, the blue part behaves as an axis, and the whole mount can be rotated around it. Once mounted, it looks like this: And finally I shot a short test video plotting my logo: If you want to see pen plots of my generative art, check my Instagram account. ## AxiDraw plotter Raspberry Pi camera mount DevFeed: [AxiDraw plotter Raspberry Pi camera mount]() Original publisher: [Read original article]() Author: Stanko Published: 2020-05-07T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Raspberry Pi](), [mount](), [3D]() Tags: [3d-printed](), [camera](), [mount](), [project](), [raspberry-pi]() ### AI overview A personal project documents mounting a Raspberry Pi camera directly on an AxiDraw plotter using a 3D-printed mount. The author describes assembling and modifying the mount, adjusting the camera lens for close-up video, and recording the resulting footage. ### Source excerpt It has been almost two months since my last post because I was super busy with my new passion, generative artFor now, you can see my work on my Instagram profile. Expect new posts about my process and tools in the near future.. I also got my hands on the brilliant little machine by Evil Mad Scientist, AxiDraw plotter, and it is the best purchase I made in a long time. I love everything about it - how it is engineered, images I can produce using it and their support. Then I saw this video and was blown away by the idea of recording a plotter from this perspective. When I asked the author how he does it, he pointed me to the tutorial he selflessly created. To film these wonderful videos, he made a mount for Raspberry Pi camera he can put directly on the plotter. I had a Raspberry lying somewhere in the flat, so I immediately ordered a camera and a 3d printed mount. Because of the COVID situation and the curfew it took a week for these to arrive, making me impatient. It didn't take me long to assemble this, but I did break oneLuckily I ordered two. 3d printed mount when I was drilling holes in it. I didn't have any M2 screws, so improvised with the plastic spacers and connected everything together using thin steel wire. It is not the prettiest thing I've built, but it is functional! Here you can see how much I missed when I was drilling the holes: Camera has a fixed focal length, and to get a sharp close up video, I had to adjust it by unscrewing the lens a little bit. My local Raspberry Pi supplier added this tiny tool with the camera, and it made adjusting super easy. Shorty after I was able to record the first video using the little contraption I created: White pen drawing stars on the black paper, the first video I recorded using the mount Mesmerizing isn't it? I love the reflection on the pen. More images to show how it looks mounted on the plotter: This was a fun little project, and I hope you like the video. I can't wait to record longer ones. And of course, big ## Troubleshooting systemd with SystemTap DevFeed: [Troubleshooting systemd with SystemTap]() Original publisher: [Read original article]() Author: Mark R Bannister Published: 2020-02-03T00:00:00Z Content type: tutorial Language: en Sources: [Jane Street]() Topics: [systemd](), [Linux](), [mount](), [Processes]() Tags: [commands](), [linux](), [logs](), [mount](), [processes](), [systemd](), [troubleshooting]() ### AI overview This article investigates Linux login and cron failures associated with systemd. It traces the issue to systemd choking during rapid successive automounts, known as a mount storm, and describes using SystemTap to inspect kernel and process behavior. ### Source excerpt When we set up a schedule on a computer, such as a list of commands to run every day at particular times via Linux cron jobs, we expect that schedule to execute reliably. Of course we'll check the logs to see whether the job has failed, but we never question whether the cron daemon itself will function. We always assume that it will, as it always has done; we are not expecting mutiny in the ranks of the operating system. ## Calculating the true impact of zip file entries DevFeed: [Calculating the true impact of zip file entries]() Original publisher: [Read original article]() Published: 2019-09-20T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Zip](), [Java](), [Filesystems](), [mount](), [Streams]() Tags: [api](), [files](), [filesystem](), [java](), [mount](), [open](), [random]() ### AI overview This article examines how to calculate the true contribution of each entry to a ZIP file's total size in Java. It explains why summing compressed entry sizes is insufficient and considers the entry headers and central-directory records that also contribute to the final size. ### Source excerpt How can we determine the impact of each entry on a zip file's size? It seems like a trivial problem, but things quickly don't add up. There's three built-in ways to read information about the contents of zip file in Java: Mount the zip as a FileSystem using FileSystems.newFileSystem and then access its contents using Paths. Open it with ZipInputStream for a one-shot iteration over the zip entries. Open it with ZipFile for random access to the zip entries. The first mechanism is extremely convenient. It allows interacting with the contents of a zip file using the same APIs as normal files. Unfortunately, by virtue of being exposed like regular files, you only have one way to check their size: Files.size(Path). This delegates to an API called BasicFileAttributes.size() which returns size of the file contents. While there is a ZipFileAttributes.compressedSize() for returning the size of the compressed contents, it's internal to the JDK and not available for our use. The other two mechanisms,ZipInputStream and ZipFile, both expose entries using the ZipEntry type. These being zip-centric APIs, many of the properties of the zip file format are directly available. Notably for our use case, there's a getCompressedSize() method. Problem solved? Not exactly... If you sum the compressed size of all entries in a zip the result will not equal the size of the zip file. This isn't entirely unexpected. After all, the zip file format surely requires additional metadata to track per-entry information like the relative path of each compressed file. So if we're looking to calculate the actual size impact of an entry on the final zip, can we do it? Zip file format An overview of the zip file format specification can be found on Wikipedia. It consists of a list of entries which are each defined as header followed by the compressed data (whose length is specified in the header). Finally, at the end, there is a central directory which lists all of the entries available in the file. A slight [Next page]()