@abhigya53544714
Ohhh, I'm following your logic regarding Linux now!
I assure you, the problem was not Linux there, but rather your drive configuration. The reason you "failed" to move those packages was because you should not be taking them out of the directories they're placed in by the package manager. Windows and Linux do not work in the same way; you cannot move packages like you can Windows executables.
There are multiple ways to fix that problem.
The quick-and-dirty way is to boot to a Live USB copy of Linux, so you're not booting to either hard drive directly. Copy one of the larger folders, probably /usr, to the HDD, and then rename the original (temporarily, in case of error) and create a symbolic link from the SSD to the HDD. Then reboot to the SSD like usual. (This solution is only a stop-gap in case you can't reinstall, however, as it's a tad brittle.)
The better, more stable way, is done at installation. Select custom drive configuration during Install, and set up the SSD as root (/), but then set up separate partitions on your HDD for /usr (where most programs get installed) and /home. Your computer will be a bit slower as a result, obvious since you're loading your programs from an HDD instead of an SSD, but it will work pretty well regardless.
Solution 3 is to get a larger SSD, but I assume that's not an option.
I agree with your solutions(I don't want to buy a new SSD), and I even implemented these all for a while. However, it became a nightmare to maintain all this.
Also, had you indeed reinstalled with /usr being configured as a separate partition on the HDD? It didn't sound like you had. That isn't a "nightmare" at all; it's quite effective if done in the normal manner, and you wouldn't ever notice it (except for the speed drop).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
@abhigya53544714 Ohhh, I'm following your logic regarding Linux now!
I assure you, the problem was not Linux there, but rather your drive configuration. The reason you "failed" to move those packages was because you should not be taking them out of the directories they're placed in by the package manager. Windows and Linux do not work in the same way; you cannot move packages like you can Windows executables.
There are multiple ways to fix that problem.
The quick-and-dirty way is to boot to a Live USB copy of Linux, so you're not booting to either hard drive directly. Copy one of the larger folders, probably
/usr, to the HDD, and then rename the original (temporarily, in case of error) and create a symbolic link from the SSD to the HDD. Then reboot to the SSD like usual. (This solution is only a stop-gap in case you can't reinstall, however, as it's a tad brittle.)The better, more stable way, is done at installation. Select custom drive configuration during Install, and set up the SSD as root (
/), but then set up separate partitions on your HDD for/usr(where most programs get installed) and/home. Your computer will be a bit slower as a result, obvious since you're loading your programs from an HDD instead of an SSD, but it will work pretty well regardless.Solution 3 is to get a larger SSD, but I assume that's not an option.
I agree with your solutions(I don't want to buy a new SSD), and I even implemented these all for a while. However, it became a nightmare to maintain all this.
How was it a nightmare, precisely?
Also, had you indeed reinstalled with
/usrbeing configured as a separate partition on the HDD? It didn't sound like you had. That isn't a "nightmare" at all; it's quite effective if done in the normal manner, and you wouldn't ever notice it (except for the speed drop).