> It's not a bug, it's a feature!

I disagree and will fork a local grml-chroot.

> grml-chroot handles multiple joins to the same chroot just fine.

No.

> The first grml-chroot instance will mount and unmount, all other will not 
touch anything.

So it doesn't properly handle the case where the first chroot terminates before 
others. That's surprising behavior.

> It'd really prefer to not write to the chroot.

On grml, you can keep the state outside the chroot, for example in /var. my 
patch keeps the state inside the chroot since it keeps one from messing around 
with generating a directory name for the state of _this_ chroot.

Greetings
Marc