I still don't see the problem, i.e. what you are trying to do.

27.03.2010 19:13 schrieb am "erik quanstrom" <quanstro@quanstro.net>:

> > how does history(1) work in the face of a complicated namespace?
> > we get buy now because the ...
in order for a namespace to be non-empty, it will need binds or mounts
somewhere.  even a "global" (i'm assuming by global you mean in
/lib/namespace)
bind will not work well with history.  since the namespace isn't fancy
enough
to do rewriting based on pattern matching.  (thank god!).

i suppose you could write a script, but such a script would need to generate
a set of binds for each day of the dump.  are you ready for a 350*(1 + 2136)
line namespace?

- erik