Partitioning your drive is something that basically everyone on Linux does but what purpose does it actually serve and is there any reason why it might be better to avoid creating partitions in your d...
some partitions are useful.
Keeping /var and /tmp separate can stop DoS attacks by now allowing logs to fill the entire drive
/home means you can wipe the / partition and keep user data.
I’ve had a full /var partition cause all sorts of problems using the system. But I still think it’s good to have four partitions /, /var, /tmp, and /home. At least split out /home so you can format / without losing your stuff in /home.
Damn I’ve always wanted Windows to have that. Being able to put user folders on another partition, or even another drive, at install time. And being able to use “dynamic disk” (aka software raid) to expand partitions across disks as storage requirements grow. I know it is possible to setup, but with a lot of workarounds and annoying problems.
Windows user folders are nearly unusable in my opinion, too many programs throw in random folders and files everywhere. Especially the Documents folder, too many games putting incoherent stuff in there
Jup, useless folder. There’s one related thing I’ve complained a lot about lately, so I’m gonna complain some more about it:
Microsoft got this “great” idea of trying to repeatedly trick me into uploading that Documents folder to the cloud. A folder filled with GBytes of Battlefield and Assassins Creed cache files, Starfield mods, MS database files, etc… A lot of files that are in constant change, or locked the entire session. Annoying as hell. I love Onedrive, but I dont know why its so damn important for them to have those files.
Sometimes I really wish I could switch to some Linux distro instead.
It’s asinine that Onedrive doesn’t have an equivalent of the decades-old gitignore technology…
There seems to be a workaround, though - archive link. It should work as long as the local and remote conflict remains unresolved, or Microsoft decides to just push the remote onto the local machine and delete your files instead.
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:.
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?
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.
I remember doing this in macOS, when I got my first SSD. I installed it and kept the os on the SSD and mapped my user directory to my hdd. It made upgrades and re-installs much easier, which was a plus because it was actually a hackintosh.
some partitions are useful. Keeping /var and /tmp separate can stop DoS attacks by now allowing logs to fill the entire drive /home means you can wipe the / partition and keep user data.
I’ve had a full /var partition cause all sorts of problems using the system. But I still think it’s good to have four partitions /, /var, /tmp, and /home. At least split out /home so you can format / without losing your stuff in /home.
Damn I’ve always wanted Windows to have that. Being able to put user folders on another partition, or even another drive, at install time. And being able to use “dynamic disk” (aka software raid) to expand partitions across disks as storage requirements grow. I know it is possible to setup, but with a lot of workarounds and annoying problems.
Windows user folders are nearly unusable in my opinion, too many programs throw in random folders and files everywhere. Especially the Documents folder, too many games putting incoherent stuff in there
Jup, useless folder. There’s one related thing I’ve complained a lot about lately, so I’m gonna complain some more about it:
Microsoft got this “great” idea of trying to repeatedly trick me into uploading that Documents folder to the cloud. A folder filled with GBytes of Battlefield and Assassins Creed cache files, Starfield mods, MS database files, etc… A lot of files that are in constant change, or locked the entire session. Annoying as hell. I love Onedrive, but I dont know why its so damn important for them to have those files.
Sometimes I really wish I could switch to some Linux distro instead.
It’s asinine that Onedrive doesn’t have an equivalent of the decades-old gitignore technology…
There seems to be a workaround, though - archive link. It should work as long as the local and remote conflict remains unresolved, or Microsoft decides to just push the remote onto the local machine and delete your files instead.
Except ms wants you running out of space and upgrading to a higher level tier. Upton Sinclair and all that.
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:.
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?
The second paragraph is about changing the path where Windows should look for the user files (analogous to running
usermod -h /new/home userto 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 –
HOMEDRIVEcontains the drive letter, andHOMEPATHcontains the path relative to the drive’s root (no, I’m not willing to call it an absolute path). If an application only uses theHOMEPATHenvvar, 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.what’s c: ?
I remember doing this in macOS, when I got my first SSD. I installed it and kept the os on the SSD and mapped my user directory to my hdd. It made upgrades and re-installs much easier, which was a plus because it was actually a hackintosh.