mgj how there will be comparable rm -rf / * this magical command, the thinking of the current directory permissions to 777, did not expect the next whole / whole directory is set to 777, where intuition tells me as if something was wrong, Fortunately, toss the final meal xjb somehow, should be nothing big problem, ah for now, it can be used normally.
Specific approach is to take a boot disk (not reinstall the system, although most of the recommendations reload online, I was almost too heavy, but tried holding on and hoping the psychological result like) into the startup disk click Try Ubuntu then enter the interface, open terminal, generally will automatically mount all partitions on a physical machine, locate the damaged system / directory and then open the terminal (yesterday patronize the repair, and did not leave a drawing to be a memorial), then use Sudo chmod ... ordered all directories / permissions changed under the normal system, I just happen to have a cloud Ali cloud server (but not Ubuntu, is Centos, was also holding a dead horse a living horse medicine mentality), and the server also installed to Road cloud (free version, of course, you can also use the command line), in accordance with the authority figure shows, one by one change on the line, then I will / etc / ssh in the file in accordance with the normal system of privileges changed next.
Also executed two commands:
cd /etc
chmod 644 passwd group shadow
chmod 400 gshadow
Other no problem, then restarting it to boot up (fortunately), other questions can be asked of the Mother resolved (to enter the system can be normal anyway, is valid and the other is not a big problem), this method of course I do not guaranteed universal, just to share my experience, if can save the next sad reminder of the child.
PS: are tears ah, the future use of this command is still cautious on us.
