Difference between revisions of "Beginners' Guide/Post-Installation"

From ArchWiki
Jump to: navigation, search
(rephrased the article summary)
(major overhaul. Merged a few sections, renamed the titles, simplified, rephrased... the section on package verification was deprecated)
Line 23: Line 23:
 
Your new Arch Linux base system is now a functional GNU/Linux environment ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes.
 
Your new Arch Linux base system is now a functional GNU/Linux environment ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes.
  
Login with the root account. We will configure pacman and update the system as root.
+
Go ahead and login with the root account, because we will configure pacman and update the system as root.
  
{{Note|Virtual consoles 1-6 are available. You may switch between them with {{Keypress|Alt+F1...F6}}}}
+
{{Note|Virtual consoles 1-6 are available. You may switch between them with {{Keypress|Alt+F1}},{{Keypress|Alt+F2}}, ... {{Keypress|Alt+F6}}.}}
  
=== Update ===
+
=== Familiarize yourself with the packaging system ===
  
==== Update, Sync, and Upgrade the system with pacman ====
+
==== Pacman ====
  
Now we will update the system using [[pacman]]. Pacman is the '''pac'''kage '''man'''ager of Arch Linux. It manages your entire package system and handles installation, removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, remote and local searches and much more. Pacman will now be used to download software packages from remote repositories and install them onto your system.
+
Pacman is the '''pac'''kage '''man'''ager of Arch Linux. It manages your entire package system and handles installation, removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, remote and local searches and much more. Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use it.
  
==== Get familiar with pacman ====
+
Read {{ic|man pacman}}, have a look at the [[pacman]] article, or check out the [[Pacman Rosetta]] article for a comparison to other popular package managers.
  
Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use it.
+
{{Tip|If you find the lines of text to be too long (e.g. using a widescreen) or going all the way across your screen (e.g. if you have more than one monitor), you can export the {{ic|$MANWIDTH}} environment variable:
 
+
$ man pacman
+
 
+
{{Tip|If you find the lines of text to be too long and going all the way across your screen, you can export the {{ic|$MANWIDTH}} environment variable:
+
 
  # export MANWIDTH<nowiki>=</nowiki>80
 
  # export MANWIDTH<nowiki>=</nowiki>80
 
}}
 
}}
  
For more information, have a look at the [[pacman]] wiki entry at your own leisure, or check out the [[pacman rosetta]] entry for a comparison to other popular package managers.
+
==== Repositories ====
 
+
==== /etc/pacman.conf ====
+
  
To make any changes to your repository selections or pacman options, edit {{ic|/etc/pacman.conf}}.
+
A [[Wikipedia:software repository|software repository]] is a storage location from which software packages may be retrieved and installed on a computer. Arch Linux [[Package Maintainer|package maintainers]] (developers and [[Trusted Users]]) maintain a number of official repositories containing software packages for essential and popular software, readily accessible via pacman.
  
Repositories are described below; enable all desired repositories by removing the # in front of the 'Include =' and '[repository]' lines.
+
For repository selections and pacman options, edit {{ic|pacman.conf}}:
  
 
{{Note|When choosing repos, be sure to uncomment both the {{ic|[''repo_name'']}} header lines, as well as the {{ic|Include}} lines. Failure to do so will result in the selected repository being omitted! This is a very common error.}}
 
{{Note|When choosing repos, be sure to uncomment both the {{ic|[''repo_name'']}} header lines, as well as the {{ic|Include}} lines. Failure to do so will result in the selected repository being omitted! This is a very common error.}}
  
===== Package Repositories =====
+
# nano /etc/pacman.conf
  
A [[Wikipedia:software repository|software repository]] is a storage location from which software packages may be retrieved and installed on a computer. Arch Linux [[Package Maintainer|package maintainers]] (developers and [[Trusted Users]]) maintain a number of official repositories containing software packages for essential and popular software, readily accessible via [[pacman]]. This article outlines those officially-supported repositories. See [[Official Repositories]] for more information including details about the purpose of each repository.
+
Most people will want to use {{ic|[core]}}, {{ic|[extra]}} and {{ic|[community]}}.
  
Most people will want to use [core], [extra] and [community]. If you want to run 32-bit applications on Arch x86_64, enable the [multilib] repository by adding the lines below to {{ic|/etc/pacman.conf}}:
+
If you want to run 32-bit applications on Arch x86_64, enable the {{ic|[multilib]}} repository, as well:
  
 
  [multilib]
 
  [multilib]
 
  Include = /etc/pacman.d/mirrorlist
 
  Include = /etc/pacman.d/mirrorlist
  
