A few months ago, I did a comparison test between 5 KDE distributions that aim to be friendly to newbies. These distributions were PC-BSD 8.1 "Hubble" (which is technically a distribution of BSD, not Linux), PCLinuxOS 2010.07 KDE, openSUSE 11.3 KDE, Sabayon 5.3 KDE, and Pardus 2009.2 "Geronticus Eremita" (live CD). (I also tested Chakra Alpha 5 "Panora", but that wasn't compared to the others due to its pre-release nature.) I did all these tests on my old Sony VAIO desktop. I intended to make live USBs out of all of these using UnetBootin, but only Sabayon and (surprisingly, given its origin and its developers' previous statements about using UnetBootin in this particular case) PCLinuxOS cooperated. The others required that I make a live USB using the "dd" command, which wipes all existing data off the flash drive and writes the ISO file onto the USB with a primitive filesystem type that can't coexist with other partitions. This didn't look good for me, because I didn't want to keep erasing and rewriting data on the flash drive. Thus, I tested all these distributions in VirtualBox. The downsides to this were that as my old computer only had 1 GB of RAM, I could only allocate 448 MB of RAM to the guest OSs, which in some cases was clearly too little, and that I couldn't in some cases properly test things like hardware detection and installation of programs in this limited virtual environment.
Then, a couple weeks ago, I found a program called MultiSystem, which I wrote about promptly. This program allows writing a live multiboot setup to a USB drive partition without destroying other partitions. Plus, it supports distributions like Mandriva (which I tested shortly after the original comparison), openSUSE, and Pardus which otherwise require the "dd" command. (Unfortunately, it doesn't support either PC-BSD or Chakra, the latter of which is surprising in its omission considering that distributions like Arch, ArchBang, and CTKArchLive are all supported.) Clearly, this was what I needed. Now I could go back and test Mandriva, openSUSE, and Pardus as live USB systems with direct access to all my computer's hardware without issue. And that's exactly what I've done and that's the subject of today's post.
Please note that I'm not including any screenshots with this post because the relevant screenshots have already been put up in the previous comparison. Next, I'm not actually comparing these distributions to one another, as that's already been done — I'm just seeing if each one on its own will cooperate with my computer's hardware. Also, I realize that because I'm testing these on a much better computer than before (and I'm using Mandriva 2010.2 instead of version 2010.1 that was previously tested), the methodologies may turn out different results than before. With all that in mind, follow the jump to see how each one fares.
Read more »
Then, a couple weeks ago, I found a program called MultiSystem, which I wrote about promptly. This program allows writing a live multiboot setup to a USB drive partition without destroying other partitions. Plus, it supports distributions like Mandriva (which I tested shortly after the original comparison), openSUSE, and Pardus which otherwise require the "dd" command. (Unfortunately, it doesn't support either PC-BSD or Chakra, the latter of which is surprising in its omission considering that distributions like Arch, ArchBang, and CTKArchLive are all supported.) Clearly, this was what I needed. Now I could go back and test Mandriva, openSUSE, and Pardus as live USB systems with direct access to all my computer's hardware without issue. And that's exactly what I've done and that's the subject of today's post.
Please note that I'm not including any screenshots with this post because the relevant screenshots have already been put up in the previous comparison. Next, I'm not actually comparing these distributions to one another, as that's already been done — I'm just seeing if each one on its own will cooperate with my computer's hardware. Also, I realize that because I'm testing these on a much better computer than before (and I'm using Mandriva 2010.2 instead of version 2010.1 that was previously tested), the methodologies may turn out different results than before. With all that in mind, follow the jump to see how each one fares.
0 comments:
Post a Comment