Tinkering is all fun and games, until it’s 4 am, your vision is blurry, and thinking straight becomes a non-option, or perhaps you just get overly confident, type something and press enter before considering the consequences of the command you’re about to execute… And then all you have is a kernel panic and one thought bouncing in your head: “damn, what did I expect to happen?”.

Off the top of my head I remember 2 of those. Both happened a while ago, so I don’t remember all the details, unfortunately.

For the warmup, removing PAM. I was trying to convert my artix install to a regular arch without reinstalling everything. Should be kinda simple: change repos, install systemd, uninstall dinit and it’s units, profit. Yet after doing just that I was left with some PAM errors… So, I Rdd-ed libpam instead of just using --overwrite. Needless to say, I had to search for live usb yet again.

And the one at least I find quite funny. After about a year of using arch I was considering myself a confident enough user, and it so happened that I wanted to install smth that was packaged for debian. A reasonable person would, perhaps, write a pkgbuild that would unpack the .deb and install it’s contents properly along with all the necessary dependencies. But not me, I installed dpkg. The package refused to either work or install complaining that the version of glibc was incorrect… So, I installed glibc from Debian’s repos. After a few seconds my poor PC probably spent staring in disbelief at the sheer stupidity of the meatbag behind the keyboard, I was met with a reboot, a kernel panic, and a need to find another PC to flash an archiso to a flash drive ('cause ofc I didn’t have one at the time).

Anyways, what are your stories?

  • emly_sh
    link
    fedilink
    English
    51 year ago

    I’ve not broken my setup (yet), but I’ve came close to it one time when I accidentally made a lesser fork bomb.

    I was writting a function that would display how many jobs I currently had in the command prompt, but when writting the function instead of calling jobs I called the function itself, sourced .bashrc and now everything was laggy (my pc only has 4GB). Thankfully I was able to shut down the terminal before my swap got completely consumed.

  • @[email protected]
    link
    fedilink
    71 year ago

    I ran firejail config or something, which replaces a lot of home directory app files. Not sure if binaries or desktop entries.

    But things broke, randomly, screenshots not working, not even inside firefox etc. I reinstalled the system and imported the home folder… and it was there again!

  • bitwolf
    link
    fedilink
    4
    edit-2
    1 year ago

    The only time was within a VM. I accidentally wrote

    rm -rf ./* while my cwd was /

    I use absolute paths with -rf now, to prevent the error again.

    Every other breakage I had was with apt shitting itself. It has always been fixable just annoying.

    I now use Fedora, to prevent the error again.

  • Doctor MoodMood
    link
    fedilink
    6
    edit-2
    1 year ago

    I had issues with a new version of glibc that prevented me from working on music in Ardour on Manjaro. I then proceeded to force-downgrade glibc (in the hopes of letting me get back to work) and that broke sudo and some other things, which I found out after rebooting. That was an interesting learning experience. Now I snapshot before I do stupid stuff. :]

      • @[email protected]
        link
        fedilink
        English
        101 year ago

        Oh no, this was back in the days when we loaded our distros by way of a stack of floppy disks.

    • @[email protected]
      link
      fedilink
      21 year ago

      Top tip, if tired, replace the rm -f part of the command with something innocuous for a first run. Actually, is better to do this mistake once so that the two important lessons are learned… Backup (obviously, in your case it was backups, but the point still stands) and double check your command if it has potential for destruction 👍

  • @[email protected]
    link
    fedilink
    171 year ago

    I don’t know if that counts, but on a fresh default Debian Stable system, my cat walked across the keyboard and the DE crashed.
    I could still switch to another TTY and reboot via command line.
    After the reboot, I was greeted by a blinking cursor and nothing else. Had to reinstall.

  • @[email protected]
    link
    fedilink
    121 year ago

    Not strictly Linux related, but in college I was an IT assistant. One day I was given a stack of drives to run through dariks boot and nuke.

    I don’t remember exactly what happened, but I think midway through, my laptop shut off.

    Guess who picked the wrong drive to wipe with DBAN :)

  • msmc101
    link
    fedilink
    241 year ago

    First time trying Linux I went with an arch install because I Googled “best version of Linux” and went with arch. Followed a guide to the point of drive formatting and I decided to go with a setup with drive encryption. I didn’t understand what I was doing, ended up locking myself out of my hard drives and couldn’t get windows to reinstall on them. I used a MacBook for a week until I installed Ubuntu and managed to wipe and reset my drives and reinstalled. Needless to say I am going to read up a little more before I try that again.

    • @[email protected]OP
      link
      fedilink
      121 year ago

      Been there, and even without encryption: took me to reinstall a few times before I realized I can chroot again and repair 😅

    • @[email protected]
      link
      fedilink
      51 year ago

      Archinstall python script is your friend 😄😉 I tried install arch manually, but as I learned that not even sudo is included in the Linux essential packages, I stopped the process and went back to aromatic script install, lol, got no time for that S*** 😂

  • BlueÆther
    link
    fedilink
    141 year ago

    I’ve broken systems far too many times in the last 24 years, since Mandrake 6.x, to count:

    • I’ve dd a disk or more
    • I’ve rm *
    • I’ve chmod
    • I’ve brought down the network, with every intention tar it would come back - on a remote box
    • I’ve failed to RTFM far too many times
  • @[email protected]
    link
    fedilink
    51 year ago

    I recently broke the networking stack by uninstalling ca-certificates

    I was using a slightly risky command to delete unneeded packages, and for some reason ca-certificates was on the list

    At least the fix was simple. Boot the rescue iso and reinstall them

  • jan teli
    link
    fedilink
    121 year ago

    I once deleted the network system in alpine. I’d been having some trouble with with the default one (I think wpa_supplicant) so I decided to try the other one (I think iwctl). But I thought that there might be problems with havung both of them so before I installed iwctl I deleted wpa_supplicant (thinking that it was more of a config utility than the whole network system), only to find that I couldn’t connect to the internet to install iwctl.

  • Dandroid
    link
    fedilink
    91 year ago

    It was my first time using a Linux GUI. I was comfortable with CLI, but it was my first time having it installed on a laptop instead of just sshing into a server somewhere.

    So naturally, instead of learning how the GUI worked, I tried changing it to be exactly like Windows. I was doing things like making it so I could double click shell scripts and other code files and they would run instead of opening them up in an editor. I think you see where this is going, but I sure as hell didn’t.

    Well, one of my coworkers comes over and asks me to run this code on this device we were developing. We were still in the very early stages of development, we didn’t even have git set up, so he brought the code over on a USB stick. I pop it into my laptop. I went to check it once by opening it in an editor by double clicking on it… Only it ran the code that was written for our device on my laptop instead of opening in an editor.

    To this day, I have no idea what it did to fuck my laptop so bad. I spent maybe an hour trying to figure out what was wrong, but I was so inexperienced with Linux, that I decided to just reinstall the OS. I had only installed it the day before anyway, so I wasn’t losing much.

  • @[email protected]
    link
    fedilink
    131 year ago

    Not the installation strictly speaking, but my most “funny” fuckup was setting up xfree86. There was a configuration for crt monitor scan frequency that you had to setup. I messed up something and the monitor started to squeel like crazy and quickly hit hard reset in panic.

    The monitor didn’t die, but it had a slight high pitch noise to it after.

    • aard
      link
      fedilink
      111 year ago

      Back then I was testing modelines to see the maximum I could push to my 14" monitor. I then backed it with a 1200x1600 virtual screen.

      My girlfriend got sick from watching me scrolling around and bought me a 19" display which could do that resolution - and ended up frustrated when I added a larger virtual screen.

      • @[email protected]
        link
        fedilink
        21 year ago

        A 19" monitor was quite big for the day, and expensive! I hope your gf didn’t beat you up too much for that :)

    • @[email protected]
      link
      fedilink
      21 year ago

      I know little about crt because I was born in 2000. Can you explain why did the monitor started to make scary sounds?

      I know that crt monitors didn’t have any method to report the supported frequency, aside from more recent models, correct?

      • @[email protected]
        link
        fedilink
        31 year ago

        Yeah, monitors were somewhat dumb, just received and did what the vga output asked to do.

        The noise most likely came from the semiconductors that controlled the magnet field that directed the rays onto the screen. These components are selected for a specific speed that the monitor can handle. So going under or over it’s spec can make something resonate in the audible range, and could even destroy the components if stressed too much.

        The thing is that for each resolution and refresh rate you had two values to configure, one for the vertical speed in Hz, and horizontal speed in kHz. These values were usually specified in the owners manual. Typos can happen, and this was quite a risky operation.