The beauty of a hundreds of thousands of GNU/Linux Distributions is that they provide endless options to end-users as well as developers and, or packagers. All you need to have is an appetite to learn, a patience to try, a curiosity to explore and a creativity to deploy un-imaginable possibilities.
You might be wandering what triggered me to write all this, when hundreds of other people are bashing the creepers, creators and, or all those inharmonious beaters of drums?
Well, I wanted to give the KDE 4.1 desktop a try without rebooting off of a LiveCD, installing a complete distro and, or compiling the sources locally on my live Debian rig. By searching a bit, I found that the ArchLinux is always ahead in making available latest stable builds and, or binaries for most of the popular software; so I downloaded the archlinux-2008.06-core-i686.iso and booted off of the image itself with QEMU, addtionally giving it a free partition say /dev/sda5 as a drive and installed the core and KDE 4.1 desktop including all dependencies in single shot. I did all this in kind of a virtual environment, but we know almost all the virtual environments and, or machines have some overheads which make the system somewhat slow.
To overcame and, or avoid all that overhead, I exited the QEMU and mounted the partition where I recently installed ArchLinux and KDE 4.1, mounted few parts from my existing /dev and chrooted in to that new partition from console:
mount -t ext3 /dev/sda5 /mnt/sda5 mount --bind /dev /mnt/sda5/dev mount --bind /dev/pts /mnt/sda5/dev/pts mount --bind /dev/shm /mnt/sda5/dev/shm mount --bind /home /mnt/sda5/home mount --bind /proc /mnt/sda5/proc mount --bind /sys /mnt/sda5/sys invoke-rc.d kdm stop chroot /mnt/sda5 /etc/rc.d/esd start chroot /mnt/sda5 /etc/rc.d/kdm start
Viola! Me, as expected was greeted and, or welcomed to login in to that KDE 4.1 desktop.
Although I needed to tweak around a few user and, or group id’s in the /etc/passwd and /etc/group and relevant shadow files in this ArchLinux partition, might be tedious job for newbies, but the things are working smoothly ever since with a zero or no downtime.
The experts might have guessed that we need to reverse execute all the above steps to come out from this chrooted environment or we may automate all these steps with the help of an init script.