Difference between revisions of "System maintenance"

From ArchWiki
Jump to: navigation, search
(Add zh_CN page.)
(use https for links to archlinux.org)
Line 5: Line 5:
 
Often, the developers will provide important information about required configurations and modifications for known issues. The Arch Linux user is expected to consult these places before performing an upgrade.
 
Often, the developers will provide important information about required configurations and modifications for known issues. The Arch Linux user is expected to consult these places before performing an upgrade.
  
The Arch Linux News is posted here: [http://www.archlinux.org/news] You can subscribe to the rss feed by adding: [http://www.archlinux.org/feeds/news] to your favorite feed reading software. You can also get news by subscribing to the Arch Announce mailing list: [http://mailman.archlinux.org/mailman/listinfo/arch-announce].
+
The Arch Linux News is posted here: [https://www.archlinux.org/news] You can subscribe to the rss feed by adding: [https://www.archlinux.org/feeds/news] to your favorite feed reading software. You can also get news by subscribing to the Arch Announce mailing list: [https://mailman.archlinux.org/mailman/listinfo/arch-announce].
  
 
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.  
 
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.  

Revision as of 00:08, 6 December 2012

Read the News

Often, the developers will provide important information about required configurations and modifications for known issues. The Arch Linux user is expected to consult these places before performing an upgrade.

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.

Update the system

Warning: System updates should be performed with care. It is very important to read and understand this before proceeding.

Sync, refresh the package database, and upgrade your entire system with:

# pacman -Syu

Or, same thing:

# pacman --sync --refresh --sysupgrade

If you are prompted to upgrade pacman itself at this point, respond by pressing Template:Keypress, and then reissue the pacman -Syu command when finished.

Note: Occasionally, configuration changes may take place requiring user action during an update; read pacman's output for any pertinent information. See Pacnew and Pacsave Files for more details.

Keep in mind that Arch is a rolling release distribution. This means the user doesn't have to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Issuing pacman -Syu periodically (and noting the above warning) keeps the entire system up-to-date and on the bleeding edge. At the end of this upgrade, the system will be completely current.

See Pacman and FAQ#Package Management for answers regarding updating and managing packages.

Packages

  • When you update, check pacman output for instructions related to updated packages.
  • Use pacman -Qdt to find orphaned packages, and pacman -Qo <file> to find out which package owns that particular file.
  • 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 useful tool to assist in this process is cachecleanAUR.

Hardware

  • Check disk (use fstab options to check at boot)
  • Search logs for errors (list scripts, tools to make this easier/more automated)
  • Look into errors as soon as possible - do not leave them unattended to.

Bad Practices

  • Linking random libraries together to get a program to work.
  • Updating once a year.
  • Copy-pasting commands into the terminal without at least reading man pages to understand what you are doing to your system.
  • Clearing the entire package cache using pacman -Scc - this removes the possibility to do package downgrades in cases of breakage.

See also