![]() See the #Read before upgrading the system section.Īvoid using the -d option with pacman. In a properly maintained system, it should only be used when explicitly recommended by the Arch developers. When used, pacman will bypass file conflict checks for files that match the glob. The -overwrite option takes an argument containing a glob. Generally avoid using the -overwrite option with pacman. ![]() In other words, never run pacman -Sy instead, always use pacman -Syu. Avoid certain pacman commandsĪvoid doing partial upgrades. Tip: You could use a pacman hook like informant AUR which prevents you from updating if there is fresh Arch News that you have not read since the last update ran. Instead, wait to upgrade until there is enough time available to resolve any post-upgrade issues. Users must equally be aware that upgrading packages can raise unexpected problems that could need immediate intervention therefore, it is discouraged to upgrade a stable system shortly before it is required for carrying out an important task. When updates require out-of-the-ordinary user intervention (more than what can be handled simply by following the instructions given by pacman), an appropriate news post will be made.īefore upgrading fundamental software (such as the kernel, xorg, systemd, or glibc) to a new version, look over the appropriate forum to see if there have been any reported problems. Users must be vigilant and take responsibility for maintaining their own system.īefore upgrading, users are expected to visit the Arch Linux home page to check the latest news, or alternatively subscribe to the RSS feed or the arch-announce mailing list. Pacman is a powerful package management tool, but it does not attempt to handle all corner cases. If the system has packages from the AUR, carefully upgrade all of them. Then, if no problems arise, roll out the changes to the production system. If you are running Arch in a production environment, or cannot afford downtime for any reason, test changes to configuration files, as well as updates to software packages, on a non-critical duplicate system first. Make sure to have the Arch install media or another Linux "live" CD/USB available so you can easily rescue your system if there is a problem after updating. When requesting support from the community, it will usually be assumed that the system is up to date. It is recommended to perform full system upgrades regularly via Pacman#Upgrading packages, to enjoy both the latest bug fixes and security updates, and also to avoid having to deal with too many package upgrades that require manual intervention at once. See Data-at-rest encryption#Backup for disk encryption scenarios. See pacman/Tips and tricks#Back up the pacman database. See Pacman tips#List of installed packages for details. Maintain a list of all installed packages so that if a complete re-installation is inevitable, it is easier to re-create the original environment. ![]() On a larger scale, consider using a configuration manager.įor dotfiles (configuration files in the home directory), see dotfiles#Tracking dotfiles directly with Git. Editors like vim and emacs can do this automatically. It is encouraged to automate backups, see Autostarting#On time events.īefore editing any configuration files, create a backup so that you can revert to a working version in case of problems. See Category:System recovery for other articles of interest. See Synchronization and backup programs for many alternative applications that may better suit your case. Having backups of important data is a necessary measure to take, since human and machine processing errors are very likely to generate corruption as time passes, and also the physical media where the data is stored is inevitably destined to fail. See Xorg#Troubleshooting for information on where and how Xorg logs errors. See systemd/Journal for more information and filtering options. Look for errors in the log files located in /var/log/, as well as messages logged in the systemd journal: See systemd#Using units for more information. Timely maintenance is a practice many users get accustomed to.Ĭheck if any systemd services have failed: Regular system maintenance is necessary for the proper functioning of Arch over a period of time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |