* Prof J C Nash <nashjc [ at ] uottawa [ dot ] ca> [061020 09:05]: > Possibly I have misunderstood the debootstrap and that it is running the > same kernel and different libraries and apps only. I thought it was > running a whole VM. I set it up in a roaring hurry to get a mission > critical tool working in time for 1400 students to use "yesterday". I did a virtualization talk a while back, should you be interested: http://www.jukie.net/~bart/slides/vservers-on-debian/vservers-on-debian.pdf Here is the summary: debootstrap can be used for real VMs (xen, qemu, VMware) as well as chroots. It can also be used by vservers -- which lie somewhere in between chroots and VMs. xen, qemu and VMware will execute a second kernel. Other then memory, CPU and peripheral restrictions, each system looks and feels like a new machine. vservers use the same kernel for all domains, but isolate file system, policy, and networking APIs for each. Each domain has an illusion of having it's own network stack. Finally, chroots hide the filesystem operations only. You share PIDs, the network stack, the scheduler and many other things. The only thing that chroots protect is access to the full file system tree from within the chroot. > I needed to run an "old" Apache, php and mysql because of some changes > in php since codes were written about 4 years ago. So I've got "woody" > running under debootstrap, and have switched off Apache in the outer > machine, but want sshd to run in both, which I now have going. Sounds like it was a critical component and you shouldn't muck with it :) -Bart -- WebSig: http://www.jukie.net/~bart/sig/
Attachment:
signature.asc
Description: Digital signature