My crippled kernel count is around 6, how about yours?

    • over_clox@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      18 hours ago

      Timeshift itself borked my shit up. I had to reinstall all registered packages to fix its fuckups…

      sudo aptitude reinstall '~i'

      Edit: Sure it took a long while, about as long as a full OS reinstall, but never once was there any issue with the kernel.

      • bobs_monkey@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        18 hours ago

        While only once, timeshift destroyed my bootloader. Don’t update and reboot before a meeting, kids

        • over_clox@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          18 hours ago

          My test of Timeshift was pretty simple and straightforward.

          1. Fresh install Linux Mint

          2. Install most of the main software I wanted.

          3. Do a Timeshift backup.

          4. Install some extra software I didn’t necessarily need, but might want to use someday.

          5. Restore the backup from step 3.

          Results: Everything from step 4 was still registered as installed, but almost nothing from step 4 actually worked.

          So I brute force reinstalled everything in place, and haven’t used Timeshift since. I’m perfectly comfortable using the terminal, and at worst a live boot media, to fix any issues that might come up.

          • FauxLiving@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            13 hours ago

            Timeshift is a good piece of software doing a tired trick.

            The new hotness is copy on write file systems and snapshots. I can snapshot, instantly, then do a system update and revert to the previous snapshot also instantly.

            Instead of using symlinks files, like Timeshift, the filesystem is keeping track of things at the block level.

            If you update a block it writes a new copy of the block (copy on write). The old copy is still there and will be overwritten unless it is part of a snapshot. Since the block is already written, snapshots don’t require any data to be copied so they’re instant.

            Once you finish the system update, all of the overwritten blocks are still there (part of the snapshot) and reverting is also just a filesystem operation, theres no mass data to be copied and so it is also instant.

            It does use disk space, as allocated blocks AND snapshotted blocks are stored. It uses less than Timeshift though, since Timeshift copies the entire file when it changes

            ZFS and btrfs are the ones to use.

      • Kairos@lemmy.today
        link
        fedilink
        arrow-up
        1
        ·
        18 hours ago

        I also can’t get over the fact that it doesn’t understand RAID or filesystems somehow.