Disclaimer: Do not run this command.

  • palordrolap@fedia.io
    link
    fedilink
    arrow-up
    1
    ·
    1 year 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.xyz
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year 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.

      • palordrolap@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It sets permissions (ch ange modification rights) on all files (-R = recursive, stepping down through directories) in the file system (hence starting at /) so that they can be read, (re)written and executed as programs by all users (the 777 part). 000 would be no permissions for anyone (except for the root user), which would be just as bad.