Brno Hat

Jiri Eischmann's Blog

Linux Desktop Migration Tool 1.5

After almost a year I made another release of the Linux Desktop Migration Tool. In this release I focused on the network settings migration, specifically NetworkManager because it’s what virtually all desktop distributions use.

The result isn’t a lot of added code, but it certainly took some time to experiment with how NetworkManager behaves. It doesn’t officially support network settings migration, but it’s possible with small limitations. I’ve tested it with all kinds of network connections (wired, Wi-Fi, VPNs…) and it worked for me very well, but I’m pretty sure there are scenarios that may not work with the way I implemented the migration. I’m interested in learning about them. What is currently not fully handled are scenarios where the network connection requires a certificate. It’s either located in ~/.pki and thus already handled by the migration tool, or you have to migrate it manually.

The Linux Desktop Migration Tool now covers everything I originally planned to cover and the number of choices has grown quite a lot. So I’ll focus on dialogs and generally UX instead of adding new features. I’ll also look at optimizations. E.g. migrating files using rsync takes a lot of time if you have a lot of small files in your home. It can certainly be speeded up.

Fediverse Reactions

4 responses to “Linux Desktop Migration Tool 1.5”

  1. MicKet Avatar

    @brnohat
    I like the Idea of this application but I assumed some other usage.
    If you switch a distribution or reinstall a Device you usually do not have a spare computer.

    So i assumed your Migration tool is kind of a backup tool which Backup the home but extract the usefull things which could differ between desktops and store it e.g. in a .yml and ZIP.

    eg. network and VPN configuration. Used W-LAN, copy home without some directories like .cache. etc.

    1. eischmann Avatar

      I definitely don’t want to step into the backup area. I think there is a lot of great backup tools already. At the moment I’m focusing on one scenario: you have a new computer and you want to migrate your data and settings from the old computer. The scenario with a temporary storage is interesting, I might look into it in the future, but I think it may get really complex like: where to store it? Locally? What if there isn’t enough space? Remotely? What remote targets to support using which protocols?

      1. MicKet Avatar

        @brnohat
        > where to store it? Locally? What if there isn’t enough space? Remotely? What remote targets to support using which protocols?

        It is nice, that you think that far, but I don't see a need that you focus on that.

        I think a working concept behind it is more important.

  2. dusoft Avatar

    @brnohat I have created something similar, but just for KDE apps – it migrates configs (settings) only:
    https://github.com/nekromoff/kde-migrant

Leave a Reply

Your email address will not be published. Required fields are marked *