System maintenance

From ArchWiki
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Read the News

The Arch Linux News is posted here: [1] You can subscribe to the rss feed by adding: [2] to your favorite feed reading software. You can also get news by subscribing to the Arch Announce mailing list: [3]

Pay special attention to news items with "manual intervention required" in their header. You can avoid a lot of trouble and embarrassment by reading the instructions in these news announcements and following them.

Packages

When you update, check pacman output for instructions related to updated packages

pacman -Qo to see if something owns them

Search for .pac* files (how to use locate, and suggest tools like meld and vimdiff)

Check for out of date or unmaintained aur packages on your system (sometimes these can cause problems when you update)

Check the size of /var and clear pacman's cache once in a while. A usefull tool to assist in this process is Cacheclean.

Hardware

check disk (fstab options to check at boot)

search logs for errors (list scripts, tools to make this easier/more automated) look into errors when they come up, do not wait

Bad Practices

link random libraries together to get a program to work

update once a year

copy - pasting commands into the terminal without at least reading the man page to see what you are actually doing to your system