Arch terminology

From ArchWiki
Revision as of 09:28, 14 April 2006 by Codemac (Talk | contribs) (makepkg)

Jump to: navigation, search

Arch Terminology/Jargon for newbies

This page is intended to be a page to demystify common terms used among the Arch Linux community. Feel free to add or modify any terms, but please use that particular section's edit option. If you decide to add one, please put it in alphabetical order.

ABS

The Arch Build System (ABS for short) is useful to

  • Make new packages of software for which no packages are yet available
  • Customize/Modify existing packages to fit your needs (enabling or disabling options)
  • Re-build your entire system using your compiler flags, "a la gentoo" (And getting kernel modules working with your custom kernel!)

ABS is not necessary to use Arch Linux, but it is useful.

For more information see the ABS wiki

AUR

PKGBUILD

TU

Trusted User. This is someone who the other TU's have voted into place to manage the AUR and the [community] repository.

Trusted Users have the ability to mark a package as safe on the AUR, and if it has been voted as popular, move it into the [community] repository.

Trusted users follow the [AUR Trusted User Guidelines] and TU by-laws

TUR

community/[community]

current/[current]

custom/user repository

developer

devfs

/etc/network-profiles

/etc/rc.conf

/etc/rc.d

/etc/rc.local

extra/[extra]

hotplug

hwd

hwdetect

initramfs

initrd

makepkg

makepkg is the application that ArchLinux uses to build packages for use with pacman. makepkg will read the install instructions in a PKGBUILD file, and execute them.

package

pacman

pacman.conf

release/[release]

rtfm

Read The Fucking Manual. This is simple message is replied to a lot of new linux/arch users who ask about the functionality of a program, when it is clearly defined in
man program

It is often used when a user fails to make any attempt to find a solution to the problem themselves. If someone tells you this, they are not trying to offend you, they are just frustrated with your lack of effort.

The best thing to do if you are told to do this, is to do as above, and read the manual page:

  • Read the program man page, at a command line
man program-name
  • Search the wiki
  • Search the forum
  • Search Google

testing/[testing]

udev

unstable/[unstable]

wiki