• BaumGeist
      link
      fedilink
      arrow-up
      3
      ·
      2 hours ago

      I’m gonna laugh if it’s something as simple as a botched fstab config.

      In the past, it’s usually been the case that the more ignorant I am about the computer system, the stronger my opinions are.

      When I first started trying out Linux, I was pissed at it and would regularly rant to anyone who would listen. All because my laptop wouldn’t properly sleep: it would turn off, then in a few minutes come back on; turns out the WiFi card had a power setting that was causing it to wake the computer up from sleep.

      After a year of avoiding the laptop, a friend who was visiting from out of town and uses Arch btw took one look at it, diagnosed and fixed it in minutes. I felt like a jackass for blaming the linux world for intel’s non-free WiFi driver being shit. (in my defense, I had never needed to toggle this setting when the laptop was originally running Windows).

      The worst part is that I’m a sysadmin, diagnosing and fixing computer problems should be my specialty. Instead I failed to put in the minimum amount of effort and just wrote the entire thing off as a lost cause. Easier then questioning my own infallibility, I suppose.

      • interdimensionalmeme
        link
        fedilink
        arrow-up
        1
        ·
        59 minutes ago

        A typo in fstab shouldn’t wreck the system. Why is that not resilient ? I added an extra mount point to an empty partition but forgot to actually create it in LVM.

        During boot, device not found and boot halted, on a computer with no monitor/keyboard