sudo chmod 664 * screwed me over

Discussion in 'MacBook Pro' started by MiracleWhip, May 23, 2011.

  1. MiracleWhip macrumors newbie

    Joined:
    May 23, 2011
    #1
    So I had a blue tint problem after screensaver and a website told me that using this in terminal would work. sudo chmod 664 * Now my computer is back to the way it first was but still with everything on it just old wallpaper and old dock. Help!
     
  2. Mackilroy macrumors 68040

    Mackilroy

    Joined:
    Jun 29, 2006
  3. MiracleWhip thread starter macrumors newbie

    Joined:
    May 23, 2011
    #3
    Nvm I fixed it just used the 777 command and restarted. Thanks anyways.
     
  4. Mackilroy macrumors 68040

    Mackilroy

    Joined:
    Jun 29, 2006
    #4
    Not a good idea – 777 leaves your computer vulnerable. You shouldn't ever use sudo chmod, really.
     
  5. adamZero macrumors newbie

    Joined:
    May 23, 2011
    #5
    "sudo chmod" is never* a good idea. While `sudo chmod 777 *` may have fixed your problem short-term, this could be a security loophole.

    But fear not! Repairing disk permissions may be able to correct the problem. So try that ;)



    *unless used precisely and you know what the effects will be
     
  6. Detrius macrumors 68000

    Joined:
    Sep 10, 2008
    Location:
    Asheville, NC
    #6
    Even repairing permissions still won't fix it. That only repairs permissions on stuff installed via Apple's installer. Applications installed via Drag'n'Drop will not be fixed, and home directories will also not be fixed.

    If you have a time machine backup, you're better off restoring from that.
     

Share This Page