By employing undefined*, you added both . / and . . /. Together with the -R alternative, your chown phone was going to navigate your whole filesystem (and other people ( maybe mounted), heading through . . /. Together with different controls, this tiny error can be very fatal, but believe me, you are not the first, and you won’t be the final…
As this operation is rather hefty, your chown call recovered some time, since it had a whole lot of documents to process. I would recommend you return to the directory in which you left the phone, and return to / / to understand what alterations were made. You might Have the Ability to apply a Fast fix :
Chown root:root /* # Set ownership to root for many directories .
Chown you:yourgroup / / home/you -R # Require your house back.
On Ubuntu, the /house directory is provided to the very first (admin/sudo) user enrolled within the system. If you are the sole user, You May Want to do:
Chown you:yourgroup /house -R
But a very simple chmod 755 on /house is sufficient, even though it goes to root.
Using a quick glance right at / (like the origin permissions themselves, ls -ld /) are also a wonderful place to get started. I advise you be certain / belongs to origin, using a 755 permissions set.
If you utilized chown to establish a very particular ownership (a person other than root or you, a rare set,…), then you might choose to utilize locate to search for chown-ed files.
find / -user undefined
find / -group undefined
Regrettably, there’s absolutely no such thing as reverse for exactly what your own did. Linux does not naturally maintain tracks of those”casual” operations