How I updated Linux Mint
My main OS at the moment is Linux Mint. Until recently, it was version 8, but in May 9-ka came out and wanted to upgrade. It would seem that Mint is after all a slightly doped ubunt, and the update here should also be the same with the notification of the new release. But in the mine, the automatic upgrade is removed, and the official website recommends updating through ... reinstalling the system from scratch.
Proflink: community.linuxmint.com/tutorial/view/2
The manual even describes in detail the creation of a backup using a special tool MintBackup, which will help you, after a fresh installation, then deploy the same set of software as it was before.
Honestly, it puzzled me. Demolish the system and roll a new one? What for? Over the years, Debian and Ubuntu have used a reliable update mechanism via apt-get, is it really not needed now?
In general, such a blatant injustice forced me to do everything in the old-fashioned way, having updated 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 references to 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 ceases to generate errors. Also, if in the system a number of packages were previously installed not from repositories, but manually, then it is likely that apt-get will stumble about file conflicts. For me, for example, this happened to flash-installer and fglrx, which I manually installed on top of the standard ubuntov packages. In short, inaccuracies in the packet system will surely come up with an error when updating the distribution.
In the end, I had to remove the conflict packages with the banal sudo dpkg -r --force-all <package_name>, since there were two such packages.
When everything is ready - sudo reboot. The system should offer when booting a new kernel 2.6.32.
If there is an error somewhere, the system does not boot to the end, the Xs hang, then you can do the recovery by booting 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 already small dopilki, usually it only in pleasure! :)
Proflink: community.linuxmint.com/tutorial/view/2
The manual even describes in detail the creation of a backup using a special tool MintBackup, which will help you, after a fresh installation, then deploy the same set of software as it was before.
Honestly, it puzzled me. Demolish the system and roll a new one? What for? Over the years, Debian and Ubuntu have used a reliable update mechanism via apt-get, is it really not needed now?
In general, such a blatant injustice forced me to do everything in the old-fashioned way, having updated 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 references to 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 ceases to generate errors. Also, if in the system a number of packages were previously installed not from repositories, but manually, then it is likely that apt-get will stumble about file conflicts. For me, for example, this happened to flash-installer and fglrx, which I manually installed on top of the standard ubuntov packages. In short, inaccuracies in the packet system will surely come up with an error when updating the distribution.
In the end, I had to remove the conflict packages with the banal sudo dpkg -r --force-all <package_name>, since there were two such packages.
When everything is ready - sudo reboot. The system should offer when booting a new kernel 2.6.32.
If there is an error somewhere, the system does not boot to the end, the Xs hang, then you can do the recovery by booting 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 already small dopilki, usually it only in pleasure! :)
')
Source: https://habr.com/ru/post/96887/
All Articles