Hi all,
I did a seriously stupid thing... and completely screwed my fedora... To think it was just a mere typing error... I am still laughing even though I did it two days ago...
So, I needed to copy some files (with root privileges) to my home and change owner to myself... but I hurried too much and made the mistake... luckily I discovered it as soon as I hit enter - file and directories in /proc complained that chown cannot be applied... So I reread what I typed and get horrified...
So still more or less conscious I did chown root:root /*/*... well... that was good idea, but not that good - it screwed my gnome nearly to unusability... not rights anywhere... not folders in my home... so I fixed owners in /home and logged out... and... gdm didn't came up... instead it fall back to xdm... so I tried to log in.... unsuccessfully...complained of not enough rights in /tmp... so I logged as root in CLi and deleted whole content of /tmp... well... at least I was able to log in... but still through xdm...
So I rebooted to see if things change to better... They changed... GDM loaded successfully and I was able to log in... however when I turned gnome terminal and wanted su - it complained of incorrect password... even for users without password
So I realized, that I probably screwed more than I though... Then I remembered that if I force re-installation of rpms that has to do something with the screwed files rights will be repaired... So I went to rpm.pbone.net and typed su to the find query... Amongst many packages there were filesystem a coreutils...
So I yum-downloaded them and rpm -Uhv --forced them... And su started to work... But then I when I closed the laptop lid to go away and when I returned I wasn't able to relog... Screensaver complained of wrong password... Grr... so I run yum update (to fix things that might be in updates and I was not aware yet that I screwed them) and then yum-downloaded and rpm -Uhv --forced gnome-screensaver since it wasn't in updates... Well... that fixed the screensaver issue...
Now, the last thing, that apparently didn't work was ftp... Since I share files on anonymous account and my own user, I created /home/ftp and set it as home for anonymous ftp user and from my home made symbolic links there... but forgot which was the owner and when I repaired the mess I set it to ftp:users... well that was not good idea... But at last I came to conclusion why vsftpd complains of root write privilegies and set the owner to me... That fixed. It. Yupee....
So far this is the last thing that I know was broken... Seem I was able to repair it without reinstall.... cool... Next time I will check twice before pressing enter with root privileges...
And my question is... Do you have similar experience?
I did chown mso:mso /*/*
Linear Mode
