However, this is not guaranteed to work. If that fails, you will need an alternative way to boot your system so you can access and repair it. One option is to use a special rescue image or a Linux live CD.
After booting from that, you should be able to mount your root file system and chroot into it to investigate and fix the problem. Another option we'd like to recommend is to use the rescue mode of the wheezy Debian Installer. The advantage of using the installer is that you can choose between its many installation methods to find one that best suits your situation. The initramfs-tools package includes a debug shell [3] in the initrds it generates. If for example the initrd is unable to mount your root file system, you will be dropped into this debug shell which has basic commands available to help trace the problem and possibly fix it.
If you do manage to fix the problem, typing exit will quit the debug shell and continue the boot process at the point it failed. Of course you will also need to fix the underlying problem and regenerate the initrd so the next boot won't fail again. The distribution upgrade should be done either locally from a textmode virtual console or a directly connected serial terminal , or remotely via an ssh link. If you are using some VPN services such as tinc they might not be available throughout the upgrade process.
Please see Section 4. In order to gain extra safety margin when upgrading remotely, we suggest that you run upgrade processes in the virtual console provided by the screen program, which enables safe reconnection and ensures the upgrade process is not interrupted even if the remote connection process fails.
You should not upgrade using telnet , rlogin , rsh , or from an X session managed by xdm , gdm or kdm etc. That is because each of those services may well be terminated during the upgrade, which can result in an inaccessible system that is only half-upgraded. Use of the GNOME application update-manager is strongly discouraged for upgrades to new releases, as this tool relies on the desktop session remaining active. For the greatest reliability of the upgrade process, you may wish to remove third-party packages from your system before you begin upgrading.
Direct upgrades from Debian releases older than 6. Please follow the instructions in the Release Notes for Debian 6. This procedure also assumes your system has been updated to the latest point release of squeeze. If you have not done this or are unsure, follow the instructions in Section A.
Because of this you should review if there are any pending actions in the package manager aptitude. If a package is scheduled for removal or update in the package manager, it might negatively impact the upgrade procedure. Note that correcting this is only possible if your sources. If it shows any actions, you should review them and either fix them or implement the suggested actions. If you have configured APT to install certain packages from a distribution other than stable e.
Regardless of the method used for upgrading, it is recommended that you check the status of all packages first, and verify that all packages are in an upgradable state. The following command will show any packages which have a status of Half-Installed or Failed-Config, and those with any error status. You could also inspect the state of all packages on your system using aptitude or with commands such as. It is desirable to remove any holds before upgrading.
If any package that is essential for the upgrade is on hold, the upgrade will fail. Note that aptitude uses a different method for registering packages that are on hold than apt-get and dselect.
You can identify packages on hold for aptitude with. If you want to check which packages you had on hold for apt-get , you should use. If you changed and recompiled a package locally, and didn't rename it or put an epoch in the version, you must put it on hold to prevent it from being upgraded.
If there is anything you need to fix, it is best to make sure your sources. This is a precaution to reduce the likelihood of conflicts. If you have any non-Debian packages on your system, you should be aware that these may be removed during the upgrade because of conflicting dependencies. Such packages are most likely to cause problems during an upgrade as they may result in file conflicts [4]. Section 4. A release can often be referred to both by its codename e.
Referring to a release by its codename has the advantage that you will never be surprised by a new release and for this reason is the approach taken here. It does of course mean that you will have to watch out for release announcements yourself. If you use the status name instead, you will just see loads of updates for packages available as soon as a release has happened.
When inspecting that mirror with a web browser or FTP program, you will notice that the main directories are organized like this:. To use this mirror with apt , you add this line to your sources. To use this with apt , add this line to your sources. Note that there must be no spaces between the words noauto,ro in the fourth field. The recommended way to upgrade from previous Debian releases is to use the package management tool apt-get.
In previous releases, aptitude was recommended for this purpose, but recent versions of apt-get provide equivalent functionality and also have shown to more consistently give the desired upgrade results.
There should not be any sources entries pointing to squeeze. Then if a problem occurs, you will have a log of what happened, and if needed, can provide exact information in a bug report. To start the recording, type:. If you have to rerun the typescript e. The typescript will also allow you to review information that has scrolled off-screen. After you have completed the upgrade, you can stop script by typing exit at the prompt. If you have used the -t switch for script you can use the scriptreplay program to replay the whole session:.
First the list of available packages for the new release needs to be fetched. This is done by executing:. You have to make sure before upgrading your system that you will have sufficient hard disk space when you start the full system upgrade described in Section 4. After the download, you will probably need more space in other file system partitions in order to both install upgraded packages which might contain bigger binaries or more data and new packages that will be pulled in for the upgrade.
If your system does not have sufficient space you might end up with an incomplete upgrade that is difficult to recover from. Before executing the upgrade, you can see this estimate by running:. Running this command at the beginning of the upgrade process may give an error, for the reasons described in the next sections.
In that case you will need to wait until you've done the minimal system upgrade as in Section 4. If you do not have enough space for the upgrade, apt-get will warn you with a message like this:. Cleaning up the package cache by running apt-get clean will remove all previously downloaded package files. Remove forgotten packages.
If you have used aptitude or apt-get to manually install packages in squeeze it will have kept track of those packages you manually installed, and will be able to mark as redundant those packages pulled in by dependencies alone which are no longer needed due to a package being removed. They will not mark for removal packages that you manually installed. To remove automatically installed packages that are no longer used, run:.
You can also use deborphan , debfoster , or cruft to find redundant packages. Do not blindly remove the packages these tools present, especially if you are using aggressive non-default options that are prone to false positives. It is highly recommended that you manually review the packages suggested for removal i. Remove packages that take up too much space and are not currently needed you can always reinstall them after the upgrade.
If you have popularity-contest installed, you can use popcon-largest-unused to list the packages you do not use that occupy the most space. You can find the packages that just take up the most disk space with dpigs available in the debian-goodies package or with wajig running wajig size. They can also be found with aptitude. This will give you a handy list to work with. Remove translations and localization files from the system if they are not needed. You can install the localepurge package and configure it so that only a few selected locales are kept in the system.
Do not use an NFS mount as the network connection could be interrupted during the upgrade. You can create the temporary cache directory on whatever filesystem is mounted on your system. Do a minimal upgrade of the system see Section 4. This will make it possible to upgrade the system partially, and allow you to clean the package cache before the full upgrade. Note that in order to safely remove packages, it is advisable to switch your sources. If your computer is currently running the configuration but does not have PAE, you will need to switch to the configuration instead.
You can check whether your computer has PAE by running:. If it does not i. In some cases, doing the full upgrade as described below directly might remove large numbers of packages that you will want to keep. We therefore recommend a two-part upgrade process: first a minimal upgrade to overcome these conflicts, then a full upgrade as described in Section 4. This has the effect of upgrading those packages which can be upgraded without requiring any other packages to be removed or installed.
The minimal system upgrade can also be useful when the system is tight on space and a full upgrade cannot be run due to space constraints. If the apt-listchanges package is installed, it will in its default configuration show important information about upgraded packages in a pager. Press q after reading to exit the pager and continue the upgrade.
Once you have taken the previous steps, you are now ready to continue with the main part of the upgrade. The upgrade process for some previous releases recommended the use of aptitude for the upgrade. This tool is not recommended for upgrades from squeeze to wheezy. This will perform a complete upgrade of the system, installing the newest available versions of all packages, and resolving all possible dependency changes between packages in different releases.
If you need a more recent version of the kernel you can get it from backports where it is at version 3. Squeeze is a old stable version. The new stable version, wheezy , is in " release candidate 1 " state, so an old kernel is normal in squeeze. I suggest upgrade to wheezy or activate "backports". Backports are new stuff ported to squeeze. Sign up to join this community.
The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Debian Squeeze Kernel Ask Question. Asked 8 years, 6 months ago. Active 8 years, 6 months ago.
Viewed times. Should I upgrade? Firmware files needed during installation may be loaded by the installation system; special CD images and tarballs for USB based installations are available too. More information about this may be found in the Debian Firmware wiki page. Furthermore, Debian 6. Various other changes make Debian more suitable for small form factor notebooks, like the introduction of the KDE Plasma Netbook shell.
With this broad selection of packages, Debian once again stays true to its goal of being the universal operating system. It is suitable for many different use cases: from desktop systems to netbooks; from development servers to cluster systems; and for database, web or storage servers. At the same time, additional quality assurance efforts like automatic installation and upgrade tests for all packages in Debian's archive ensure that Debian 6.
It is rock solid and rigorously tested. Starting from Debian 6. Their coverage has increased as Debian 6. The full content of all the blends can be browsed , including prospective packages that users are welcome to nominate for addition to the next release.
0コメント