===== AUR =====
+
See [[Official Repositories]] for more information, including details about the purpose of each repository.
  
The '''[[Arch User Repository]]''' (AUR) holds the [community] and [unsupported] branches. Unlike the other branches, [unsupported] contains no binary packages and cannot (by design) be accessed directly by pacman. This branch is a collection of [[PKGBUILD]] bash scripts written by Arch users to build packages from source using the [[Arch Build System]]. Software in [unsupported] is generally not available in the other branches. When an [unsupported] package acquires enough popular votes, it may be moved to the [community] binary repository if one of the [[Trusted Users]] is willing to adopt and maintain it there.
+
For software unavailable directly through pacman, see [[Arch User Repository]].
 
+
{{Note|There are a number of pacman wrappers ('''[[AUR Helpers]]''') available that provide seamless access to the AUR.}}
+
  
 
==== Mirrors ====
 
==== Mirrors ====
  
Same Arch packages are stored on multiple servers across the world. Selected mirrors are listed in {{ic|/etc/pacman.d/mirrorlist}}, ordered by priority. Initially {{ic|/etc/pacman.d/mirrorlist}} contains list of all known mirrors, some of which should be enabled to proceed any further.
+
Mirrors are listed in {{ic|/etc/pacman.d/mirrorlist}}, ordered by priority.
  
