![]() Your system should fail to reboot or, for remotely managed systems, fail to Known potential issues areĭocumented in this and the next chapters of these Release Notes.įor this reason it makes sense to ensure that you will be able to recover if There is always a chance that you may experience problems These critical services are running and available through the full upgradeĪlthough Debian tries to ensure that your system stays bootable at all times, Upgrade these packages prior to doing the full upgradeĭescribed in Section 4.4.5, “Upgrading the system”. You do a minimal system upgrade, as described in Section 4.4.4, “Minimal system upgrade”, followed by a kernel upgrade and reboot,Īnd then upgrade the packages associated with yourĬritical services. If the system being upgraded provides critical services for your users or the Possibility of services being unavailable for a significant period of time. The system requests input during the upgrade there is a high Notice that if the upgrade process is left unattended and Packages being upgraded in the system, and it also includes the time the systemĪdministrator spends answering any configuration questions from package The precise downtime for these services will vary depending on the number of During this time, these services will not be If this is the case, please note that,ĭuring the upgrade, these services will be stopped while their associated packagesĪre being replaced and configured. There might be services that are offered by the system which are associated with packages The upgrade has a few preconditions you should check them before actually You may also want to inform users about this.Īny package installation operation must be run with superuser privileges, soĮither log in as root or use su or sudo to This backup may help to restore or recreate the old settings. As a precaution, you may want to makeĪ backup of the hidden files and directories ( “ dotfiles”) in users' homeĭirectories. Overwrite existing user settings with new defaults when a new version of theĪpplication is first started by a user. Of the Mozilla suite, and the GNOME and KDE desktop environments) are known to The upgrade process itself does not modify anything in the Will also want to back up /var/lib/aptitude/pkgstates. You use aptitude to manage packages on your system, you var/lib/apt/extended_states and the output ofĭpkg -get-selections "*" (the quotes are important). The main things you'll want to back up are the contents of Hardware failure in the middle of an upgrade could result in a severely damaged The upgrade tools and process are quite reliable, but a Transitional dummy packagesĤ.1.1. Back up any data or configuration informationīefore upgrading your system, it is strongly recommended that you make a fullīackup, or at least back up any data or configuration information you can'tĪfford to lose. Upgrading your kernel and related packages 4.6.1. Dist-upgrade fails with “ Could not perform immediate configuration” 4.5.2. Make sure you have sufficient space for the upgrade 4.4.4. Adding APT sources from optical media 4.4. Adding APT sources for a local mirror 4.3.3. ![]() Verify network interface name support 4.2. Prepare a safe environment for the upgrade 4.1.6. Back up any data or configuration information 4.1.2.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |