NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Not all virualisation solutions are equal (Score:2)
I've been a heavy user of Linux vservers (see also: OpenVZ and the other one whose name I forget; and BSD 'jails') for a number of years. They are similar in concept to your chroot solution except much more convenient to use. They are lightweight because the virtual servers don't run their own kernels - they share the host kernel but with key structures like the process table partitioned into separate namespaces.
I've found this type of virtualisation to be invaluable in the 'staging' or 'User Acceptance Test' environment. If an application will be split across multiple servers in production (eg: DB server, app server, frontend web server), then you really want your staging environment to be configured the same way. Doing it with virtual servers is a cheap and effective solution.
Reply to This