What are some of the easiest ways for a beginner to make their system untable when they start tinkering with it?

  • node815@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 minutes ago

    Instability you ask? This is like a slow creep to instability and freeze your system. It’s called the Bash Fork Bomb (look it up if you want), but it’s a copy/paste you put in and it slows your system down by consuming all the system resources and cause it to lock up HARD. It goes away after a system reboot, though.

    I was going to post the code here, but decided to play nice. But if you are curious:

    https://itsfoss.com/fork-bomb/

    (edit: Made ‘slow’ ‘slows’)

  • superkret@feddit.org
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    2 hours ago

    Go through all installed packages and remove “bloat”.
    Add third party repositories.

    • Lantern@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      4 minutes ago

      Removing bloat doesn’t necessarily make things unstable. I remove all the games from my KDE Plasma installs. The primary mistake that can occur in removing non-essential programs is ignoring the list of programs that this is a dependency of or also removes.

    • Fonzie!@ttrpg.network
      link
      fedilink
      arrow-up
      5
      ·
      2 hours ago

      Ahaha. That hurts.

      Pro-Tip: Even if you don’t program in Python, it might be necessary for several of your applications.

  • HouseWolf
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 hours ago

    Trying to mount an iso image in the terminal and accidentally un-mounting your root drive.

    Totally didn’t do that before…nope not even once, definitely not twice >.>

  • perishthethought
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 hours ago

    Mess with grub, without really understanding what you’re doing.

    Also, “meep”.

  • theshatterstone54@feddit.uk
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    Apparently running an update on Fedora. My flatpaks were broken on Fedora 40, so I thought it’s a configuration issue on my part and did a clean reinstall when Fedora 41 came out. Issues were not present… until I ran an update.

  • vort3@lemmy.ml
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    3 hours ago

    Just my experience, I was unable to log in after trying to add samba to my installation. Had to boot into live usb and reset my password.

    Maube I’m just bad and it’s not samba.

    • N0x0n@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      2 hours ago

      Not sure if this is what happend, but there is a sync option in samba where you can sync your samba user password with login user password.

      However this needs explicitly be stated in the samba.conf and needs some further configuration. It could be possible that the installation fuckedup something with passwd.

      Just guessing here, I played a bit arround with samba and password syncing.

      • vort3@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        2 hours ago

        My thought as well. Maybe sync was in default configuration or I just copy pasted it without reading.

        Long story short, I have no idea if system user passwords and sama user passwords are the same thing, how to set them up (if they are not the same), or how to make samba use same user accounts and passwords (so that I don’t have to remember one more password). So I just gave up.

        I was trying to do everything according to arch wiki, but either samba is overcomplicated for no reason, or the article is just not written well.