A basic system configuration has been made during installation.

However you will need to re-configure it to add or remove users, add a printer or a new service, change the user's language for instance. This article states how-to perform some configuration tasks for a desktop or laptop with the tools included in Slint.

Slint includes two kinds of configuration tools:

• Tools intended for and included in a specific desktop, gathered in a control center
• Generic tools usable in all window managers and desktops

To access the configuration tools intended for a specific desktop:

• From Xfce, in the Applications menu click on Settings then Settings Manager.
• From KDE, click on the K menu in the bottom left corner of the screen then on System Settings.

We will let you discover these specific tools and now present the generic ones.

Many generic tools include two user interfaces:

• A terminal user interface or TUI : you type a command in a terminal to use it.
• A graphical user interface or GUI: you click on an icon to use it.

In console mode, you can only use the TUI: just type the command, after having become root if need be (see below). You can also use the TUI in graphical mode: first click on a Terminal icon or choose a terminal in an application menu to start a terminal emulator.

Most of the icons that allow to start configuration tools are gathered in the Slint Control Center. They are listed at the end of Slint kick start.

Most of the tools used for configuration tasks need administrative privilege in other words to be used as root (super user). To do that:

• In a terminal or console (TUI) type su then root's password before typing the command.
• In a GUI: Type root's password if asked in the window that pops up when you click the relevant icon, or start a terminal emulator and, after having become root if need be, type the name of the GUI version of the tool.

Two commands are provided to manage users and groups:

• The usersetup command (TUI)
• The gtkusersetup command (GUI), with an icon in the Slint Control Center, System category)

These commands allow you to add or delete users and groups of users, and add users to groups.

Bear in mind that each user account is associated by default to its on space in the /home directory. For instance if you add a user leonie, a /home/leonie folder will be created, to which only this user (and root) will be allowed to access.

Two commands are provided for that:

• The localesetup command (TUI).
• The gtklocalesetup command (GUI), with an icon in the Slint Control Center, Settings category.

Bear in mind that this settings changes the language used by the applications' interfaces if they are internationalized, not the keyboard map (see below).

Also, localized packages (if available) matching the language chosen have been already installed at end of Slint installation. If you change the default language afterwards, you will need to install the corresponding localized packages if you want.

Localized means “provided in a given locale”, the locale being a language plus peculiarities associated to a geographic area. For instance Portuguese spoken in Portugal and Brazil differ. In the localized packages names, l10n is an abbreviation of “localization” meaning “letter l, 10 other letters, letter n”.

Localized packages are included for many languages. Their name include the base package name, a hyphen, then the language code. We list below the base names of the localized packages:

To find a localized package, type in a terminal emulator as root (example for kde-l10n):

spi libreoffice

This will display the list of all localized LibreOffice package. Find the one you want and install it. For instance for Persian the language code is fa (short for Farsi), so to install it type:

spi -i libreoffice-l0n-fa

If you prefer you can use gslapt. then, type the package name in the search field to display all localized libreoffice packages.

You can change the default keymap used in graphical mode using:

• The keyboardsetup command (TUI)
• The gtkkeyboardsetup command (GUI), with an icon in the Slint Control Center, Hardware category.

These commands also allow you to choose if numlock should be enabled when the system is started, and if the SCIM (input method) shuold be enabled at system startup.

If you use a window manager with a panel, you can also make this setting through a right click on the keyboard applet (displayed by default as the two letters language code of the keyboard map in use). KDE and Xfce have specific tools for that.

In Slint the CUPS print server manages printers and printing tasks. In its default configuration, recorded in the file /etc/cups/cupsd.conf, only users belonging to the sys (short for system) group are allowed to perform administrative tasks, like adding or removing a printer.

For a simple setup (printer attached to a desktop or laptop and not shared between machines), you just need to add one user (who will manage the printers) to the sys group. For instance adding the user didier to the group sys can be done two ways:

• In console mode or using a terminal emulator, become root with su then type:

  gpasswd --add didier sys

• In graphical mode from the Slint Control Center click on Users and Groups (System category), select the user and click Properties, then in the Groups tab check sys. Or the other way round (select the group then add the user to it).

There are several ways to add and configure a printer (remember: this has to be done by an user member of the group sys):

• From the Slint Control Center, category Hardware, click on Printer Setup to display a GUI allowing a simple setup…
• … Or click on Cups Print Control the display a web interface to the CUPS server. You can also display the web interface to the CUPS server typing localhost:631 in the address field of a web browser.
• If you have a Hewlett Packard device, make a right click on the hp logo in the notification area of the panel.

In Slint PulseAudio serves as a proxy to sound applications that interact with ALSA, the system that communicates with the sound cards drivers.

By default the services alsa, alsa-oss (that allows to use OSS instead of ALSA for legacy sound cards) and pulseaudio are not activated at system startup. This is intentional as this setting fits most use cases and allows an instance or PulseAudio to be be automatically started when an user logs in with specific settings for that user. Only change that if you know what you are doing.

To change the sound setup, the main tool is the pavucontrol mixer. You can start it from a terminal or application menu, and also from the Slint Control Center, Settings Category: PulseAudio Volume Control. Actually it allows more settings than just the volume control, take the time to explore all its features.

You can also use volume control applet in the notification area of the panel: a left click allows to adjust the volume, a right click gives access to other settings and allows to start the pavucontrol mixer.

The network has been configured during installation.

Would you need to change its configuration, you can use the netsetup command as root, or in the Slint Control Center, System category, click on Network Configuration.

In most cases, especially for a mobile computer or using wireless connections, NetworkManager is the recommended choice for network configuration. Then tne network manager applet is displayed in the notification area of the panel. Make left click on it to display available network and connect or disconnect form one of them, a right click right click to configure the connections.

You can also configure the host names, necessary for instance if your computer belongs to a a local network, clicking Hostnames in the Slint Control Center, category System.

During installation you were asked which system services activate by default at startup.

You can change these settings using either:

• The servicesetup command (TUI)
• The gtkervicesetup command (GUI), also accessible from the Slint Control Center, category System.

The services are managed by scripts whose name begin with rc. in the directory /etc/rc.d/. For instance the service acpi is managed by the shell script /etc/rc.d/rc.acpi. Most of the services are activated at startup if the corresponding script is executable. In the table below we indicate if it is activated at startup (on in the column A) or not (off in the column A). If the column is blank the activation of the services depend on a choice made during installation. The Package column indicate which software package provides the script corresponding to the service, case occurring