I agree with the advice to put Linux on its own machine, but not for any difficulty with configuring dual boot systems. Actually, it's not that hard to put a reasonably accesible dual boot system together. The problem arises from the fact that you can't be in both environments at the same time (without something like vmware, but let's not go there). On a dual boot environment, you choose which OS to boot, and the other remains unavailable to you unless you reboot. As a result, you learn less, because you can not readily turn from one OS to the other for a simple (or more complex) task. Rather, you have to close out whatever you have open, taking care to save open files, shutdown, wait for the new system to boot, then open another application, etc., etc., etc. Now, who will do such a thing just to check out some new trick you've just heard about for the grep command? Or to test a suggested configuration setting for mutt or lynx? Or to learn something cool with sed or awk? No, you won't reboot for such things. You'll wait until you have nothing better to do--and that day rarely comes. _______________________________________________ Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list