I let Discover handle updating to Fedora 42 and got a kernel panic error, so I backed up /home/ and did a fresh install of Fedora 42.

I started my restoration by nuking /home/ with sudo rm -R /home/ and then copied everything over via Dolphin as stuff was slowly torn asunder as parts unloaded from RAM. Everything seems intact so far…

  • pineapple@lemmy.ml
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 days ago

    Is it not perfectly fine and the official way to update fedora? (To do so via diacover)

  • LupusBlackfur@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    5 days ago

    I don’t guess I understand what thinking process on your part prompted this sequence of events… 🤷‍♂️ 🤷‍♂️

    • jws_shadotakOP
      link
      fedilink
      English
      arrow-up
      8
      ·
      5 days ago

      To actually answer, I fucked up by running sudo rclone first to copy everything and it messed with permissions, so I nuked it and copied with dolphin.

      I was just being lazy.

    • pineapple@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Just curious what do you mean by flat files? Do other operations systems include parts that aren’t actually visible files you can interact with?

      • just_another_person@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        Windows uses the system registry to control other aspects of interaction with runtimes and linked libraries, so it can be confusing to people newer to Linux to just realize that flat files don’t have some hidden interaction elsewhere in the system (usually).

    • jws_shadotakOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 days ago

      I had started with a full disk clone which is why I was careless with the restoration