8 Mar
2011
8 Mar
'11
3:07 p.m.
On Tue, Mar 8, 2011 at 9:41 AM, Castro <castro(a)indigoblues.co.uk> wrote:
Darrell Anderson wrote:
It is actually slower, even if not by much. If you have a fast CPU
supporting virtualization and a lot of RAM, you can have it run close
enough to your real computer that you don't notice much of a
difference.
Provided you have a minimal set of processes running on both your real
hardware and your chroot, the chroot will be faster for building than
keeping minimal processes running on your real hardware and the VM.
The only advantage to a VM for building packages is to test them after
they've been built.
Needless to say, there are other uses for a VM outside building packages.
--
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager
Can newer releases of a distro be run in a chroot from within an older
release? What problems will occur?
I'm running Slackware 12.2, mostly because that was the last release
supporting KDE 3.5.10. I run my Trinity builds in a chroot.
I would like to start Trinity build testing for the most recent Slackware
release.
I can run newer releases in a virtual machine, but I find virtual machines
much slower than the chroot.
Thanks.
Darrell
When I boot my VM, I leave it sitting at console login
I then sftp into my VM using konqueror for file management and ssh with
konsole
for building etc.
It is much faster.
I then login and startx when I am ready to test. ;-)
castro (David Baylis)