this post was submitted on 07 May 2025
62 points (88.8% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
60857 readers
466 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
🏴☠️ Other communities
FUCK ADOBE!
Torrenting/P2P:
Gaming:
💰 Please help cover server costs.
![]() |
![]() |
---|---|
Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A copy-on-write (CoW) filesystem like btrfs would be useful here. The “copy” would just be be shallow. The files exist in the new location but their contents are not copied, until a file in the new location is modified. And even then, not the whole contents of the file are duplicated. A “copy” like this would effectively only be a few kilo / mega bytes big rather than gigs
Sure ok. These filesystems are certainly superior in the ways you've described, but unless you were already considering changing to an fs like that, it's probably not an appropriate solution to this simple problem.
Fair, but it’s something painless do to next time someone might be installing a new system or migrating disks. Until not too long ago I didn’t know about these kind of options, so just knowing is a good first step even without further action
Yeah I agree with you here, your comment definitely has helped me finally make the switch (mentally, at least) to btrfs. I was a slow hold-out on ext4, but my next install I'll go the butter route.