• Vilian@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      22 days ago

      I remember this lol, to be fair no one knew how the guy managed todo it, because steam(the launcher) has checks for that, they assume the guy tried to run the steam command instead of clicking the launcher(don’t do that)

            • slacktoid@lemmy.ml
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 days ago

              Makes sense… I was curious what your solution was… Sounds like I should invest some time into that … Thanks.

              • raspberriesareyummy@lemmy.world
                link
                fedilink
                arrow-up
                2
                ·
                edit-2
                2 days ago

                On debian testing (trixie):

                $ cat bin/steam-jailed.sh

                #!/bin/sh
                firejail --private=/home/user/steamjail --profile=/etc/firejail/steam.profile ~/steam $1
                

                Sometimes an update breaks something, and I have to experiment with the profile settings, for which it helps to launch a bash with the same jail and start steam on the command line inside the jail to see output messages.

                #!/bin/sh
                firejail --private=/home/user/steamjail --blacklist=${HOME}/.inputrc --profile=/etc/firejail/steam.profile bash
                

                What happens most of the time is that a steam update depends on a newer system library that I didn’t yet install and I then have to do a system update - steam is shit at managing OS dependencies (i.e.: it doesn’t)

    • Martin@feddit.nu
      link
      fedilink
      arrow-up
      0
      ·
      22 days ago

      There is a wild card * that will remove everything in the current directory (and remove /tmp too)

    • exu@feditown.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      23 days ago

      I ran the command without sudo first. It had a bunch of permission errors removing stuff in /tmp. So I retried but with sudo

      • superkret@feddit.org
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        22 days ago

        /tmp is world-writable. If you get permission-errors, you should become suspicious.
        Also, whenever you write “sudo rm -rf” you should quadruple-check if that’s really what you want to do.
        Non-interactively deleting entire directories in root space isn’t something you should have to do normally.