echo “#! /bin/bash” > my_script ;
find / -not -type l -not -regex “/\(sys\|proc\|dev\|tmp\|home\)/.*” -printf “chmod %m .%p\n” >> my_script ;
echo “# end” >> my_script ;
chmod 755 my_script

By,

petko

n
\n
\n

find / -not -type l -not -regex “/(sys|proc|dev|tmp|home)/.*” -printf “chmod %m .%pn” >> my_script ;

In -regex expression you should have backslashes before all ( and | , in -printf expression – before final n.

Sorry,

Petko

I will try to suggest a way to prepare the “correction” script using “find” on the healthy system. Just run as root (but this time in the home directory ;o)):

echo “#! /bin/bash” > my_script ;
find / -not -type l -not -regex “/(sys|proc|dev|tmp|home)/.*” -printf “chmod %m .%pn” >> my_script ;
echo “# end” >> my_script ;
chmod 755 my_script

It’s important to exclude symbolic links because in fact their target is chmod-ed (which is probably not what we want).

You may opt not to exclude /tmp or /home (if you have no real users) but better keep yourself away from /dev, /proc and /sys. And they are dynamically populated anyway.

The dot before %p will be helpful if you can’t start your trashed system – and better don’t listen to me if I tell going to / and running anything from there .

You’ll get something like this, just several tens Klines long (in 17 secons one of my servers produced ~75000 lines in a 4 MB file, so the generation time is not a problem – however, execution will take longer…)

#! /bin/bash
…
chmod 755 ./bin/mknod
chmod 755 ./bin/mt-st
chmod 4755 ./bin/mount
chmod 4711 ./bin/ping6
chmod 755 ./bin/rmdir
chmod 755 ./bin/shred
…
# end

Well, the real problem will be execution on the trashed system. Most probably, you will not be able to start it – so, run some live CD distribution, mount the system root partition at some mount point, mount other partitions under the appropriate locations, cd to the mount point and run the transferred script.

Good luck,

Petko