I’m working on a some materials for a class wherein I’ll be teaching some young, wide-eyed Windows nerds about Linux and we’re including a section we’re calling “foot guns”. Basically it’s ways you might shoot yourself in the foot while meddling with your newfound Linux powers.

I’ve got the usual forgetting the . in lines like this:

$ rm -rf ./bin

As well as a bunch of other fun stories like that one time I mounted my Linux home folder into my Windows machine, forgot I did that, then deleted a parent folder.

You know, the war stories.

Tell me yours. I wanna share your mistakes so that they can learn from them.

Fun (?) side note: somehow, my entire ${HOME}/projects folder has been deleted like… just now, and I have no idea how it happened. I may have a terrible new story to add if I figure it out.

  • pmk@lemmy.sdf.org
    581·
    7 months ago

    I wanted to try inserting and removing kernel modules, so I looked around and thought “well, I don’t have a USB stick in right now so I can safely try removing the usb kernel module.” So I did that, and after pressing enter I realized my keyboard is connected with USB.

    • flubba86@lemmy.world
      16·
      7 months ago

      I was smug thinking “I haven’t done anything so silly as the people commenting in this thread”, then I came across this one. I’ve actually done this one, and it was earlier this year, and I’ve been using Linux since 2004, 20 years.

  • inetknght@lemmy.ml
    49·
    7 months ago

    1. have an nvidia GPU

    2. have Fedora

    3. download RPM package of drivers for Red Hat (after all, Fedora and Red Hat are… compatible, right?)

    4. Everything goes fine

    5. Six months later, upgrade to a new version of Fedora

    6. oops, kernel panic at boot after the upgrade, and no video to troubleshoot after UEFI boot

    7. figure out how to boot into a recovery partition from UEFI

    8. figure out how to enable a serial console over a USB device

    9. figure out how to connect to the serial console from another computer using another USB device

    10. figure out what the kernel panic is from (not the upgrade, but the driver which wasn’t upgraded)

    11. figure out how to uninstall the incorrectly installed driver

    12. figure out how to install the correct driver

    That was a fun three week OS upgrade.

      • macniel@feddit.de
        9·
        7 months ago

        You attach a secondary computer via serial (COM port) with your primary computer and then you can open a console on that one. You can access the primary computer as if you would be sitting in front of it.

      • AngryPancake@sh.itjust.works
        5·
        7 months ago

        Adding to what DmMacniel said, it’s a hardware interface, often accessed via a USB port (which after all, is the universal serial bus).

        • FigMcLargeHuge@sh.itjust.worksEnglish
          6·
          7 months ago

          Christ you guys are making me feel old. I remember back in the day when a serial connection was made through an actual serial port. I know I have some serial cards around here somewhere. I have also used the tar command on an actual tape… Here’s a fun fact, if your tape drive (big reel to reel looking thing, not a cassette or other kind of ‘tape’) has an issue with rewinding, do not use your finger to manually spin the reel. Use a pencil. I finished reeling my tape back up once and realized I now had a blister on the end of my finger.

      • inetknght@lemmy.ml
        4·
        7 months ago

        https://en.wikipedia.org/wiki/Serial_console

        tl;dr:

        Serial ports are (for example) commonly RS-232, although other types of ports exist. Imagine it to be a very slow Ethernet device. Because it’s so slow (and the technology predates Ethernet and also has different requirements), it’s usually attached directly to a device instead of to a network. But you could connect a modem to it and it becomes connected to a network device.

        It could also be connected to a system console device. These are commonly called terminals. Such devices are often monochrome (especially older ones) because a serial connection is often bandwidth limited (eg, measured in kilobits per second instead of megabits or gigabits). Since it’s so slow, it’s not practical for video, so it’s generally just text-only.

        Note that your GPU might also output a system console but rendered on your display at very high resolution and with graphics-drawing capabilities. So a system console would be any console that connects to the system.

        What is a console? Well, Wikipedia presents several valid articles and the common theme as far as computers go is that a “console” is typically something that a human and a computer use to interact with each other.

        For serial consoles, you might find device files for them at /dev/tty*. But for general serial devices, it could be any of several different types of device files.

        Wikipedia’s article on /dev devices has a pretty decent listing of what kinds of devices you might find and several of them might be classified as a serial port. Any serial port might be connected to a serial console.

        So in my case, a serial console is:

        1. 2x USB-to-RS-232 (USB is a serial protocol and is basically “just” another (Universal) (and perhaps high speed) Serial port (Bus), so conversion is super cheap)
        2. 1x RS-232 null modem cable

        That’s pretty much it in a nutshell. Then

        1. System 1 (the failing system) UEFI boots into repair system partition on a separately attached disk (eg, boot from CD or live USB) to get a local system console
        2. System 1 repair system mounts the failing system partition
        3. System 1 modifies failing system grub configuration to enable a serial console on the attached USB-to-serial device file and saves changes, then unmounts failing system partition
        4. Power off System 1
        5. Remove repair partition device
        6. Open terminal window on System 2 (recovery system)
        7. Connect System 2 terminal to the attached USB-to-serial device file using screen (oh wow those were some old days)
        8. Power on System 1
        9. System 1 boot enters grub recovery menu which allows fixing the system remotely

        To be fair, a lot of that complexity could have been done by either reinstalling, or removing the hard drive and attaching it to another computer. But doing it this way allowed me to poke around and try different ways of solving the issue, rebooting, etc. It was a learning experience worth exploring.

        It was years ago though and I think there was some complication with trying to understand what device file (or device number or something) needed to be to work on the correct serial device (there are often multiple)

  • boredsquirrel@slrpnk.net
    44·
    7 months ago

    I tried to install an OS to a USB stick. This is Kubuntu specific.

    You need to create a GPT partition on the stick, then you should be able to just use the installer and install on another USB stick.

    I went through it, selected the usb stick… was not sure if everything was right and went a menu back, was correct, went forth again, past the install target selection and installed.

    Well… turns out the Kubuntu installer (Calamares) selects the first disk always. And that selection seems to reset to default when going a menu back…

    I deleted my complete normal disk, with like everything I had.

    No Backup no mercy. Luckily did one only a few weeks before. The first since half a year! Damn… had my uni stuff on Nextcloud, a lot of personal stuff synced to my phone with syncthing.

      • boredsquirrel@slrpnk.net
        2·
        7 months ago

        I mean if you actually want to overwrite the main SSD this is okay. Calamares is very nice too.

        Kubuntu stays on Plasma 5 forever so I highly recommend against it. There are many bugs that will not get fixed, the fixes are only in Plasma 6.

        I recommend Fedora Kinoite. Use Flatpaks, layer the packages you dont need. Add rpmfusion and layer libavcodec-freeworld to get video playback working.

        I broke all KDE distros, Kubuntu included. I wouldnt use anything other than Fedora Kinoite, nor want to maintain that mess. Have a look at my latest post for some explanations.

          • boredsquirrel@slrpnk.net
            1·
            7 months ago

            Yes it is stable. Stable means you ship packages that dont change. Which in general is a really bad idea if you want your issues to be solved.

            The timing was just really bad, as Plasma6 now is perfectly usable. Bad decision if you ask me.

            At least on Fedora Plasma6 is really good.

              • boredsquirrel@slrpnk.net
                3·
                7 months ago

                It is a very experimental repackaging of Fedora, ripping out SELinux and replacing that with Apparmor, which will be way less secure as it is not the focus. They add a ton of custom stuff but the Distro is still mutable.

                If you want that amount of tweaking, I recommend Bazzite. There you will have reproducible bugs and rollbacks.

  • theroff@aussie.zone
    33·
    7 months ago

    ntfsclone /dev/sdc /dev/sdb

    /dev/sdb was a blank filesystem and /dev/sdc was my Windows filesystem.

    ntfsclone man page

    It ran for less than a second and didn’t take me long to figure out what happened. That’s the story of how I stopped using Windows.

    • diffusive@lemmy.world
      2·
      7 months ago

      I don’t use windows for close to 20 years so I didn’t need ntfsclone so far but do I read correctly the man page that only the source is specified as positional parameter? If so, shouldn’t you have to write

      nftsclone —overwrite /dev/sdc /dev/sdb? It still can be misleading (given that mv uses two positional parameters so mv -f source destination would have done what you wanted) but a bit less cryptic?

      • theroff@aussie.zone
        7·
        7 months ago

        Yeah, sorry it was a long time ago (like 10+ years) but I checked and it would’ve been the --overwrite arg.

        The manpage for the older ntfsclone command has it:

        Clone NTFS on /dev/hda1 to /dev/hdc1: ntfsclone --overwrite /dev/hdc1 /dev/hda1

        Moral of the story was to RTFM 😂

        • AnarchistArtificer@slrpnk.netEnglish
          2·
          7 months ago

          (RTFM = Read the Fucking Manual)

          Adding this because I only learned this acronym just last week, and wish to share the knowledge with anyone else like me)

  • Morphior@feddit.de
    321·
    7 months ago

    If you count Android too, then this: I got my first Android phone when I was 10 or 11 and rooted it on the first day of having it. This was during a time when we were all still using ClockworkMod because TWRP didn’t exist yet, and I somehow ended up with a system without a kernel. Panic ensued, and I spent that entire night (like 10 hours) digging through xda in order to find a tutorial on how to get this damn phone to run again. Imagine having to tell your parents “I broke my phone I got yesterday.” I did get it working at like 6:30 AM. Fun times.

    • isolatedscotch@discuss.tchncs.de
      21·
      7 months ago

      what’s the fun in modding if not the two hours where you think you’ve bricked everything and you’re scrambling through a 52 page post on XDA trying to find someone with your same problem

    • JustARegularNerd@aussie.zoneEnglish
      5·
      7 months ago

      I did pretty much exactly this on a Galaxy S1 (i9000) that was old even when I got it, but my uncle who gave it to me said that to make it usable I needed to install Cyanogenmod.

      I thought I fully bricked the phone trying and it actually sat dormant for years afterwards until I re-found the Odin backups I had taken, and was able to fully fix and restore it. Unfortunately by that time, nearly no ROM existed that was both up to date and a usable speed.

    • AnarchistArtificer@slrpnk.netEnglish
      3·
      7 months ago

      Oh man, Clockwork mod, that takes me back. Although I had my android phone for a while before I built up the courage to root it, in part due to stories like yours

  • mackwinston@feddit.uk
    28·
    7 months ago

    An older friend of mine told me years back about an incident that happened on a university VAX running Unix. In those days, everyone was using vt100 terminals, and the disk drives weren’t all that quick. He was working on his own terminal when without warning, he got this error when trying to run a common command (e.g. ls)

    $ ls -l
