Disclaimer: Do not run this command.

    • sanderium@lemmy.zipOPEnglish
      31·
      1 hour ago

      CHMOD command does not exist either. It’s just the meme’s font that is in all caps.

  • palordrolap@fedia.io
    802·
    5 hours ago

    Obligatory DO NOT RUN THIS ON YOUR COMPUTER (or anyone else’s).

    You’d think with fully open permissions, everything would work better, but many programs, including important low level things, interpret it as a sign of system damage and will refuse to operate instead.

    If you do run it, you’d better have a backup or something like Timeshift to bail you out, and even if you do have that, it’s not worth trying it just to see what will happen.

    It’s not quite as bad as deleting everything because you can boot from external media and back up non-system files after the fact, but the system will almost certainly not work properly and need to be repaired.

    You have been warned.

    • LastYearsIrritant@sopuli.xyzEnglish
      37·
      4 hours ago

      New guy at work ran this to try to fix permissions on his home folder, accidentally ran it on root (both would have been bad)

      Several highly paid and experienced Linux admins finally just gave up and deleted the server and built a new one from the backups.

        • Cenzorrll@lemmy.world
          1·
          1 hour ago

          I learned this relatively quickly running my own server with the intention of my family also using it. Data on a separate drive, backed up regularly and automatically. System on it’s own drive, dd’d when it’s in it’s final state and backed up before I screw around any deeper than trying out a new container. I can bring my server back up in however long it takes to transfer data.

    • dan@upvote.au
      9·
      3 hours ago

      Windows perms are pretty locked down though. Sometimes I can’t delete my own files because I need permission from “Administrator” :/

      You can actually use Windows-style permissions (ACLs) on Linux via setfacl.

        • Ooops@feddit.org
          1·
          22 minutes ago

          File permissions…

          allowed to execute=1, allowed to write=2, allowed to read=4

          grouped by owner/group/everyone.

          So one of your own files you have full access to while users in your usergroup are only allowed to read it and nobody else has any permissions would have: 740 (read+write+execute / read / none).

        • TheTechnician27@lemmy.worldEnglish
          25·
          3 hours ago
          • sudo is telling the computer to do this with root privileges.
          • chmod sets permissions.
          • Each digit of that three-digit number corresponds to the owner, the group, and other users, respectively. It’s 0–7, where 0 means no access and 7 means access to read, write, and execute. So 077 is the exact inverse of 700, where 077 means “the owner cannot access their own files, but everyone else can read, write, and execute them”. Corresponding 700 to asexuals is joking that nobody but the owner can even so much as touch the files.
          • / is the root directory, i.e. the very top of the filesystem.
          • The -R flag says to do this recursively downward; in this case, that’s starting from /.

          So here, we’re modifying every single file on the entire system to be readable, writable, and executable by everyone but their owner. And yes, this is supposed to be extremely stupid.

            • Cenzorrll@lemmy.world
              2·
              52 minutes ago

              Just wait until you need to figure out what you want when you want something other than all or none for those permissions. 4 is read, 2 is write, 1 is execute. Add them up to get what you want for each owner/group/other portion.

        • KickMeElmo@sopuli.xyz
          6·
          4 hours ago

          7 is read, write, and execute permissions. 700 is owner, but not group or others. 077 means the owner has no permissions, but group and others all have full permissions.