I’m a little teapot 🫖

  • 1 Post
  • 222 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle








  • how though?

    mount -o bind /source /target or use fstab or systemd mount units

    Can you explain a bit more please?

    Container software often needs permission for both the virtual path (wherever the bind mount is mounted to) and the source path (wherever the original is mounted from. It’s not terribly complicated but it does mean fiddling with access permissions in flatpaks.

    You should read about bind mounts, they’re fairly straightforward and there are many, many, many explanations available online


  • Lots of internet people says that one can’t create mount points across different filesystems.

    Citation needed. Bind mounts work just fine wherever you put them, again: you need to mount your source filesystem somewhere then you can bind mount paths from that mounted filesystem anywhere in the running VFS tree. You should Google linux bind mounts, they’re quite simple.

    problems that symlinks do

    Can you explain more please?

    Some software has problems following symlinks properly and fails to work unless given the symlink source path instead



  • For data like this from another filesystem I usually like to mount the entire volume somewhere private (like under /run) and then bind mount the parts I want to use into their desired locations (like /home/foo/Download, etc.)

    I do this with a second ext4 drive that I use for performance sensitive storage with my primary btrfs system root. It works well, just be aware of edge cases involving containers (you may have to grant the container access to the original mount location under /run in addition to the bound path. This is definitely a gotcha when working with those paths with flatpak.)