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

  • needanke@feddit.org
    link
    fedilink
    arrow-up
    4
    ·
    26 days ago

    I think we are using linux very differently. Mine is two and one of those was a dead ssd.

    • OhVenus_Baby@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      24 days 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.

      • Fonzie!@ttrpg.network
        link
        fedilink
        arrow-up
        1
        ·
        24 days ago

        Sure, ok, that’s still my daily driver, it’s incredibly stable (and no, it’s not fucking outdated), but other than that it doesn’t help so much against accidentally borking your system.

        So in this context, I’m recommending @[email protected] NixOS.

  • mybuttnolie@sopuli.xyz
    link
    fedilink
    arrow-up
    4
    ·
    26 days ago

    Two. The first time I had nvidia related issues with nobara, so I removed nvidia drivers for reinstallation… And couldn’t figure out how to get them back. The second time I had used mint for long enough that I felt confident enough to nuke windows partition. I used gparted and nuked the whole disk instead.

    Not counting the times I tried fedora and it killed itself with the first updates and then with multimedia codecs.

  • nfreak@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    26 days ago

    I haven’t majorly fucked up any recent systems (almost botched the steam deck once or twice but nothing that required a reinstall), but god 10 years ago I probably reset my arch dual boot like five times lmao

  • MoonMelon@lemmy.ml
    link
    fedilink
    English
    arrow-up
    14
    ·
    26 days 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.org
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      26 days 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”.

  • Magiilaro@feddit.org
    link
    fedilink
    arrow-up
    12
    ·
    26 days ago

    Making errors and analysing them to figure out what went wrong and why is a huge part of learning. You can only learn so much from theory, some things can be learned best by trial and error and the experience gained from it.

    When I started with Linux I did choose to use Gentoo Linux because it was the most complex and complicated option, so I had the most opportunities to learn something by ducking up!

  • OhVenus_Baby@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    24 days 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.

  • arsCynic@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    24 days ago

    Nearly always it’s been during the live USB install of a dual-boot that a distro messes with the grub or installed grub to the USB disk itself. The fault lies with me because I’m almost blindly trusting the distro, but also with the distro for lacking proper yet succinct documentation during the install or configuration of partitions.

    • unhrpetby@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      25 days 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
        link
        fedilink
        arrow-up
        2
        ·
        25 days 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

  • Dudewitbow@lemmy.zip
    link
    fedilink
    arrow-up
    3
    ·
    26 days ago

    i broke debian on my plex server and said fuck it and migrated to endeavor because im more familiar with arch

  • Sock Puppet Society@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    25 days ago

    Both, to the point it doesn’t boot, and just tweaking enough bugs that it’s easier to jist start over.

  • collapse_already@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    25 days 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
      link
      fedilink
      arrow-up
      5
      ·
      25 days ago

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

  • thedeadwalking4242@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    26 days ago

    I’m not sure I’ve ever actually killed a system, I’ve booted from UEFI shell manually just to recover systems. Back when I was using arch id just chroot into the system from a flash drive and fix whatever ¯\_(ツ)_/¯