These are all some great thoughts. I didn’t do it, although I could’ve simply experimented with the new laptop. I just happened to find a yet better solution. I realized that all my goals would be better served by doing a fresh install of manjaroKDE on a 64GB USB stick!
I have spent the last couple days re-doing my old configurations for all my important programs. I can now boot the portable system in both laptops, or any future ones. I plan on using the laptop’s internal drives only for extra storage and backups. This feels like a dream setup so far, no perceivable difference from running system in internal SSD as is the convention.
In any event, this is an interesting topic in its own sake. Here are my thoughts.
you can copy to your new disks before install ( /home/ usr/ /opt ) , but /etc
will be changed by installing
Which implies /home, /usr and /opt would be left untouched. I was aware modern installers leave /home intact, but didn’t know the same holds true for /usr and /opt. This might be worth trying.
I’ve never dealth with cpu microcodes, but based on quick research, seems like another rabbit hole like this video, for example: Install the CPU Microcode on Arch When Dual Booting - YouTube
@stargazer I’ve considered disk cloning and rsync. Both require modifying fstab, grub and other components after installing in a new machine, which is daunting to me, as all the tutorials I’ve ever found are directed at linux gurus. Also, having encrypted partitions adds an extra layer of complexity to this procedure.
But now that my main system is in a USB stick, I could very well use clonezilla to easily save disk images as backups. From my understanding, I could even restore one of these images onto another USB stick, and not have to modify the usual things: [fstab, grub, encryptab, network manager], which makes the portable setup the more convenient and easily migratable in case of damage to the USB stick.
@cscs transfuse looks cool I’ll definitely try it at some point.
@cbDejaVu I assume
pacman -Qe only saves the package names, but no application configuration data, correct? I know most packages save their configuration files in
/home/<user>/.<package_name>/ or in
/home/<user>/.config/<package_name>/ . So this leads to a new mystery:
If I reinstalled the packages from a
packagelist.txt, and copied the old /home to the new system, would this be ALL that is necessary to have the packages be configured just as before? Or would there be missing bits and pieces from other locations?? (such as… maybe /opt, or /usr/local)???