Maybe it is a real problem for you, but you are certainly using the
wrong fix. As others have pointed out, if you want to chown only
files owned by certain users, PLEASE DO SO! OK, so find(1) has this
uid option. You say you don't know the users in advance. Maybe
find <dir> ! -uid 0 |xargs chown
will help then. Maybe you have more complex criteria to chown the
files, like a list of people who are allowed to get their files chowned?
Well, write a small Perl/Python/bash script that does the job you want
to do.
You say you need a solution now. So changing kernel code was more easy
than writing a simple perl script? Come on...
> 2EE&VS: молчать! плиз!
That's what I was going to say. Can we *please* stop this?
Thanks,
Martin