this post was submitted on 18 Jul 2024
25 points (96.3% liked)

Linux

48081 readers
796 users here now

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.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

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)

you are viewing a single comment's thread
view the rest of the comments
[–] aBundleOfFerrets@sh.itjust.works 4 points 3 months ago* (last edited 3 months ago) (2 children)

I don’t think this is a bad question at all, personally I would prefer to mount the drive once and symlink folders for a couple reasons:

  1. It’s easier to automate
  2. it’s theoretically faster (to initialize) as symlinks are effectively free
  3. I personally like symlink syntax more than mount syntax :P

One possible con to symlinks is that certain (linux native) software can misbehave when it has to interact with them, but this is a fairly uncommon issue. Stuff ran through wine or proton should support them just fine, as they are abstracted away.

[–] gpstarman@lemmy.today 1 points 3 months ago

Thanks man.

It’s easier to automate

I'm failing to see how and why one would do this? ( just curious )

I personally like symlink syntax more than mount syntax :P

same man. It's just more simple.

[–] seaQueue@lemmy.world 1 points 3 months ago (1 children)

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.today 1 points 3 months ago* (last edited 3 months ago) (1 children)

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 2 points 3 months ago (1 children)

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

[–] gpstarman@lemmy.today 1 points 3 months ago

Citation needed

My bad. I got it confused with hardlinks.

Thank you.