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

  • floofloof@lemmy.ca
    0·
    2 months ago

    OpenSuse Tumbleweed helps because you can create a btrfs snapshot at any moment and then roll back to it if you get in trouble. And it does this automatically whenever you update the packages.

    • overload@sopuli.xyz
      0·
      2 months ago

      OpenSUSE Tumbleweed Gang. The only distro I haven’t been able to break after 6 months (well, I have, but I’ve been able to snapper rollback every time)

      • floofloof@lemmy.ca
        0·
        2 months ago

        It’s the first rolling distro I have tried, and I’ve been running it for about 3 years now without any real problems. I think maybe twice there have been updates that cause issues, out of hundreds of updates per week. It’s surprisingly solid, and everything’s up to date.

        Not everyone would want hundreds of updates per week of course, but it’s up to the user to decide how often to install updates. Unlike Windows, the updates don’t intrude, and they are fast.

        • overload@sopuli.xyz
          0·
          2 months ago

          It seems to hit that right balance of bleeding edge while SUSE are still testing the packages for a bit to ensure there aren’t bad updates. Fedora sounds interesting to me as well, but I’m not going to fix what isn’t broken.

    • aizakku@waterloolemmy.caEnglish
      0·
      2 months ago

      Been looking for a DR system for Ubuntu or mint, need to look into it myself but would like some feedback if this could be the right ticket.

      I just bought a raspberry pi 4 to host plex, I’m sure I could get it to do backup and restore too. Looking into it

  • collapse_already@lemmy.mlEnglish
    0·
    2 months ago

    I tried to use dd with too much hubris once. I had to restore from backups (which ironically, I had made with dd). I’m usually overly cautious, but I was in a hurry.

    • cevn@lemmy.world
      0·
      2 months ago

      I did this one a few weeks ago lmao. You think once would be enough. But I am a truly special being.

    • OhVenus_Baby@lemmy.ml
      0·
      2 months ago

      Knock Knock Knock.

      We (Jehovah’s Witness) would like to know if you had a minute, so we could come inside, and talk to you about OUR Lord and Savior… Linux Mint.

  • teawrecks@sopuli.xyz
    0·
    2 months ago

    So, when you say crippled kernel, do you actually mean you tweaked the kernel params/build to the point that it failed to boot? Or do you just mean you messed up some package config to the point that the normal boot sequence didn’t get you to a place you knew how to recover from and need to reinstall from scratch?

    I think I’m past the point where I need to do a full reinstall to recover from my mistakes. As long as I get a shell, I can usually undo whatever I did. I have btrfs+timeshift also set up, but I’ve never had to use it.

  • OhVenus_Baby@lemmy.ml
    0·
    2 months ago

    I just spent 11 days on a dual boot repair in fstab, passwd, loads of ecryptfs, amongst other boot and login issues. Before restoring from the full system backup after getting mad to finally want to use my PC. 11 fucking days almost all day in terminal. TOO many partitions and too many folders inside of folders to get to my ecryptfs files. I got so lost LSing around.

    After it all though, and it was an aneurism and a half. I still want to finish my goal and reinstall my dual boot this time correctly aiming the folders correctly.

    • SayCyberOnceMore@feddit.ukEnglish
      0·
      2 months ago

      Ah yes, reminds me of messing with my 1st pfSense firewall… I learned how good their recovery process was that evening

      • ohshit604@sh.itjust.worksEnglish
        0·
        2 months ago

        Just bricked my Proxmox install an hour ago and I had the pleasure to learn their recovery process sucks. (At least for my case)

        • SayCyberOnceMore@feddit.ukEnglish
          0·
          2 months ago

          Ah, yeah, you’ve just reminded me, I must move my stuff off proxmox when I get a chance.

          I tried that proxmox backup thing when I first set it up, good god what a complex mess… backup & recovery needs to be as simple and as smooth as possible.

    • Sock Puppet Society@lemm.eeOPEnglish
      0·
      2 months ago

      You mean why? Because you’re using your bare machine, you can use it as you wish. No nanny software limiting the fun or productivity

      • agent_nycto@lemmy.world
        0·
        2 months ago

        Yeah but breaking like six computers to do it, or one computer six times, seems like a pretty steep price for that when I basically just use my computer for gaming browsing and the occasional audio/video edit.

        • SayCyberOnceMore@feddit.ukEnglish
          0·
          2 months ago

          Nah, if you’re installing something user friendly (ie Linux Mint just for an example) it’ll work 1st time, guaranteed - or your money back.

          But… you’ll only really learn once you’ve fubar’d something… just like falling off riding a bike

        • priapus@sh.itjust.worksEnglish
          0·
          2 months ago

          OP said breaking the kernel, not the machine. The computers would be fine, its pretty damn difficult to brick a computer using software, at least by accident.

          Normal users will not break their kernel, op is likely doing some advanced tinkering. I have been using Linux for years and am definitely an advanced user and Ive broken my kernel zero times.

  • 🇰 🔵 🇱 🇦 🇳 🇦 🇰 ℹ️@lemmy.worldEnglish
    0·
    2 months ago

    I would actually be amazed if I ever bricked a PC fucking around with installing software to it. At the very worst, I might have to move a jumper pin to flash the CMOS and start fresh like I never even touched the thing. If somehow even that fails, it would be a unique experience.

  • Kng@feddit.rocksEnglish
    0·
    2 months ago

    Just did a fresh install after attempting to migrate from a proxmox VM to baremetal (turns out my mobo only supports UEFI and after spending an hr trying to convert I just gave up and reinstalled)

    • unhrpetby@sh.itjust.worksEnglish
      0·
      2 months ago

      It can be done if you mess with the initramfs.

      The kernel starts everything else by unpacking an archive containing a minimal environment to set stuff up for later. Such as loading needed kernel modules, decrypting your drive, etc. It then launches, by default, the /init program (mines a shell script).

      That program is PID 1. If it dies, your kernel will panic.

      After it finishes setup, it execs your actual /sbin/init. These means it dies, and that program (systemd, openrc, dinit, runit, etc) becomes PID 1. If an issue happens, both could fail to execute and the kernel will loop forever.

      • Shanmugha@lemmy.world
        0·
        2 months ago

        Thank you for explanation :) I suspected something like that - mess up with some internals, you do have a chance to bring the thing down. Which is why I always have a bootable usb around before doing anything risky

  • MoonMelon@lemmy.mlEnglish
    0·
    2 months ago

    It’s the same as learning anything, really. A big part of learning to draw is making thousands of bad drawings. A big part of learning DIY skills is not being afraid to cut a hole in the wall. Plan to screw up. Take your time, be patient with yourself, and read ahead so none of the potential screw-ups hurt you. Don’t be afraid to look foolish, reality is absurd, it’s fine.

    We give children largess to fail because they have everything to learn. Then, as adults, we don’t give ourselves permission to fail. But why should we be any better than children at new things? Many adults have forgotten how fraught the process of learning new skills is and when they fail they get scared and frustrated and quit. That’s just how learning feels. Kids cry a lot. Puttering around on a spare computer is an extremely safe way to become reacquainted with that feeling and that will serve you well even if you decide you don’t like Linux and never touch it again. Worst case you fucked up an old laptop that was collecting dust. That is way better than cutting a hole in the wall and hitting a pipe.

    • easily3667@lemmus.orgEnglish
      0·
      2 months ago

      See that would be a good analogy if the fail was fun.

      Making a shit painting is still fun.

      Having to reinstall my OS because I ran pacman -Syu and now my computer won’t boot, and now I have to spend hours making things work again: not at all fun.

      Having my server run out of memory and freeze up instead of having a sane out of memory behavior the day before a long trip: not fun

      It’s also archaic, niche information. Do I want to learn how to make a kernel version that didn’t get installed right show up in grub? Fuck no. Do I want to google for the 100th time what command exists to register the encryption key for my hard drive in the TPM? Fuck no. What an absolute waste of life.

      Linux isn’t “I cut a hole in my wall” it’s “my electrician only documented the wiring in hieroglyphs and now I have to reverse engineer everything to turn on a light bulb”.

  • easily3667@lemmus.orgEnglish
    0·
    2 months ago

    Unbootable systems in the dozens. I think I’ve only fucked up the kernel itself a few times. But grub or other bootloader tons, desktop environment tons, and getting into states so broken the only readily available option was reinstall, dozens. Thankfully most of these were right after a fresh install. For example dual booting just doesn’t work right for some OS installers and grub fails. Manjaro bricked itself after an update. Etc. etc.

  • gonzo-rand19@moist.catsweat.com
    0·
    2 months ago

    I’m on my second install now. I fucked up the first one pretty handily by accidentally wiping the boot partition in gparted. (Like a complete idiot, because the partitions are labeled.)