I keep my /home directory too, and have many other drives and partitions that are symlinks within /home, that point to other partitions. I even have my drives installed considering their types, speeds, the busses they are on and their speeds… for max performance
! Keeping the home folder keeps my many KDE Plasma settings, just about all of my program’s settings, and then some as I had them prior to a reinstall
, and it should be perfectly fine too on a rolling release, because there will be little to no legacy stuff on it anyhow, but current stuff. Sure some programs leave stuff behind on uninstall, and if you don’t weed it out every once in a while it can get cluttered, but I always look for it and delete it if I don’t need it, and I hardly think they are any danger at all but wasted space. I do that manually, not with a cleaner (Kfind is a great help with that). I wouldn’t do it on a typical LTS OS though, as in 2+ years, a lot can change.
Small drives are cheaper in $/GB than large ones, and on modern motherboards, data can be sent between busses and circumvent the processor if just transferring data, and so write between them much faster than if it’s all on one big drive, which is especially good for content creators, musicians… who have large file assets to work with running in programs doing lot’s of work. When pooling from many drives they can do different things at the same time and with fewer bottlenecks.
I have the LTS Kernel installed as a fallback, and use the main and zen kernels for computing! Bleeding edge with a fail safe. I always have the newest and the previous version of EOS on a thumb drive for recovery or reinstall, backups of backups of backups, and keep package lists and even a step by step “before, during, and after” guide to my reinstall routine. I would like to script more of it, especially package installs, and have tried some methods but they never go down as planned and don’t handle errors gracefully, because pacman and or Pamac don’t. There should be an app for that, or it should be a feature of package installers to begin with!
In the end it’s all about use case too, but I too have a few things I think people should do less of to get more out of Linux:
-
Stop distro and/or DE hopping every time there’s an annoyance here and there, or because something in another one sounds promising, because for every one thing you gain by trying a different DE or distro, you will get plenty of new problems: Linux (Especially arch) is highly flexible, and you can do just about anything on any distro, you just have different ways to get there sometimes, I just picked the most versatile combo I know of: Arch with KDE Plasma, via EOS for added ease! They both advance fast in development and keep up with new tech, as well as have quick bug fix rates, so I often don’t even bother about anything not critical, and it fixes itself (metaphorically), and you can change things to your hearts desire and end up with your own perfect distro and DE in a way, so it can only be more suited for you than any other distro made by someone else which should only serve as a starting point. When you stick to something you will learn it in way more detail and be better prepared for problems in the first place, know where to look for things… and get more done in less time.
-
Information is king! When trying to do something you never have done before, for anything you don’t quite understand, or have more options than you understand how to pick from, get information first, and from many sources for comparison, preferably safer ones, like the Archwiki, your OS’s, Distro’s, the suspect software’s program forums and bug trackers. Next from tech sites with expertise and expert user base like stackexchange, not Redit or Youtube channels like “Linux newb”, “Someguy loves Linux”… with low subscriber and view ratings, because a huge amount of additional trouble can be had from the blind leading the blind! Also always check the dates of the information, and version numbers the information pertains to, because there’s way more outdated info out there than current up to date info, and you could have the very same problem in effect as to the symptoms, but a completely different problem under the hood, requiring a completely different fix, and if you try the wrong one you can easily just add to your problem! Detailed information gathering is a good way to find out if you are about to do the right thing for all the wrong reasons or vice versa, chasing the wrong thing or method for a thing…
-
If you are not an ace at remembering stuff, then take notes, notes, and more notes! Most importantly keep meticulous track of your steps!: In troubleshooting, even just learning something new, you will be pulled in many directions, and have to cross reference a bunch to gain a more thorough understanding, given how much stuff has to work together, and depends on other stuff! Less is often not more! Actually it rarely is! Keeping it simple isn’t always an option, and good records and more information, will help you reverse mistakes, trace your steps to see what you may have done wrong, get used to common operations, files, commands and procedures, find all kinds of goodies you didn’t know existed and so much more. Keep your records, because it’s likely you may need some of the same info again, and remember you already have some or all of it already.
I have been computing since 1979, and using Linux exclusively for over 15 years, most of that on Antergos and then EndeavourOS (since day one), and still don’t know much at all, and things are ever changing, but I can say that the more information you take in and digest, the more things start explaining each other, and the easier it gets to learn more!