I would suggest also use virtual machine for test propose as sandbox,
and you can always easy recover it from snapshots.
Nowadays limitation with hardware is not so critical especially for
linux/unix based OS not working with GUI.
Read about XEN also.
BR
16.12.2010 9:14, teddi...@tmo.blackberry.net wrote:
Ressell Gadd said
so I think I should start with
a clean system. At present I use Lenny (AMD64) with a couple of
backports (maybe they are part of the problem), although I do
multiboot several OS's and I can install another easily. So I think I
may install another OS just for this project (which will keep my day
to day system intact). I'd like to ask for suggestions as to what OS,
preferably some flavour of Debian, perhaps the current Squeeze?
Any other suggestions gratefully welcomed, particularly where to start reading.
----
One thing I may suggest is look into the use of virtual machines for something
like this. You can install and run the OS of your choosing in a window ontop of
your main system,
This has the advantages of sandboxing your experiments, having access to your
running and stable normal environment at the same time as experimenting, and
save hard disk space in unfilled partitions.
It also won't affect your stable installs should something go terribly wrong.
Your main disadvantage is your essentially running two OS's at the same time so
eats ram resources like crazy, and may not be an effective true test of system
intensive programs given the weight of all the extra stuff on the proc.
Oricle's Virtual Box is a good simple to use Virtulization software if your
interested.
Hope it helps;
TeddyB
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d09d0b4.6040...@utod.de
