#Linux clean disk install
#Linux clean disk manual

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.

#Linux clean disk install

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.

#Linux clean disk manual

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. Look for errors in the log files located at /var/log, as well as high priority errors in the systemd journal: Reason: Not all important error messages will be priority 3 (Discuss in Talk:System maintenance)