halm,
@halm@leminal.space avatar

I just made the move to another computer, using the same distro and DE setup as the old one. So far I managed by backing up ~/ and /usr/ so I could drop in system and programming settings.

I don’t know how that will work if you’re going for a new distro but it’s always good to have your old configs for reference!

Deckweiss,

Nobody mentioned it yet, but my current no hassle solution is to:

just physically move the nvme from one computer to the other

eldavi,

i’ve done this a couple times w sata and pata drives and it works; there’s lots to clean up to do, but it works.

ikidd,
@ikidd@lemmy.world avatar

That’s all I’ve done, or imaged it to a new drive. Linux is glorious for portability.

John,

Or if you want to use the new drive, clone your drive to the new one(using clonezilla for example)

Dariusmiles2123,

I’m also thinking a lot about the best way to move everything from one computer to another if one day I buy a new computer.

I thought I had found a way with Clonezilla, but after trying to clone my Surface Go 1 to an old laptop I had, it didn’t work. Could be because I hadn’t removed the surface specific kernel. But now I don’t feel safe anymore.

Some people are suggesting to copy my home folder which I did, but I’m not sure it would fit my needs.

Basically, my files are taken care of with cloud storage (kDrive by the way), but I’d like to keep the way all my programs and extensions are setup.

So I ain’t sure I was a big help😅

I hope one day we’ll just have some program to prepare an archive to unpack for your next system to make the transition seamlessly. Or just putting the computer side by side and sending everything wirelessly.

I feel like we need this with all the personalization we can have on Linux.

pinchcramp,
@pinchcramp@lemmy.dbzer0.com avatar

Pretty sure that is possible with Nix and home-manager.

yak,
@yak@lmy.brx.io avatar

Consider using tar to create an archive of your home directory, and then unpacking that on the new machine. This will help to capture all the links as well as regular files, and their permissions.

Take a minute to think what else you have changed on the old machine, and then take another minute to think how tricky it would be to replicate on a new machine. Downloading the apps again is gloriously easy. Replacing configs, or keys and certificates, is not!

I normally archive /etc as well, and then I can copy out the specific files I need.

Did you install databases? You’ll want to follow specific instructions for those.

Have you set up web sites? You’ll want to archive /var/www as well.

GustavoM,
@GustavoM@lemmy.world avatar

tl;dr:


<span style="color:#323232;">dnf list installed > $anydir/meow
</span>

On new computer, with fedora installed and the meow file;


<span style="color:#323232;">dnf install $(cat $anydir/meow)
</span><span style="color:#323232;">
</span>
boredsquirrel,

Well doesnt work on Silverblue but


<span style="color:#323232;">flatpak list --app
</span>

If you have configured Flatpaks, you may want to copy the ~/.var/app/ directories.

bloodfart,

If you’re currently running a rpm distro, you can make it easier on yourself by using the duke nukem forever command to make a list of your installed programs: dnf list installed.

Once that’s outputting an appropriate format, dump it into a text file with | oldprogs.txt.

On your new computer, that same duke nukem forever command can be used to install from the list with something like dnf install << oldprogs.txt

I bet you can come up with a way to stuff all that into a neat little one liner that’ll provide error handling, output teeing and everything else!

GravitySpoiled,

Nice one.

On silverblue, everything is installed within a distrobox. I should back that up and make sure it’s in my home folder.

boredsquirrel,

No not everything is installed in a Distrobox.

  • the core system contains base stuff
  • you can layer needed apps that need to be on the base system
  • GUI apps are preferred as Flatpaks
  • some random stuff may be in a Toolbox or Distrobox
  • you can use pip, cargo and others on the base OS to install binaries there.
bjoern_tantau,
@bjoern_tantau@swg-empire.de avatar

One correction, it would be dnf list installed > oldprogs.txt. > instead of |.

bloodfart,

Ty, it’s early yet…

boredsquirrel,

Well that doesnt work for RPM distros, but just for dnf distros XD

mat,
@mat@linux.community avatar

Thanks, I can’t think of it as anything but duke nukem forever now. Your comment made my day.

Tlaloc_Temporal,

It’s more appealing than the Did Not Finish command. That’s to thematically close to flaming crashes for my liking.

ArcaneSlime,

duke nukem forever

My life has two eras, pre- and post- awakening to this acronym. Updates will never be the same.

velox_vulnus,

That will preserve your files in home directory - however, it is not reproducible in the sense that you’ll have to install all apps manually.

GravitySpoiled,

Thx.

Meaning, backup a list of flatpak apps and reinstall them on the new machine

lemmyvore,

See if flatpak has some sort of export format that would let you install everything the same on the other machine. Some package managers have that.

GravitySpoiled,

I think I wrote a function for that a year ago, I’ll have a look

boredsquirrel,

Export the wanted ~/.var/app/ folder to keep flatpak data

rotopenguin,
@rotopenguin@infosec.pub avatar

If you set up flatpak as --user, bringing your home directory over would be 99% of the job.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • linux@lemmy.ml
  • fightinggames
  • All magazines
    •