> Sorry for bothering the list once again with my humble suggestion but coming
> back to ClearCase: why not implement the concept of a view:
> 1. You specify a set of rules which say which file is seen if there is a
> 2. In the case discussed here you also specify where to write.
> On mount these are read by a daemon and the kernel shovels all file I/O to this
> daemon into user-space. The daemon goes through 1 and 2 and does the actual
> file I/O.
Sounds like podfuk to me
:-). http://atrey.karlin.mff.cuni.cz/~pavel/podfuk/podfuk.html. Oh,
you'll have to specify your rules in C.
Podfuk might be really usefull for testing if semantics you propose is
reasonable, before putting it into kernelspace.
-- I'm really firstname.lastname@example.org. Look at http://126.96.36.199/~pavel. Pavel Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/