| SUSE LINUX Documentation Chapter 3. System Configuration with YaST / 3.2. Software | ||||
|---|---|---|---|---|
 | Chapter 3. System Configuration with YaST | 3.3. Hardware |  | |
| SUSE LINUX Documentation Chapter 3. System Configuration with YaST / 3.2. Software | ||||
|---|---|---|---|---|
| Chapter 3. System Configuration with YaST | 3.3. Hardware | | |
To install, uninstall, and update software on your machine, use . In Linux, software is available in the form of packages. Normally, a package contains everything needed for a program: the program itself, the configuration files, and all documentation. A package containing the source files for the program is also normally available. The sources are not needed for running the program, but you may want to install the sources to compile a custom version of the program.
Some packages depend on other packages. This means that the software of the package only works properly if another package is also installed. The installation of some packages is only possible if certain other packages are installed, perhaps because the installation routine requires specific tools. Such packages must be installed in the correct sequence. There are some packages with identical or similar functionalities. If these packages use the same system resource, they should not be installed at the same time (package conflict). Dependencies and conflicts can occur between two or more packages and are sometimes very complex. The fact that a specific package version may be required for smooth interaction can make things even more complicated.
All these factors must be taken into consideration when installing, uninstalling, and updating software. YaST provides an extremely efficient tool for this purpose: the software installation module, usually referred to as the package manager. When the package manager starts, it examines the system and displays installed packages. If you select additional packages for installation, the package manager automatically checks the dependencies and selects any other required packages (resolution of dependencies). If you select conflicting packages, the package manager indicates this and submits suggestions for solving the problem (resolution of conflicts). If a package required by other installed packages is marked for deletion, the package manager issues an alert with detailed information and alternative solutions.
Also use the package manager for the well-structured overview of the range of packages in SUSE Linux that it provides. The packages are arranged by subject and you can restrict display of these groups with filters.
To start the package manager, select . This opens a dialog as shown in Figure 3.2, “YaST Package Manager”. Modify the frame sizes by clicking and moving the borders separating the areas. The contents of the frames and their uses are described in the following sections.
Arrange the packages in categories and limit the number of packages displayed with the filters. View the filters in the left frame. The frame displays the settings for the current filter method. Choose the desired filter from the list in .
Initially, the filter is active. It groups the program packages according to their application purpose, such as multimedia or office applications. The various groups of the filter are listed with the installed packages preselected. Click the status box at the beginning of a line to change the status flags of a selection. Select a status directly by right-clicking the selection and using the context menu. From the individual package overview to the right, which displays the packages included in the current selection, select and deselect individual packages.
provides a more technical overview of the range of packages and is suitable if you are familiar with the package structure of SUSE Linux. This filter sorts the program packages by subjects, such as applications, development, and hardware, in a tree structure to the left. The more you expand the branches, the more specific the selection is. This means fewer packages are displayed in the individual package window.
Additionally, this filter lets you display all packages in alphabetic order without any categorization. To do this, select at the bottom of the tree. SUSE Linux contains a number of packages and it might take some time to display this long list.
Find a specific package with . By specifying various search criteria, restrict the search to display a few or even only one package. Enter a search string and use the check boxes to determine where to search for this string (in the name, in the description, or in the package dependencies). You can define special search patterns using wild cards and regular expressions and search the package dependencies in the and fields.
![[Tip]](admon/tip.png) | Quick Search |
|---|---|
In addition to the filter, all lists of the package manager feature a quick search. Simply enter a letter to move the cursor to the first package in the list whose name begins with this letter. The cursor must be in the list (by clicking the list). | |
To find language-specific packages, such as translated texts for the user interface of programs, documentation, and fonts, use . This filter shows a list of all languages supported by SUSE Linux. If you select one of these, the right frame shows all packages available for this language. Among these, all packages applying to your current software selection are automatically tagged for installation.
![[Note]](admon/note.png) | Note |
|---|---|
Because language-specific packages may depend on other packages, the package manager may select additional packages for installation. | |
After selecting the packages for installation, update, or deletion, view the installation summary with . It shows how packages will be affected when you click . Use the check boxes to the left to filter the packages to view in the individual package window. For example, to check which packages are already installed, start the package manager and deactivate all check boxes except .
The package status in the individual package window can be changed as usual. However, the respective package may no longer meet the search criteria. To remove such packages from the list, update the list with .
As already mentioned, a list of individual packages is displayed to the right in the individual package window. The content of this list is determined by the currently selected filter. If, for example, the filter is selected, the individual package window displays all packages of the current selection.
In the package manager, each package has a status that determines what to do with the package, such as “Install” or “Delete.” This status is shown by a symbol in a status box at the beginning of the line. Toggle the status by clicking or selecting the desired status from the menu that opens when the item is right-clicked. Depending on the current situation, some of the possible status flags may not be available for selection. For example, a package that has not yet been installed cannot be set to “Delete.” View the available status flags with +.
The package manager offers the following package status flags:
Do Not InstallThis package is not installed and will not be installed.
InstallThis package is not yet installed but will be installed.
KeepThis package is already installed and will not be changed.
UpdateThis package is already installed and will be replaced by the version on the installation medium.
DeleteThis package is already installed and will be deleted.
Taboo—Never InstallThis package is not installed and will never be installed. It is treated as if it does not exist on any of the installation media. If a package would automatically be selected to resolve dependencies, the “Taboo” setting prevents this. However, this may result in inconsistencies that must be resolved manually (dependency check). “Taboo” is mainly intended for expert users.
ProtectedThis package is installed and should not be modified. Third-party packages (packages without a SUSE signature) are automatically assigned this status to prevent them from being overwritten by later versions existing on the installation media. This may cause package conflicts that must be resolved manually.
Automatic InstallationThis package has been automatically selected for installation because it is required by another package (resolution of package dependencies). To deselect such a package, the status “Taboo” may be necessary.
Automatic UpdateThis package is already installed. However, because another package requires a newer version of this package, the installed version will automatically be updated.
Delete AutomaticallyThis package is already installed, but existing package conflicts require that this package be deleted. For example, this may be the case if the current package has been replaced by a different package.
Automatic Installation (after selection)This package has been automatically selected for installation because it is part of a predefined selection, such as “Multimedia” or “Development.”
Automatic Update (after selection)This package is already installed, but a newer version exists on the installation media. This package is part of a predefined selection, such as “Multimedia” or “Development,” selected for update and will automatically be updated.
Delete Automatically (after selection)This package is already installed, but a predefined selection (such as “Multimedia” or “Development”) requires that this package be deleted. This does not happen very often.
Additionally, you can decide whether to install the sources for a package. This information complements the current package status and cannot be toggled with the mouse or selected directly from the context menu. Instead, mark a check box at the end of the package line. This option can also be accessed under .
Also install the source code.
The sources will not be installed.
The font color used for various packages in the individual package window provides additional information. Installed packages for which a newer version is available on the installation media are displayed in blue. Installed packages whose version numbers are higher than those on the installation media are displayed in red. However, because the version numbering of packages is not always linear, the information may not be perfect, but should be sufficient to indicate problematic packages. If necessary, check the version numbers in the information window.
Get information about the selected package in the tabs in the bottom right frame. The description of the selected package is automatically active. Click the other tabs to view technical data (package size, group, etc.), the list of other packages on which it depends, or the version information.
During the selection of the software, the resource window at the bottom left of the module displays the prospective usage of all mounted file systems. The colored bar graph grows with every selection. As long as it remains green, there is sufficient space. The bar color slowly changes to red as you approach the limit of disk space. If you select too many packages for installation, an alert is displayed.
You can also use the menu bar at the top left of the window to access most of the functions already described. Find important functions in the following four menus:
Select + to save a list of all installed packages in a text file. This is recommended if you want to replicate a specific installation scope at a later date or on another system. Import a file generated in this way with to have the same package selection as was saved. In both cases, define the location of the file or accept the suggestion.
To exit the package manager without saving changes to the package selection, click . To save your changes, select . In this case, all changes are applied and the program is terminated.
The items in the menu always refer to the package currently selected in the individual package window. Although all status flags are displayed, you can only select those possible for the current package. Use the check boxes to specify whether to install the sources of the package. opens a submenu listing all package status flags that then affect all packages in this list.
The menu offers options for handling package dependencies and conflicts. If you have manually selected packages for installation, click to view the list of packages that the package manager has automatically selected to resolve dependencies. If there are still unresolved package conflicts, an alert is displayed and solutions suggested.
If you set package conflicts to , this information is saved permanently in the system. To unignore dependencies, click .
+ provides a brief explanation of the package manager functionality. A detailed description of the various package flags is available under . If you prefer to operate programs without using the mouse, click to view a list of keyboard shortcuts.
and are located under the information window. If you click , the package manager checks if the current package selection results in any unresolved package dependencies or conflicts. In the event of unresolved dependencies, the required additional packages are selected automatically. For package conflicts, the package manager opens a dialog that shows the conflict and offers various options for solving the problem.
If you activate , any change of a package status triggers an automatic check. This is a useful feature, because the consistency of the package selection is monitored permanently. However, this process consumes resources and can slow down the package manager. For this reason, the autocheck is not activated by default. In either case, a consistency check is performed when you confirm your selection with .
For example, sendmail and
postfix may not be installed concurrently.
Figure 3.3, “Conflict Management of the Package Manager”
shows the conflict message prompting you to make a decision.
postfix is already installed. Accordingly, you
can refrain from installing sendmail, remove
postfix, or take the risk and ignore the
conflict.
![[Warning]](admon/warning.png) | Handling Package Conflicts |
|---|---|
Unless you are very experienced, follow the suggestions of YaST when handling package conflicts, because otherwise the stability and functionality of your system could be endangered by the existing conflict. | |
You can use multiple installation sources of several types. Select them and enable their use for installation or update using . When started, it displays a list of all previously registered sources. Following a normal installation from CD, only the installation CD is listed. Click to include additional sources in this list. Sources can be CDs, DVDs, or network sources, such as NFS and FTP servers. Even directories on the local hard disk can be selected as the installation medium. See the detailed YaST help text for more details.
All registered sources have an activation status in the first column of the list. Enable or disable individual installation sources by clicking . During the installation of software packages or updates, YaST selects a suitable entry from the list of activated installation sources. When you exit the module with , the current settings are saved and applied to the configuration modules and .
Install important updates and improvements with the YaST Online Update (YOU). These patches are available for download on the SUSE FTP server and various mirror servers.
Under , select one of the various
servers. When you select a server, its URL is copied to the input field,
where it can be edited. You can also specify local URLs in the format
file:/my/path or /my/path.
Expand the existing list with additional servers using . Click to modify the
settings of the currently selected server.
When the module starts, is active, enabling selection of the patches to fetch. To apply all available recommended and security patches, deactivate this option. However, depending on the bandwidth of the connection and the amount of data to transmit, this can result in long download times.
If you activate , all available patches, installable packages, and descriptions are downloaded from the server. If this is not activated (default), only patches not yet installed on your system are retrieved.
To configure a process that automatically looks for updates and applies them on a regular basis, click . This procedure is fully automated. The system must be able to connect to the update server at the scheduled time.
To perform the update, click . For a manual update, this loads a list of all available patches and starts the package manager, described in Section 3.2.1, “Installing and Removing Software”. In the package manager, the filter for YOU patches is activated, enabling selection of updates to install. At start-up, the available security patches and recommended patches are preselected, if the applicable software is installed on the system. This proposal should be accepted.
After making your selection, click in the package manager. All selected updates are then downloaded from the server and installed on your machine. Depending on the connection speed and hardware performance, this may take some time. Any errors are displayed in a window. If necessary, skip a problematic package. Prior to the installation, some patches open a window displaying details.
While the updates are downloaded and installed, you can track all actions in the log window. Following the successful installation of all patches, exit YOU with . If you do not need the update files after the installation, select for them to be deleted after the update. Finally, SuSEconfig is executed to adjust the system configuration as needed.
installs patches from CD, not from an FTP server. The advantage lies in a much faster update with CD. After the patch CD is inserted, all patches on the CD are displayed in the dialog. Select the desired packages for installation from the list of patches. The module issues an error message if no patch CD is present. Insert the patch CD then restart the module.
Update the version of SUSE Linux installed on your system with . During operation, you can only update application software, not the base system. To update the base system, boot the computer from an installation medium, such as CD. When selecting the installation mode in YaST, select .
The procedure for updating the system is similar to a new installation. Initially, YaST examines the system, determines a suitable update strategy, and presents the results in a suggestion dialog. Click or the individual items to change any details.
Set the update method for your system. Two options are available.
To update the entire system to the latest versions of software, select one of the predefined selections. These selections are the same as those offered during the installation. They ensure that packages that did not exist previously are also installed.
This option merely updates packages that already exist on the system. No new features are installed.
Additionally, you can use to remove packages that do not exist in the new version. By default, this option is preselected to prevent outdated packages from unnecessarily occupying hard disk space.
Click to start the package manager and select or deselect individual packages for update. Any package conflicts should be resolved with the consistency check. The use of the package manager is covered in detail in Section 3.2.1, “Installing and Removing Software”.
During the update, the configuration files of some packages may be replaced by those of the new version. Because you may have modified some of the files in your current system, the package manager normally makes backup copies of the replaced files. With this dialog, determine the scope of these backups.
![[Important]](admon/important.png) | Scope of the Backup |
|---|---|
This backup does not include the software. It only contains configuration files. | |
Primary and other languages currently installed on the system are listed here. Change them by clicking in the displayed configuration or with +. You can choose to adapt the keyboard layout and time zone to the region where the primary language is spoken. More about language selection can be found in Section 3.7.11, “Language”.
The system update is a very complex procedure. For each program package, YaST must first check which version is installed on the computer then determine what needs to be done to replace the old version with the new version correctly. YaST also tries to adopt any personal settings of the installed packages. Some configurations may cause problems because the old configuration cannot handle the new program version as expected or because unexpected inconsistencies arise between various configurations.
The older the existing version is and the more the configuration of the packages to update differs from the standard, the more problematic an update is. Sometimes, the old configuration cannot be adopted correctly. In this case, reconfigure. Before starting the update, save the existing configuration.
Install packages into a directory for Xen with . Xen is a virtual machine monitor (VMM) for x86-compatible computers that enables you to run more than one virtual machine, each with its own OS, on a single physical system and with excellent performance. After selecting this module, YaST determines the system settings and lists the default directory, installation instructions, and software to install. Edit the defaults by clicking . Confirm all changes by clicking . After all changes have been made, click until you are informed that the installation is complete. Click to exit the dialog. Find detailed information about Xen in Chapter 37, Virtualization with Xen (↑Reference).
If you encounter any problems using the SUSE Linux installation media, you can check the CDs or DVDs with . Media problems are more likely to occur with media you burn yourself. To check that a SUSE Linux CD or DVD is error-free, insert the medium into the drive and run this module. Click for YaST to check the MD5 checksum of the medium. This may take several minutes. If any errors are detected, you should not use this medium for installation.
