Brian McGroarty <[EMAIL PROTECTED]> writes: > So far as I can tell, there's no non-hackish way to accomplish what > I'd like. I have to either hold a file open to make chmod changes stay > in effect in /proc, or I have to patch the kernel. > > This sure seems kind of silly... why add all these things into Big > Giant Namespace and not honor all of the conventions of the same? I > think /proc/* not supporting chmod changes for the duration of a > system's uptime could be classified as a bug or a major design > flaw. :/
I guess it was just an oversight. Nobody needed it and nobody complained. But I did a patch against 2.5 to honor chmod and chown in procfs. Maybe you can adapt it to 2.4. The patch is available at: <http://groups.google.com/groups?selm=87zntm8cq8.fsf%40goat.bogus.local> Regards, Olaf.
