Hello, I am sick and tired of Ubuntu relentlessly pushing snap. I currently am running a Windows Ubuntu Dual Boot and would like to replace the Windows partition with Garuda OS (They are on the same SSD). Eventually I want to move all my files from Ubuntu to Garuda and then delete Ubuntu.

I am not too familiar with messing around with the BIOS. I would like some advice on how exactly to safely do this without accidently bricking my system. Pointers to resources where I can learn how would also be helpful.

I am running Intel i5 with Nvidia 1070 GPU if that helps.

  • 257m@lemmy.mlOP
    2·
    1 year ago

    I need basically just my config files since projects are on gitlab. I will probably just zip them all up and store in cloud storage on dropbox and then redownload or try to access the ubuntu home paritition from Garuda if that is possible.

    • bob_wiley@lemmy.worldEnglish
      2·
      1 year ago

      No matter what you decided, it would be a good ideas to back up your files to a cloud service or on a flash drive before you start. That way of something goes wrong you don’t lose data.

      I would tend to agree that once you’re at that point, assuming you don’t want Ubuntu anymore and we’re just going to keep it around or your config files, it would be much easier to wipe the whole disk and start over.

      When you do that, make a data partition where you can keep stuff, that way you can distro hop as much as you want and leave your data partition in place.

      • oo1@kbin.social
        2·
        1 year ago

        yeah good advice
        i’d copy/rsync /home folder to a usb. regularly.
        .
        if you have a lot of symlinks, then make a simple bash script that’ll recreate them.

        also worth having a bash script that installs all your packages , and makes any config changes (copies edited files ) should you need to start again for any reason.(fire / theft / disk failure).

        cloud is ok as a 3rd backup - but i regard it more for portability and remote access than as a primary backup. whoever owns it can go bust, or have downtime, or get hacked etc.

        • bob_wiley@lemmy.worldEnglish
          2·
          1 year ago

          Ansible can also be good for making a setup script. Since it’s idempotent, you can use it for all your configs and run it whenever you want to get things back into spec. If something needs to change it will change, if something is already good, it will skip it.