this post was submitted on 05 Mar 2024
91 points (87.0% liked)

Linux

48287 readers
638 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
you are viewing a single comment's thread
view the rest of the comments
[–] rtxn@lemmy.world 8 points 8 months ago* (last edited 8 months ago) (2 children)

I'm pretty sure you can just mount a volume to C:\Users.

I definitely wouldn't recommend changing the userdir paths in the system. Many of the office computers I work with are set up that way and it's always a pain in the ass when an application expects the home path to be located on C:.

[–] gravitas_deficiency@sh.itjust.works 4 points 8 months ago* (last edited 8 months ago) (1 children)

when an application expects the home path to be located on C:

Clarification: does NTFS just suck at understanding that a directory-mapped storage device mounted under C: should be treated as if it were C: when within the mount dir?

[–] rtxn@lemmy.world 6 points 8 months ago* (last edited 8 months ago)

The second paragraph is about changing the path where Windows should look for the user files (analogous to running usermod -h /new/home user to change the user entry in the passwd file), not changing the filesystem. I don't see any reason why a directory-mapped device would behave any differently than a regular directlry... although in my brief time working with softlinks and directory junctions, I learned not to have expectations of Windows/NTFS.

I think the issue is that Windows stores the home path in two environment variables -- HOMEDRIVE contains the drive letter, and HOMEPATH contains the path relative to the drive's root (no, I'm not willing to call it an absolute path). If an application only uses the HOMEPATH envvar, the full path will default to whichever drive letter the environment's working directory belongs to, which is most likely C:. I don't have a Windows machine to test it though, so I might be wrong.

[–] LinusWorks4Mo@kbin.social 0 points 8 months ago