One of the nices things about Linux/UNIX OSes is that if the storage is placed into the correct location, with the correct permissions, it will be used. It can "appear" to be there by mounting a partition, using a bind-mount, or just redirecting with a symbolic link. For example, KVM and libvirt likes for huge virtual machine virtual-HDDs to be in /var/lib/libvirt/images. My /var partition (if I have one) will usually be setup to hold log files and apt cache data, not 30 20G virtual machine HDDs. I can go into the libvirt settings and change where the storage pools are located ... or I can simply symlink /var/lib/libvirt/images to /data/vms/ - - done, forever. I wouldn't symlic OS partitions ... it adds another mode of failure to remember later, so if you want /home to be on a different disk, just move all the files there, and change where that new storage is mounted.Thanks for the link JD P - I bookmarked it (along with all my other "New to Linux") and will read it later tonight.
I do have a question pertaining to the file system on install. My system is a dual boot with an extra internal hard drive on my laptop. (DVD bit the dust, so I replaced it with another hard drive). I purchased the laptop in 2008, so you can see how old the hardware is. I have 4GB RAM, 256GB SSD and an extra 149GB HDD.
OR you can just modify the /etc/passwd file - there is a field for the home directory for any user - they don't have to be anywhere special at all. As long as the passwd file (or whatever equivalent authentication you use) provides the desired, correct, location for the user's HOME, it doesn't need to be /home/userid. /abdsd23rsdfas/userid is just as good. ~/ and ~userid will still work and the $HOME env will be set at login as expected. Of course and scripts that you/the user has written which hard-code /home/userid will fail.
Is ext5 something new or a typo?
Hope this helps.