this also gave me an opportunity to do some clean installs and reorganize my disks.
for a long time i've wanted to try other distros. doing that in a virtual machine is kind of ok (with the added benefit that you always have something that works and a web browser at hand to look on the net for answers), but you never get 100% of what the machine can give. it's also the problem that, if you discover that you like more the distro from your VM, than you have to reinstall it again on the hard-drive to use it directly.
after a lot of thinking i've decided to try multibooting.
this is nice, as i always have something that work just a reboot away, but, at least the solution i came with, not without its share of problems. overall, i find it quite acceptable.
for me, these were the main challenges of multiboot:
- maintain the list of boot-able OS's up-do-date
- make sure that when installing a new os i don't destroy the booting capability of the existing ones (or i have at least some way to recover that booting capability later)
- maintain the content of /boot for each linux distro
at the present i have these OS's installed:
i might also try, at some point, sabayon 7 or ubuntu 11.10.
the hardware for my main box is:
- motherboard: Gigabyte Z68X-UD3H-B3
- cpu: i5 2500K
- ram: 2x4 GB DDR3 1333
- hdd: seagate 1TB
the only driver problem so far was with the network driver from fedora 15 (and archlinux core CD): the driver was a bit finicky and the connection dropped a lot. the best solution was to download the driver sources from realtek support page, compile the driver and install it
in the next couple of days i'll try to post more info on how i've configured the system.
let me know if this is useful to you.