On Fri, 21 Nov 2008 13:40:49 -0800, Darren New wrote:

> Jim Henderson wrote:
>> Yeah, and that sort of thing can happen - though the filesystem layer
>> (on top of the actual filesystem at the kernel level - not sure what
>> it's specifically called, probably some sort of abstraction layer)
>> deals in inodes rather than files.
> 
> I'm just saying that if you have (say) an executable and three related
> dynamically-linked .so files, or you have a .so and a .h file, there's
> no way in Linux to ensure that you can update them consistently, as far
> as I know. (I learn Linux tricks by telling people Linux can't do
> something, and then people correct me. ;-)

I'm not quite sure what you mean by "ensure that you can update them 
consistently" - since a file that's open can be overwritten or deleted 
because of the nature of that filesystem abstraction layer, why would you 
not be able to update it consistently?

Jim

Post a reply to this message