Choosing Between Hard Links and Symbolic Links on Unix Filesystems
A quick decision guide for when to use hard links vs symlinks, covering cross‑filesystem limits, backup impact, and how to verify link behavior.
Loading…
ReadMeFeed / Community knowledge
#hard-links
Real questions. Useful conversations. Find the people who know your stack.
unixUsing pnpm’s Workspace Protocol to Shrink Monorepo node_modules
Learn how pnpm’s workspace protocol creates a single content‑addressable store and symlinks packages, cutting duplicate dependencies and speeding up installs in a monorepo.
pnpmLimits of Mercurial Share Extension on Filesystems Without Hard-Link Support
Share Extension Behavior on Unsupported Filesystems The Mercurial share extension creates a clone that hard‑links the source repository’s store directory, reducing disk usage for low‑traffic workloads. On filesystems that do not support hard links (e.g., FAT or certain network shares), the extension silently falls back to a full copy, producing a share that
mercurialVim backupcopy choice for retry-safe writes on network filesystems
I need to configure Vim so that an interrupted write to a shared network filesystem leaves the original file intact, while also ensuring that hard links to that file remain valid after a successful save. The documented behavior indicates that writebackup creates a temporary backup before overwriting, and backupcopy determines whether Vim copies the original
vim