RPN01 wrote:
The downside of this in a virtual environment is that you are repeatedly implementing the same operating system code in memory for each unique image, when in fact, this code could have been shared by several individual applications, were they to share a single Linux image. It would be more efficient to place several applications within a single Linux image, within reason, to exploit the shared copy of the operating system.
Not a complete answer to this problem, but http://linux-vserver.org allows you to run what seem to users/applications/etc as their own box, without duplicating the kernel, the /usr file system, etc., as long as they all want the same kernel version. They even can each have their own IP address/NIC, and their own process 1 they can kill if they want. The Server people liken it to a super chroot environment. I wish I had the time to try it out... It does require a kernel modification. -- Carnegie Institution for Science <http://www.ciw.edu/> Department of Plant Biology <http://www-ciwdpb.stanford.edu/> The Arabidopsis Information Resource <http://www.arabidopsis.org/> Larry Ploetz Systems Administrator Carnegie Institution of Washington Department of Plant Biology The Arabidopsis Information Resource 650 325 1521 x 296 [EMAIL PROTECTED] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
