View source for *Mview chroot management

chroot is currently supported by *Mview (svn 397)

There are two different chroot supported by *Mview:
* chroot of a ''real'' directory (not managed by any of the loaded modules) cause the kernel chroot to be invoked.
If the call succeeds (the user permissions to run chroot) *Mview takes into account the new root to provide modules with the correct global paths.
* chroot of a ''virtual'' directory. No special permissions needed. *Mview properly transforms the virtual pathnames.

chroot does not affect open files or the current working directory.

There is a problem related to the getcwd call:
All the cwd pathnames referring to the chroot-ed subtree are relative to the new root, all the remaining paths are absolute. This behavior although strange is the same used by the Linux Kernel.