>>> This one could be solved by deleting the file on disk when the
>>> filesystem is made read-only, I think.
>> That will "solve" the "problem" of the file remaining.  It will not,
>> however, preserve the long--standing Unix semantics of continuing to
>> use open-but-unlinked files.
> The transition to RO should not be allowed as long as processes have
> files open for write, linked or unlinked.

Well, my comments were independent of whether the file is open for
write or not.  But, that aside, I'm not entirely sure I agree; I think
there should be a way to force it to RO, with writes after that
producing errors - somewhat akin to the way umount has an option to
forcibly unmount filesystems that are in use.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B