sh: ls: command not found

    So he went on over to the system admin’s office, where he found the sysadmin and his assistant, staring at their terminal in frozen horror. Their screen had something like:

    # rm -rf / tmp/*.log
^C^C^C^C^C^C^C^C^C^C
# ls -l
sh: ls: command not found
# stat /bin/ls
sh: stat: command not found

    A few seconds after hitting return, and the rm command not finishing immediately, he realised about the errant space, and then madly hammered Ctrl-C to try to stop it. It turns out that the disk was slow enough that not everything was lost, and by careful use of the commands that hadn’t been deleted, managed to copy the executables off another server without having to reinstall the OS.

  • slembcke@lemmy.ml
    25·
    7 months ago

    I totally pulled a LTT and removed my kernel. >_< There was a “real time” kernel listed in apt, and I installed it because I was curious if it would reduce lock latency for a project I was working on. (I wasn’t trying to solve a problem, just curious) It didn’t and I figured it was probably a bad idea to leave it installed. So I did an apt remove, and the rest went something like this.

    Apt: Are you sure you want to remove the your kernel? Y/N

    Me: Oh jeez… I don’t want to do that.

    Motor Memory: Y <return>

    Apt: Are you really really sure? Your computer will not boot if you do this. Y/N

    Me: Oh, crap! That’s not what I meant to do. Definitely not!

    Motor Memory: Y <return>

    Me: No! Why would my brain betray me!?

    Fortunately this was on a PopOS machine, so I booted into the recovery partition. Even if fixing it only took a minute, I still felt very very dumb. >_<

    • AnarchistArtificer@slrpnk.netEnglish
      9·
      7 months ago

      Man, that’s a really dumb story that I find really relatable despite not having had any experiences like that. It feels like it’d be very in character for me though. Thanks for sharing, it helps me feel less silly in the various times where I’ve messed up (of which I am struggling to recall specific examples, but whatever brain part is responsible for embarrassment can remember, apparently)

  • KISSmyOSFeddit@lemmy.world
    24·
    7 months ago

    The dumbest must have been when I went through the list of installed packages on Debian and removed everything named “python-…” since I don’t program in python.

  • bloodfart@lemmy.ml
    241·
    7 months ago

    Everyone here is talking about rm, but when’s the last time you dd’ed the wrong thing by accident?

    You can get tripped up by tab completion, hda vs sda, sda vs sdb, flipping the articles around, he’ll, I’ve even blasted a good drive with /dev/random because I did t pay attention to what computer I’m logged into.

    My killer app for multiple terminals open at once, weather through several ttys, xterms, tmux or the other one I don’t use was to type out my dd commands with a ls or something safe making in front of it while I look back and forth compulsively to verify that all the targets are correct.

    • ____@infosec.pub
      12·
      7 months ago

      Only reason dd hasn’t bitten me is that in my head, if and of make perfect sense as input and output.

      Doesn’t mean I won’t make that error tomorrow, ofc. But I tend not to alias except harmless stuff to avoid that very problem.

    • Bhaelfur@lemmy.worldEnglish
      7·
      7 months ago

      Yup, I did that last year. I wrote a Linux ISO to my hard drive instead of a flash drive. It was interesting watching my desktop slowly fail. Thankfully I was preparing a switch to a different distro, so I had backed up what I needed.

      • No1@aussie.zone
        9·
        7 months ago

        All my drives are nvme* now.

        I feel so much safer punching in of=/dev/sdaX

  • ReCursing@kbin.social
    20·
    7 months ago

    Way back when I was just beginning to experiment with Linux back in the 90s I installed ZipSlack, which was a GUIless 100MB distro based on Slackware that ran from a folder on Windows. It was okay but I couldn’t really do much with it and back then 100MB was a chunk of space, so i went to delete it. But i thought I would give it one last hurrah by deleting it from Linux. So I made use of the infamous rm -rf and sat there thinking “this is taking a long time”… then realised I had my Windows drive mounted as a sub folder and I was in the process of wiping my hard drive of everything!

  • unalivejoy@lemm.eeEnglish
    20·
    7 months ago

    I once removed all groups from my user by using usermod -g instead of usermod -G

  • Aniki 🌱🌿@lemm.eeEnglish
    19·
    7 months ago

    I once tried to restore replication on a broken MySQL cluster by restoring the backup on the only good, running node.