24
Mounting Folders VS Symlinks?
(lemmy.today)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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.)how though?
Can you explain a bit more please?
mount -o bind /source /target
or use fstab or systemd mount unitsContainer 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
Thank you.