Use vcsh when provisioning virtual environments

[Brian May]

On 15 February 2012 21:30, Richard Hartmann
<richih.mailinglist at gmail.com> wrote:
> ... you shouldn't assume everyone knows all the tools you use ...

I thought this might have been the issue, not that I helped matters.

For the record, schroot is a much improved version of dchroot.
Everything knows what dchroot is, right :-)

More seriously, the description in the Debian package is far better
then what I could come up with myself:

=== cut ===
 Description-en: Execute commands in a chroot environment
 schroot allows users to execute commands or interactive shells in
 different chroots.  Any number of named chroots may be created, and
 access permissions given to each, including root access for normal
 users, on a per-user or per-group basis.  Additionally, schroot can
 switch to a different user in the chroot, using PAM for
 authentication and authorisation.  All operations are logged for
 security.
 .
 Several different types of chroot are supported, including normal
 directories in the filesystem, and also block devices.  Sessions,
 persistent chroots created on the fly from files (tar with optional
 compression and zip) and LVM snapshots are also supported.
 .
 schroot supports kernel personalities, allowing the programs run
 inside the chroot to have a different personality.  For example,
 running 32-bit chroots on 64-bit systems, or even running binaries
 from alternative operating systems such as SVR4 or Xenix.
 .
 schroot also integrates with sbuild, to allow building packages with
 all supported chroot types, including session-managed chroot types
 such as LVM snapshots.
 .
 schroot shares most of its options with dchroot, but offers vastly
 more functionality.
=== cut ===

Not mentioned here is the support for union filesystems, which is also
pretty cool.
-- 
Brian May <brian at microcomaustralia.com.au>