How I Upgraded Linux Mint

Published on June 18, 2010

How I Upgraded Linux Mint

    My main OS at the moment is Linux Mint. Until recently, it was version 8, but in May 9 came out and wanted to upgrade. It would seem that Mint is a slightly dubbed ubunt after all, and the update here should also happen in the same way, with a notification of a new release. But in Mint, the automatic upgrade is removed, and the official website recommends updating through ... reinstalling the system from scratch.
    Pruflink: community.linuxmint.com/tutorial/view/2
    The manual even describes in detail how to create a backup using the special MintBackup tool, which will help you to deploy the same set of software after the fresh installation as it was before.
    Honestly, it puzzled me. Demolish the system and roll a new one? What for? Debian and Ubuntu have been using a reliable update mechanism through apt-get for years, so is it really no longer needed?

    In general, such a blatant injustice forced me to do everything the old fashioned way, updating the release on a “live” system.
    So, if you need to upgrade Linux Mint 8 Helena to Linux Mint 9 Isadora:
    1. sudo gedit /etc/apt/sources.list
    2. Change all mentions of helena to isadora, and karmic to lucid.
    3. sudo apt-get update
    4. sudo apt-get upgrade
    5. sudo apt-get dist-upgrade

    Here you need to make a reservation. Items 4 and 5 will have to go through several times and so on until dist-upgrade stops throwing errors. Also, if in the system a number of packages were previously installed not from the repositories, but manually, then it is likely that apt-get will stumble over file conflicts. For example, it happened to me with flash-installer and fglrx, which I installed manually on top of standard Ubunt packages. In short, inaccuracy in a batch system will certainly come out as an error when updating the distribution kit.
    As a result, I had to remove the packages that are trivial sudo dpkg -r --force-all <package_name>, there were two such packages.
    When everything is ready - sudo reboot. The system should offer a new kernel 2.6.32 at boot.
    If somewhere there is an error, the system does not load to the end, the X hangs, then you can start recovery by loading with the init = / bin / sh option. This is the path directly to the admin console, without entering a password, what is called "single-user mode."

    Further there are small dopilki, usually this is just a pleasure! :)