Down that hole

  • GingerPale@lemmy.world
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Also, anyone who says “try this, it’s neat”:

    :(){ :|:& };:

    Don’t. It’ll lock up your computer. The markdown is adding code to the above. Ignore the “amp;”. It’s just an ampersand.

    Also anyone who tells you run level 6 is the best one…

    Don’t. It’ll set you in a boot loop.

    Basically, Google whatever someone suggests to you just to verify they’re not being a dick. I would say spend a bunch of time in the command line interface (CLI). There’s nothing wrong with the GUI desktop, but the real power of Linux is in the CLI because you can do so much with it. It’ll also get you on the road to scripting, if you’d like. That unleashes the power even more by making your Linux box so cool stuff on its own. Then learn the power of cron tables (crontab) so that you can schedule your computer to do cool things on its own.

    Good luck and have fun!

    • d3Xt3r@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      A fork bomb no longer works on modern distros which use systemd btw, since systemd imposes limits on the user and system cgroups (IIRC, a user can’t have more than ~10,000 tasks or something).

      • ditherwither@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        If you are low on memory, a fork bomb still works

        I can confirm that it crashed my laptop running fedora 36 (this was a while ago lol)

        • d3Xt3r@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Just tested and confirm it doesn’t work on Fedora 38. When you run it, you get an error saying:

          bash: fork: retry: Resource temporarily unavailable.

          It still does the loop, but doesn’t slow down the system or anything, and you can easily close the terminal window.

          As I said before, systemd imposes cgroup limits per user so fork bombs no longer work.