> No. You're right for the current kernel. The original poster wanted to
> forbid *any* modification to the shared lib as long as it is open by
> modifying the kernel. As I understand this his request this includes
> renameing, unlink(2) etc. And then you can no longer change the libs.
Renaming a file doesn't change that file, only the directory it
is in. Unlinking a file doesn't change that file either, it only
disconnects it from the directory it's in, since the file is presumably
in use, nothing happens to the data in the file.
What I'm saying is that if a file is in use, that is, can be
paged in by an executing program, its data should not be modifyable,
"text file busy" should be returned. I'm not sure if that's true, or even
a good idea, but that was what I was talking about.
David Schwartz