Comment 4 for bug 12815

If you don't want to make the problem go away by using the /emul/ method above
it could make sense to make the script aware of dchroot's config file. That is
the only way I know of for "registering" a chroot install somehow, so it's the
only predictable way to find them other than if they are all mounted in /emul/
(which is handled now, so this is perhaps just a documentation issue?)
Probing each one to try and find out what it is is the wrong behaviour imo, it
would imply that suitable architectures would be worth paying attention to in
some way. Ignoring them outright would certainly be quicker :)