Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: The results of sudo chmod 777 /.*

  1. #11
    Join Date
    May 2009
    Beans
    19

    Talking Re: The results of sudo chmod 777 /.*

    0
    Quote Originally Posted by sisco311 View Post
    Try to boot in recovery mode and restore the permissions:
    Code:
    chmod 0755 /
    chmod 0755 /*
    chmod 1777 /tmp
    chmod 0750 /root
    chmod 0700 /lost+found
    If you can boot in recovery mode, then boot a liveCD, mount the root partition and restore the permissions.

    sisco311,


    It seems that ubuntu works exactly as before after I changed the root permission according to your advice in the recovery mode (is there anythings else I need to do now to be sure ubuntu is fully restored?).
    So thank you, and thanks all the other for trying to help (and I also want to thank god I was not listening to their advice )


    What other dangers should I be aware of in this respect, and does ubuntu have any option of restoring itself (In my case, I must sudo many times in different ways, and it is impossible not to make simple misprints sometimes)

  2. #12
    Join Date
    Apr 2009
    Beans
    275

    Re: The results of sudo chmod 777 /.*

    LOL, this is why you always get a second (or sometimes, sixth) opinion.

    I think you should be okay now, since you essentially undid what you did in the first place and just set the permissions back. Just watch for anything unusual, and check if permissions are the problem if something else breaks.

  3. #13
    Join Date
    Nov 2008
    Beans
    30
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: The results of sudo chmod 777 /.*

    Uhm, I did this stupid thing also mistakenly...
    Should Ubuntu to make a confirm messange for only the input arg '/'?

  4. #14
    Join Date
    Oct 2005
    Location
    Carterville, IL, USA
    Beans
    211
    Distro
    Ubuntu UNR

    Re: The results of sudo chmod 777 /.*

    Quote Originally Posted by danger89 View Post
    Uhm, I did this stupid thing also mistakenly...
    Should Ubuntu to make a confirm messange for only the input arg '/'?
    Well, there are two problems with what you and the original poster did. First of all, if you own the directory, you shouldn't use sudo. Just doing chmod without sudo would have worked just fine.

    Second of all, there is no reason to run
    Code:
    chmod 777 ./*
    You can run
    Code:
    chmod 777 *
    and it will give you the exact same results, but there is practically no chance that you will accidentally change your root directory's permissions.

    Putting a warning message might not really hurt anything, but there are a million commands that someone can run to screw up their system, and it would be difficult and annoying to have confirmation messages for them all.

    - Derrick

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •