when it comes to upgrading to a new release, some say sure why not give it a try, it worked for me, afterall you do have backups of everything that matters to you, right? but then many say don't waste your time, too often it just doesn't work, or you end up with a mess. so the best advice seems to be you should plan on doing a fresh install, even if you do spend the time trying the upgrade path. and your fresh install can be any release, not just the next one in sequence. of course the fresh install(er)s are riddled with bugs too. often i've had one trouble with the desktop installer (eg an unfounded insistence on resizing my partition, and i don't want to go there), and another problem with netboot (eg no sound when done), but finally success via the alternate installer (especially after learning how to boot the alternate iso via grub loopback, an apparently little known trick, requiring manual replacement of /dev/sr0 with a softlink to the iso, but not until the first failure to find the cdrom). so i join the chorus that recommends a fresh install. but i say a couple highly helpful verses are surprisingly rarely sung. for one, the alternate iso grub loopback trick. and the other, repartition if necessary, the installers are good at resizing partitions if needed, so you can install into a fresh partition, without losing your existing install. because heck, all too often something about the new install will be a disappointment, and then you can still run your old install. and if you do end up running your old install, you'll either want to reclaim the mbr with grub-install, or have the new grub find and use the configfile for the old install, else you will end up not seeing updated kernels. seems to me to be a big blindspot on the part of grub that it doesn't do this, ought to be the default behaviour, but it's not even offered as an option. sure you can insert it manually into 40_custom, where it will survive updates. but you'll still end up editing that new grub.conf if you want to supercede the default choice. you may also want to force the menu timeout, which won't reset itself when the OS it favors isn't booted. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20140226/7258b778/attachment.html>