{{Note|If your installation medium is old, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux with pacman (see {{Bug|22510}}). Therefore it is advised to obtain the latest mirror information as described below.}}
+
{{Note|If you're using an older installation medium, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux (see {{Bug|22510}}). Therefore it is advised to obtain the latest mirror information as described below.}}
  
===== Choosing up-to-date mirrors =====
+
* [https://archlinux.org/mirrors/status/ Arch Linux MirrorStatus] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.
  
[https://archlinux.org/mirrors/status/ Arch Linux MirrorStatus] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc. [https://archlinux.org/mirrorlist/ Mirrorlist Generator] uses this information to automatically rank mirrors close to your location by how up-to-date they are. Generated list can be simply inserted in {{Ic|/etc/pacman.d/mirrorlist}}. You obviously can uncomment other mirrors based on your own guesses (remove the {{ic|#}} in front of entry to uncomment it).
+
* [https://archlinux.org/mirrorlist/ Mirrorlist Generator] uses the above to automatically sort mirrors by various criteria. Please use HTTP mirrors. They are faster because of something called [[Wikipedia:HTTP_persistent_connection|keepalive]]. FTP is slower, because it sends out a signal each time pacman downloads a package, resulting in a brief pause. For other ways to generate a mirror list, see [[Mirrors#Sorting_mirrors|Sorting mirrors]] and [[Reflector]].
  
===== Using faster mirrors =====
+
Change them to your liking and force pacman to refresh all package lists even if they are considered to be up to date:
 
+
To get the fastest mirrors refer to [[Mirrors#Sorting mirrors]].
+
 
+
===== Refreshing mirror list =====
+
 
+
Force pacman to refresh all package lists with the new mirrorlist in place:
+
  
 
  # pacman -Syy
 
  # pacman -Syy
  
Passing two {{ic|--refresh}} or {{ic|-y}} flags forces pacman to refresh all package lists even if they are considered to be up to date. Issuing {{ic|pacman -Syy}} ''whenever a mirror is changed'', is good practice and will avoid possible headaches.
+
Use this ''whenever a mirror is changed''. This is considered to be good practice and will avoid possible headaches.
  
 
{{Note|1=Some issues have been reported in the [https://bbs.archlinux.org/ Arch Linux forums] regarding network problems that prevent pacman from updating/synchronizing repositories (see [https://bbs.archlinux.org/viewtopic.php?id=68944] and [https://bbs.archlinux.org/viewtopic.php?id=65728]). When installing Arch natively, these issues have been resolved by replacing the default pacman file downloader with an alternative (see [[Improve Pacman Performance]] for more details). When installing Arch as a guest OS in [[VirtualBox]], this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.}}
 
{{Note|1=Some issues have been reported in the [https://bbs.archlinux.org/ Arch Linux forums] regarding network problems that prevent pacman from updating/synchronizing repositories (see [https://bbs.archlinux.org/viewtopic.php?id=68944] and [https://bbs.archlinux.org/viewtopic.php?id=65728]). When installing Arch natively, these issues have been resolved by replacing the default pacman file downloader with an alternative (see [[Improve Pacman Performance]] for more details). When installing Arch as a guest OS in [[VirtualBox]], this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.}}
  
==== Initialize package verification ====
+
=== Update the system ===
 
+
{{Note|This step is not necessary with the latest Arch install media (dated 2012.08.04 or later).}}
+
 
+
To initialize the verification of signatures of the packages, you can [[http://www.archlinux.org/news/having-pacman-verify-packages/ follow the steps below]]. See [[Pacman-key]] for more information.
+
 
+
# pacman-key --init
+
 
+
To generate the master-key, [[Pacman-key#Initializing_the_keyring|entropy is needed]]. You should press random keys on your keyboard, move your mouse around, or switch to another console and run a disk-intensive command such as {{ic|ls -R /}}. After the pacman-key command completes, run the following command to setup the keys.
+
 
+
# pacman-key --populate archlinux
+
 
+
Take time to verify the [https://www.archlinux.org/master-keys/ Master Signing Keys] when prompted as these are used to co-sign (and therefore trust) all other packager's keys.
+
 
+
==== Update the System ====
+
  
 
{{Warning|1=System updates should be performed with care. It is very important to read and understand [https://bbs.archlinux.org/viewtopic.php?id=57205 this] before proceeding.}}
 
{{Warning|1=System updates should be performed with care. It is very important to read and understand [https://bbs.archlinux.org/viewtopic.php?id=57205 this] before proceeding.}}
Line 115: Line 87:
 
* [https://archlinux.org/pipermail/arch-announce/ Announce mailing list].
 
* [https://archlinux.org/pipermail/arch-announce/ Announce mailing list].
  
Sync, refresh, and upgrade your entire new system with:
+
Sync, refresh the package database, and upgrade your entire system with:
  
 
  # pacman -Syu
 
  # pacman -Syu
Line 123: Line 95:
 
  # pacman --sync --refresh --sysupgrade
 
  # pacman --sync --refresh --sysupgrade
  
Pacman will now download a fresh copy of the master package list from the server(s) defined in {{ic|/etc/pacman.conf}} and perform all available upgrades. You may be prompted to upgrade pacman itself at this point. If so, respond by entering yes, and then reissue the {{ic|pacman -Syu}} command when finished.
+
If you are prompted to upgrade pacman itself at this point, respond by pressing {{Keypress|Y}}, and then reissue the {{ic|pacman -Syu}} command when finished.
  
Reboot if a kernel upgrade has occurred.
+
Reboot if the {{Pkg|linux}} package (the Linux kernel) was updated.
  
 
{{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.}}
 
{{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.}}
  
Pacman output is saved in {{ic|/var/log/pacman.log}}.
+
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 {{ic|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 [[FAQ#Package Management|Package Management FAQ]] for answers to frequently asked questions regarding updating and managing your packages.
+
See the [[FAQ#Package Management|Package Management]] section of the [[FAQ]] for answers regarding updating and managing packages.
  
===== Ignoring Packages =====
+
==== Ignoring packages ====
  
After executing the command {{ic|pacman -Syu}}, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system. In this case, there are two options; indicate the package(s) to skip in the pacman command line using the {{ic|--ignore}} switch ({{ic|pacman -S --help}} for details) or permanently indicate the package(s) to skip in the {{ic|/etc/pacman.conf}} file in the {{ic|IgnorePkg}} array. For more information, please see the [[pacman]] wiki entry.
+
After executing the command {{ic|pacman -Syu}}, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system.
  
Please note that the power user is expected to keep the **whole** system up-to-date with {{ic|pacman -Syu}}, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of {{ic|IgnorePkg}} in {{ic|/etc/pacman.conf}} is therefore discouraged, and should only be used sparingly, if you know what you are doing. Use of {{ic|IgnorePkg}} is analogous to "voiding the warranty".
+
In this case, there are two options:
  
===== The Arch rolling release model =====
+
* Indicate the package(s) to skip in the pacman command line using the {{ic|--ignore}} switch:
  
Keep in mind that Arch is a '''rolling release''' distribution. This means the user is not required to reinstall or perform elaborate system rebuilds to upgrade to the newest version. Issuing {{ic|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. Remember to '''reboot''' if a kernel upgrade has occurred.
+
# pacman -Syu --ignore libass
  
=== Adding a User ===
+
* Permanently indicate the package(s) to skip in {{ic|pacman.conf}}:
 +
 
 +
{{hc|# nano /etc/pacman.conf|2=
 +
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
 +
IgnorePkg  = nvidia libass
 +
}}
 +
 
 +
Please note that the user is expected to keep the **whole** system up-to-date with {{ic|pacman -Syu}}, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of {{ic|IgnorePkg}} in {{ic|/etc/pacman.conf}} is therefore discouraged, and should only be used sparingly, if you know what you are doing. Use of {{ic|IgnorePkg}} is analogous to "voiding the warranty".
 +
 
 +
=== Add a user ===
  
 
{{Warning|Linux is a multi-user environment. You should not perform everyday tasks using the root account, it is very poor practice and extremely dangerous: the root account should be used for administrative tasks only.}}
 
{{Warning|Linux is a multi-user environment. You should not perform everyday tasks using the root account, it is very poor practice and extremely dangerous: the root account should be used for administrative tasks only.}}
Line 172: Line 153:
  
 
The list of ''Additional groups'' in the example is a typical choice for a desktop system, hence it is recommended especially for beginners:
 
The list of ''Additional groups'' in the example is a typical choice for a desktop system, hence it is recommended especially for beginners:
*'''audio''' - for tasks involving sound card and related software
 
*'''games''' - for write permission for games in the games group
 
*'''lp''' - for managing printing tasks
 
*'''optical''' - for managing tasks pertaining to the optical drive(s)
 
*'''power''' - for allowing interactions with power options (e.g. shutdown with power button)
 
*'''scanner''' - for using a scanner
 
*'''storage''' - for managing storage devices
 
*'''video''' - for video tasks and hardware acceleration
 
  
For additional information about listed and other groups see [[Groups#User groups]].
+
*'''audio''' - for tasks involving sound card and related software.
 +
*'''games''' - for write permission for games in the games group.
 +
*'''lp''' - for managing printing tasks.
 +
*'''optical''' - for managing tasks pertaining to the optical drive(s).
 +
*'''power''' - for allowing interactions with power options (e.g. shutdown with power button).
 +
*'''scanner''' - for using a scanner.
 +
*'''storage''' - for managing storage devices.
 +
*'''video''' - for video tasks and hardware acceleration.
 +
 
 +
For additional information about listed and other groups see [[Groups#User_groups|User groups]].
  
 
Now you will be presented with a preview of your new account, and the ability to cancel or continue operations: after pressing {{Keypress|Enter}} the account will be created, and you will be prompted to enter additional, optional information for the new user (e.g. the full name). After that, you will be asked to enter the password for your account.
 
Now you will be presented with a preview of your new account, and the ability to cancel or continue operations: after pressing {{Keypress|Enter}} the account will be created, and you will be prompted to enter additional, optional information for the new user (e.g. the full name). After that, you will be asked to enter the password for your account.

Revision as of 22:41, 8 September 2012

Tip: This is part of a multi-page article for The Beginners' Guide. Click here if you would rather read the guide in its entirety.

Template:Article summary start Template:Article summary text Template:Article summary end

Post-Installation

Congratulations, and welcome to your new Arch Linux system!

Your new Arch Linux base system is now a functional GNU/Linux environment ready for customization. From here, you may build this elegant set of tools into whatever you wish or require for your purposes.

Go ahead and login with the root account, because we will configure pacman and update the system as root.

Note: Virtual consoles 1-6 are available. You may switch between them with Template:Keypress,Template:Keypress, ... Template:Keypress.

Familiarize yourself with the packaging system

Pacman

Pacman is the package manager of Arch Linux. It manages your entire package system and handles installation, removal, package downgrade (through cache), custom compiled package handling, automatic dependency resolution, remote and local searches and much more. Pacman is the Arch user's best friend. It is highly recommended to study and learn how to use it.

Read man pacman, have a look at the pacman article, or check out the Pacman Rosetta article for a comparison to other popular package managers.

Tip: If you find the lines of text to be too long (e.g. using a widescreen) or going all the way across your screen (e.g. if you have more than one monitor), you can export the $MANWIDTH environment variable:
# export MANWIDTH=80

Repositories

A software repository is a storage location from which software packages may be retrieved and installed on a computer. Arch Linux package maintainers (developers and Trusted Users) maintain a number of official repositories containing software packages for essential and popular software, readily accessible via pacman.

For repository selections and pacman options, edit pacman.conf:

Note: When choosing repos, be sure to uncomment both the [repo_name] header lines, as well as the Include lines. Failure to do so will result in the selected repository being omitted! This is a very common error.
# nano /etc/pacman.conf

Most people will want to use [core], [extra] and [community].

If you want to run 32-bit applications on Arch x86_64, enable the [multilib] repository, as well:

[multilib]
Include = /etc/pacman.d/mirrorlist

See Official Repositories for more information, including details about the purpose of each repository.

For software unavailable directly through pacman, see Arch User Repository.

Mirrors

Mirrors are listed in /etc/pacman.d/mirrorlist, ordered by priority.

Note: If you're using an older installation medium, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux (see FS#22510). Therefore it is advised to obtain the latest mirror information as described below.
  • Arch Linux MirrorStatus reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.
  • Mirrorlist Generator uses the above to automatically sort mirrors by various criteria. Please use HTTP mirrors. They are faster because of something called keepalive. FTP is slower, because it sends out a signal each time pacman downloads a package, resulting in a brief pause. For other ways to generate a mirror list, see Sorting mirrors and Reflector.

Change them to your liking and force pacman to refresh all package lists even if they are considered to be up to date:

# pacman -Syy

Use this whenever a mirror is changed. This is considered to be good practice and will avoid possible headaches.

Note: Some issues have been reported in the Arch Linux forums regarding network problems that prevent pacman from updating/synchronizing repositories (see [1] and [2]). When installing Arch natively, these issues have been resolved by replacing the default pacman file downloader with an alternative (see Improve Pacman Performance for more details). When installing Arch as a guest OS in VirtualBox, this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.

Update the system

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

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:

  • Arch news. If you did not read this before an upgrade and you encounter an error, check the news before you post a question on the forum!
  • Announce mailing list.

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.

Reboot if the linux package (the Linux kernel) was updated.

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 the Package Management section of the FAQ for answers regarding updating and managing packages.

Ignoring packages

After executing the command pacman -Syu, the entire system will be updated. It is possible to prevent a package from being upgraded. A typical scenario would be a package for which an upgrade may prove problematic for the system.

In this case, there are two options:

  • Indicate the package(s) to skip in the pacman command line using the --ignore switch:
# pacman -Syu --ignore libass
  • Permanently indicate the package(s) to skip in pacman.conf:
# nano /etc/pacman.conf
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg   = nvidia libass

Please note that the user is expected to keep the **whole** system up-to-date with pacman -Syu, rather than selectively upgrading packages. You may diverge from this typical usage as you wish; just be warned that there is a greater chance that things will not work as intended and that it could break your system. The majority of complaints happen when selective upgrading, unusual compilation or improper software installation is performed. Use of IgnorePkg in /etc/pacman.conf is therefore discouraged, and should only be used sparingly, if you know what you are doing. Use of IgnorePkg is analogous to "voiding the warranty".

Add a user

Warning: Linux is a multi-user environment. You should not perform everyday tasks using the root account, it is very poor practice and extremely dangerous: the root account should be used for administrative tasks only.

Add a normal user account instead, using one of the two following methods, both creating the user archie as an example:

Interactive method

The adduser command will prompt for information interactively:

# adduser

Login name for new user []: archie
 
User ID ('UID') [ defaults to next available ]:
 
Initial group [ users ]:

Additional groups (comma separated) []: audio,games,lp,optical,power,scanner,storage,video

Home directory [ /home/archie ]:

Shell [ /bin/bash ]:

Expiry date (YYYY-MM-DD) []:

As shown in the example, you are advised to enter values only for the Login name and the Additional groups, and leave empty all the other fields.

The list of Additional groups in the example is a typical choice for a desktop system, hence it is recommended especially for beginners:

  • audio - for tasks involving sound card and related software.
  • games - for write permission for games in the games group.
  • lp - for managing printing tasks.
  • optical - for managing tasks pertaining to the optical drive(s).
  • power - for allowing interactions with power options (e.g. shutdown with power button).
  • scanner - for using a scanner.
  • storage - for managing storage devices.
  • video - for video tasks and hardware acceleration.

For additional information about listed and other groups see User groups.

Now you will be presented with a preview of your new account, and the ability to cancel or continue operations: after pressing Template:Keypress the account will be created, and you will be prompted to enter additional, optional information for the new user (e.g. the full name). After that, you will be asked to enter the password for your account.

Non-interactive method

# useradd -m -g users -G audio,games,lp,optical,power,scanner,storage,video -s /bin/bash archie

You will have to set a password using passwd. To enter additional information you can use the chfn command.

Deleting the user account

In the event of error, or if you wish to delete this user account in favor of a different name or for any other reason, use userdel:

# userdel -r [username]

The -r option will remove the user's home directory and its content, along with the the user's mail spool.

More information

Read Users and Groups for further information. If you want to change the name of your user or any existing user, consult the Change username page. You may also check the man pages for usermod(8) and gpasswd(8). Template:Beginners' Guide navigation