Well guys...i've made a big mistake.I've changed accidentally the permission of the root folder (not /root,but / )
Since then,all my applications and servers are messed out.What i can do to change it back without reinstalling the OS.
Thanks.

How exactly did you change it? Recursively or not? Do you have the command you used? If only one or two files are changed, you can restore it. If it was done recursively, there's probably no way to change it back.

Hello Legolas891

Have you only changed the permissions of the / directory or have you changed the permissions on sub-directories and files?

Best

Recursively...i used chmod -R 777 /some-dir..and after that i wanted to erase it..and i accidentally hit enter when the pointer erased some-dir. :|
After i noticed,i wanted to change it back...and used 666,but i did much more damage than the first time :|
Isn't there a program that checks all the vital files permissions,or something like that?

Please fill in your distro details in your user profile.
It may help us help you faster/more efficient/qualitatively better.

Sorry, your best bet is a reinstall. I don't think such extensive damage is reparable, and even if it is, reinstalling will be much faster.

Depending on the distribution that statement may be false or true. Without knowing those details I think it's at least premature to say that.

I have OpenSUSE 11.There isn't any other option?I don't want to reinstall the OS.I have apache,mysql,ftp,and other servers,script and other stuff...and i don't want to do all the hard work of configuring all of them...

If you say so. Which distributions can be easily repared after a total screw up of the root directory?

You should, of course, save all you data as well as configuration files before reinstalling. Their content should not be affected.

The SuSE installer CD has a repair option which can fix problems. I don't use SuSE but the command 'rpm --setperms' (or 'rpm -qa | xargs rpm --setperms' or maybe 'rpm -a --setperms') should do the same. After you're done it can also verify packages which should be the equivalent of running 'rpm -qVva'. The only requirement for all of this is that the RPM database exists on the disk or on a backup medium.

Hm... You might be right here. I'll make a note of that.
http://www.cyberciti.biz/tips/reset-...ermission.html

I've trided 'rpm -qa | xargs rpm --setperms' but it gaves me a lot of 'No such file or directory'

Maybe a security auditing program would help. Perhaps udate-test-security or yast2-security, if run, would be able to diagnose and fix the problems.

Actually, the YaST2 submenu 'Security' should, I think, be able to fix it. SuSE, back when I used it (8.2), had preset permissions settings in the /etc/ file (these files being permissions, permissions.easy, permissions.secure, and permissions.paranoid.) These settings could be accessed by YaST2 under the submenu 'Security'.

Ok,i'll give it a try.But the problem is that the ssh server won't start...

L.E.-It's started..but it rejects my connection.
It says:
ssh_exchange_identification: Connection closed by remote host
And with -vv:
OpenSSH_5.1p1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to "ip" port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
ssh_exchange_identification: Connection closed by remote host

Do you need the ssh server to check YaST? Presumably YaST is on your local machine. Open the YaST control centre and click the "Security and Users" menu item. There might be something there to assist you, I would think.