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?

    • Black616Angel@feddit.de
      33·
      10 months ago

      source is a bash shell built-in command that executes the content of the file passed as argument, in the current shell.

      ~/.bash_history contains all the commands you ever executed in bash (the default shell in most Linux systems)

      • Kevin@programming.dev
        19·
        10 months ago

        To add on to this explanation, you generally use source ~/.bashrc to reload your shell whenever you want to make changes to your user config. Tab completion weakens the barrier to destruction significantly (esp. in my case)

        • Jordan_U@lemmy.ml
          5·
          10 months ago

          Until you use a system that doesn’t have a ~/.bashrc , and now your tab completion helpfully expands “~/.ba[TAB]” to “~/.bash_history” .

        • Black616Angel@feddit.de
          3·
          10 months ago

          That’s why I like fish, which shows matching commands you executed, so that you can easily redo them.