I have a NTFS drive for Storage, which is shared between Win 11.

I want to change the location of (or replace) ~/Downloads, ~/Music, etc…,.

Note that the link to made is between NTFS and EXT4.

I found two ways while searching.

   1.Creating **Symlinks** in `~` with target pointed to folders in NTFS drive.

   2. **Mounting** the NTFS folders **directly** to`~/Downloads`, `~/Music`, etc..,.

Which one should I do? Which one is more beneficial?

Also how to mount folders to other folders (option 2) ? (I would really appreciate a GUI way)

I know this is not that important of a thing to post on Main Linux Community, but I already asked 2 linux4noobs community, and they are empty.




This is a continuation to my previous discussion, where most of the people said,

  1. It doesn’t matter where I mount.

  2. Mount certain folders directly into home other. (like mounting /mnt/data/music to ~/music)

  • seaQueue@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    bind mounts don’t usually have the problems that symlinks do. The only time I’ve had issues involve container systems like docker or flatpak.

    • gpstarman@lemmy.todayOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      3 months ago

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

      problems that symlinks do

      Can you explain more please?

      • seaQueue@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        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