This guide details how to install single or multiple systems, and how to exploit the product-inherent capabilities for a deployment infrastructure. Choose from various approaches: local installation from physical installation media, customizing the standard installation images, network installation server, mass deployment using a remote-controlled, highly-customized, automated installation process, and initial system configuration.
root
Copyright © 2006– 2022 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see https://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.
Installations of SUSE Linux Enterprise Desktop are possible in different ways. It is impossible to cover all combinations of boot, or installation server, automated installations or deploying images. This manual should help with selecting the appropriate method of deployment for your installation.
Most tasks that are needed during installations are described here. This includes the manual setup of your computer and installation of additional software, and cloning disk images and performing the setup remotely.
SUSE® Linux Enterprise Desktop can be installed in different ways. Apart from the usual media installation, you can choose from various network-based approaches. This part describes setting up an installation server and how to prepare the boot of the target system for installation.
Learn how to configure your system after installation. This part covers common tasks like setting up hardware components, installing or removing software, managing users, or changing settings with YaST.
Documentation for our products is available at https://documentation.suse.com/, where you can also find the latest updates, and browse or download the documentation in various formats. The latest documentation updates are usually available in the English version of the documentation.
Many commands are described in detail in their manual
pages. You can view manual pages by running the
man
command followed by a specific command name. If the
man
command is not installed on your system, install it
by running zypper install man
.
The following documentation is available for this product:
This Quick Start guides you step-by-step through the installation of SUSE® Linux Enterprise Desktop 15 SP1.
This guide details how to install single or multiple systems, and how to exploit the product-inherent capabilities for a deployment infrastructure. Choose from various approaches: local installation from physical installation media, customizing the standard installation images, network installation server, mass deployment using a remote-controlled, highly-customized, automated installation process, and initial system configuration.
Covers system administration tasks like maintaining, monitoring and customizing an initially installed system.
Introduces basic concepts of system security, covering both local and network security aspects. Shows how to use the product inherent security software like AppArmor, SELinux, or the auditing system that reliably collects information about any security-relevant events. Supports the administrator with security-related choices and decisions in installing and setting up a secure SUSE Linux Enterprise Server and additional processes to further secure and harden that installation.
An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to efficiently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources.
Introduces the GNOME desktop of SUSE Linux Enterprise Desktop. It guides you through using and configuring the desktop and helps you perform key tasks. It is intended mainly for end users who want to make efficient use of GNOME as their default desktop.
The release notes for this product are available at https://www.suse.com/releasenotes/.
Your feedback and contributions to this documentation are welcome. The following channels for giving feedback are available:
For services and support options available for your product, see https://www.suse.com/support/.
To open a service request, you need a SUSE subscription registered at SUSE Customer Center. Go to https://scc.suse.com/support/requests, log in, and click .
Report issues with the documentation at https://bugzilla.suse.com/. To simplify this process, you can use the links next to headlines in the HTML version of this document. These preselect the right product and category in Bugzilla and add a link to the current section. You can start typing your bug report right away. A Bugzilla account is required.
To contribute to this documentation, use the
links next to headlines in the HTML version of this document. They take you to the source code on GitHub, where you can open a pull request. A GitHub account is required.The
links are only available for the English version of each document. For all other languages, use the links instead.For more information about the documentation environment used for this documentation, see the repository's README at https://github.com/SUSE/doc-sle/blob/main/README.adoc
You can also report errors and send feedback concerning the documentation to <doc-team@suse.com>. Include the document title, the product version, and the publication date of the document. Additionally, include the relevant section number and title (or provide the URL) and provide a concise description of the problem.
The following notices and typographical conventions are used in this documentation:
/etc/passwd
: directory names and file names
PLACEHOLDER: replace PLACEHOLDER with the actual value
PATH
: the environment variable PATH
ls
, --help
: commands, options, and
parameters
user
: users or groups
package name : name of a package
Alt, Alt–F1: a key to press or a key combination; keys are shown in uppercase as on a keyboard
, › : menu items, buttons
Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a chapter in another manual.
Commands that must be run with root
privileges. Often you can also
prefix these commands with the sudo
command to run them
as non-privileged user.
root #
command
tux >
sudo
command
Commands that can be run by non-privileged users.
tux >
command
Notices
Vital information you must be aware of before proceeding. Warns you about security issues, potential loss of data, damage to hardware, or physical hazards.
Important information you should be aware of before proceeding.
Additional information, for example about differences in software versions.
Helpful information, like a guideline or a piece of practical advice.
SUSE products are supported for up to 13 years. To check the life cycle dates for your product, see https://www.suse.com/lifecycle/.
For SUSE Linux Enterprise, the following life cycles and release cycles apply:
SUSE Linux Enterprise Server has a 13-year life cycle: 10 years of general support and three years of extended support.
SUSE Linux Enterprise Desktop has a 10-year life cycle: seven years of general support and three years of extended support.
Major releases are published every four years. Service packs are published every 12-14 months.
SUSE supports previous SUSE Linux Enterprise service packs for six months after the release of a new service pack.
For some products, Long Term Service Pack Support (LTSS) is available. Find information about our support policy and options at https://www.suse.com/support/policy.html and https://www.suse.com/support/programs/long-term-service-pack-support.html.
Modules have a different life cycle, update policy, and update timeline than their base products. Modules contain software packages and are fully supported parts of SUSE Linux Enterprise Desktop. For more information, see the Article “Modules and Extensions Quick Start”.
To receive support, you need an appropriate subscription with SUSE. To view the specific support offerings available to you, go to https://www.suse.com/support/ and select your product.
The support levels are defined as follows:
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
For contracted customers and partners, SUSE Linux Enterprise Desktop is delivered with L3 support for all packages, except for the following:
Technology Previews
Sound, graphics, fonts and artwork.
Packages that require an additional customer contract.
Some packages shipped as part of the module Workstation Extension are L2-supported only.
Packages with names ending in -devel (containing header files and similar developer resources) will only be supported together with their main packages.
SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.
Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. The previews are included for your convenience to give you the chance to test new technologies within your environment. We would appreciate your feedback! If you test a technology preview, please contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.
However, technology previews come with the following limitations:
Technology previews are still in development. Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures.
Details and functionality of technology previews are subject to change. As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
Technology previews can be dropped at any time. For example, if SUSE discovers that a preview does not meet the customer or market needs, or does not prove to comply with enterprise standards. SUSE does not commit to providing a supported version of such technologies in the future.
For an overview of technology previews shipped with your product, see the release notes at https://www.suse.com/releasenotes/.
This chapter describes some basic considerations before installing SUSE Linux Enterprise Desktop.
This chapter describes the steps necessary to prepare for the installation of SUSE Linux Enterprise Desktop on AMD64 and Intel 64 computers. It introduces the steps required to prepare for various installation methods. The list of hardware requirements provides an overview of systems supported by SUSE Linux Enterprise Server. Find information about available installation methods and several commonly known problems. Also learn how to control the installation, provide installation media, and boot with regular methods.
This chapter describes some basic considerations before installing SUSE Linux Enterprise Desktop.
This chapter is addressed mainly to corporate system administrators who face the task of having to deploy SUSE® Linux Enterprise Desktop at their site. Rolling out SUSE Linux Enterprise Desktop to an entire site should involve careful planning and consideration of the following questions:
Determine the purpose for which SUSE Linux Enterprise Desktop should be used and make sure that hardware and software with the ability to match these requirements are used. Consider testing your setup on a single machine before rolling it out to the entire site.
Determine the scope of your deployment of SUSE Linux Enterprise Desktop. Depending on the number of installations planned, consider different approaches to the installation or even a mass installation using SUSE Linux Enterprises unique AutoYaST or KIWI technology.
All patches provided by SUSE for your product are available for download to registered users at http://download.suse.com/.
SUSE provides training, support, and consulting for all topics pertaining to SUSE Linux Enterprise Desktop. Find more information about this at https://www.suse.com/products/desktop/.
In the following sections, the system to hold your new SUSE Linux Enterprise Desktop installation is called target system or installation target. The term repository (previously called “installation source”) is used for all sources of installation data. This includes physical media, such as CD and DVD, and network servers distributing the installation data in your network.
For a standard installation of SUSE Linux Enterprise Desktop, including the desktop environment and a wealth of applications, the following configuration is recommended:
Intel Pentium IV, 2.4 GHz or higher or any AMD64 or Intel 64 processor
1–2 physical CPUs
512 MB physical RAM or higher
3 GB of available disk space or more
1024 x 768 display resolution (or higher)
Let the following items guide you in your selection of SUSE Linux Enterprise Desktop and determining the purpose of the installed systems:
SUSE Linux Enterprise Desktop's broad offer of software makes it appeal to both professional users in a corporate environment and to home users or users in smaller networks.
SUSE Linux Enterprise Desktop comes with the enterprise-ready desktop environment GNOME. It enables users to comfortably adjust to a Linux system while maintaining their efficiency and productivity. To explore GNOME in detail, refer to the Book “GNOME User Guide”.
With the NetworkManager technology fully integrated into SUSE Linux Enterprise Desktop and its two desktop environments, mobile users will enjoy the freedom of easily joining and switching wired and wireless networks.
SUSE Linux Enterprise Desktop was designed to be a versatile network citizen. It cooperates with various different network types:
Pure Linux Networks. SUSE Linux Enterprise Desktop is a complete Linux client and supports all the protocols used in traditional Linux and Unix* environments. It integrates well with networks consisting of other SUSE Linux or SUSE Linux Enterprise machines. LDAP, NIS, and local authentication are supported.
Windows Networks. SUSE Linux Enterprise Desktop supports Active Directory as an authentication source. It offers you all the advantages of a secure and stable Linux operating system plus convenient interaction with other Windows clients, as well as the means to manipulate your Windows user data from a Linux client. Explore this feature in detail in Book “Security and Hardening Guide”, Chapter 8 “Active Directory Support”.
SUSE Linux Enterprise Desktop enables you to secure your applications by enforcing security profiles tailor-made for your applications. To learn more about AppArmor, refer to Book “Security and Hardening Guide”.
This chapter describes the steps necessary to prepare for the installation of SUSE Linux Enterprise Desktop on AMD64 and Intel 64 computers. It introduces the steps required to prepare for various installation methods. The list of hardware requirements provides an overview of systems supported by SUSE Linux Enterprise Server. Find information about available installation methods and several commonly known problems. Also learn how to control the installation, provide installation media, and boot with regular methods.
The SUSE® Linux Enterprise Server operating system can be deployed on a wide range of hardware. It is impossible to list all the different combinations of hardware SUSE Linux Enterprise Server supports. However, to provide you with a guide to help you during the planning phase, the minimum requirements are presented here.
If you want to be sure that a given computer configuration will work, find out which platforms have been certified by SUSE. Find a list at https://www.suse.com/yessearch/.
The Intel 64 and AMD64 architectures support the simple migration of x86 software to 64 bits. Like the x86 architecture, they constitute a value-for-money alternative.
All CPUs available on the market to date are supported.
The maximum number of CPUs supported by software design is 8192 for Intel 64 and AMD64. If you plan to use such a large system, verify with our hardware system certification Web page for supported devices, see https://www.suse.com/yessearch/.
A minimum of 1024 MB of memory is required for a minimal installation. On machines with more than two processors, add 512 MB per CPU. For remote installations via HTTP or FTP add another 150 MB. Note that these values are only valid for the installation of the operating system—the actual memory requirement in production depends on the system's workload.
The disk requirements depend largely on the installation selected and how you use your machine. Commonly, you need more space than the installation software itself needs to have a system that works properly. Minimum requirements for different selections are:
Installation Scope |
Minimum Hard Disk Requirements |
---|---|
Text Mode |
1.5 GB |
Minimal System |
2.5 GB |
GNOME Desktop |
3 GB |
All patterns |
4 GB |
Recommended Minimum (no Btrfs snapshots): 10 GB | |
Required Minimum (with Btrfs snapshots): 16 GB | |
Recommended Minimum (with Btrfs snapshots): 32 GB |
If your root partition is smaller than 10 GB, the installer will not make an automated partitioning proposal and you need to manually create partitions. Therefore the recommended minimum size for the root partition is 10 GB. If you want to enable Btrfs snapshots on the root volume to enable system rollbacks (see Book “Administration Guide”, Chapter 7 “System Recovery and Snapshot Management with Snapper”) the minimum size for the root partition is 16 GB.
The computer can be booted from a CD or a network. A special boot server is required to boot over the network. This can be set up with SUSE Linux Enterprise Server.
This section encompasses many factors that need to be considered before installing SUSE Linux Enterprise Desktop on AMD64 and Intel 64 hardware.
SUSE Linux Enterprise Desktop is normally installed as an independent operating system. With virtualization it is also possible to run multiple instances of SUSE Linux Enterprise Server on the same hardware. However, the installation of the VM Host Server is performed like a typical installation with some additional packages.
Most installations are to a local hard disk. Therefore, it is necessary for the hard disk controllers to be available to the installation system. If a special controller (like a RAID controller) needs an extra kernel module, provide a kernel module update disk to the installation system.
Other installation targets may be various types of block devices that
provide sufficient disk space and speed to run an operating system. This
includes network block devices like iSCSI
or
SAN
. It is also possible to install on network file
systems that offer the standard Unix permissions. However, it may be
problematic to boot these, because they must be supported by the
initramfs
before the actual system can start. Such
installations can be useful when you need to start the same system in
different locations or you plan to use virtualization features like
domain migration.
Control the installation in one of several ways. Boot the setup with one of the options listed in Section 2.4, “Booting the Installation System”. To enable the different control methods refer to Section 3.3.4, “Specifying Remote Access”. For information about how to use each remote control method, refer to Chapter 7, Remote Installation.
A brief overview of the different methods:
This is the method most frequently used to install SUSE Linux Enterprise Desktop. This also requires the smallest preparation effort but requires a lot of direct interaction.
You can control the installation via SSH either in text mode or use X-forwarding for a graphical installation. For details refer to Section 7.4, “Monitoring Installation via SSH”.
For this installation method you need a second computer connected by a null modem cable to the computer on which to install SUSE Linux Enterprise Desktop. The installation then proceeds in text mode. For details refer to Section 7.5, “Monitoring Installation via Serial Console”.
Use this method if you want a graphical installation without direct access to the target machine. For details refer to Section 7.3, “Monitoring Installation via VNC”.
This section gives an overview of the steps required for the complete installation of SUSE® Linux Enterprise Desktop.
Unlike previous SLE products, the entire SLE 15 SP1 product line can be installed using the Unified Installer.
For a full description of how to install and configure the system with YaST, refer to Part II, “Installation Procedure”.
Prepare the installation media.
This is the simplest way to start the installation. To create a bootable
flash disk, you need to copy a DVD image to the device using the dd
command. The flash disk must not be mounted, and all data on the device
will be erased.
root #
dd
if=PATH_TO_ISO_IMAGE of=USB_STORAGE_DEVICE bs=4M
DVD media are available from SUSE, or you can make your own. This method is useful if you have multiple machines to provision at the same time. It requires either a built-in or removable DVD drive. The process is straightforward for most computer users, but requires a lot of interaction for every installation process. If you did not receive a DVD, get the ISO image from the SUSE home page and burn it to a blank, writable DVD.
If the target computer's firmware supports it, you can boot the computer from the network and install from a server. This booting method requires a boot server that provides the needed boot images over the network. The exact protocol depends on your hardware. Commonly you need several services, such as TFTP and DHCP or PXE boot. For details, read Chapter 13, Preparing Network Boot Environment.
It is possible to install from many common network protocols, such as NFS, HTTP, FTP, or SMB. For more information on how to perform such an installation, refer to Chapter 7, Remote Installation.
Configure the target system firmware to boot the medium you chose. Refer to the documentation of your hardware vendor about how to configure the correct boot order.
Set the boot parameters required for your installation method. An overview of the different methods is provided in Section 2.3, “Controlling the Installation”. A list of boot parameters is available in Chapter 3, Boot Parameters.
Perform the installation as described in Chapter 4, Installation Steps. The system needs to restart after the installation is finished.
Optional: Change the boot order of the system to directly boot from the medium to which SUSE Linux Enterprise Desktop has been installed. If the system boots from the installation medium, the first boot parameter will be to boot the installed system.
Perform the initial system configuration as described in Part V, “Initial System Configuration”.
Prior to delivery, SUSE® Linux Enterprise Desktop is subjected to an extensive test program. Despite this, problems occasionally occur during boot or installation.
Boot problems may prevent the YaST installer from starting on your system. Another symptom is when your system does not boot after the installation has been completed.
Change your computer's firmware or BIOS so that the boot sequence is correct. To do this, consult the manual for your hardware.
Change the console on your computer so that the kernel outputs are visible. Be sure to check the last outputs. This is normally done by pressing Ctrl–Alt–F10. If you cannot resolve the problem, consult the SUSE Linux Enterprise Desktop support staff. To log all system messages at boot time, use a serial connection as described in Section 2.3, “Controlling the Installation”.
The boot disk is a useful interim solution if you have difficulties setting the other configurations or if you want to postpone the decision regarding the final boot mechanism. For more details on creating boot disks, see Book “Administration Guide”, Chapter 14 “The Boot Loader GRUB 2” grub2-mkrescue.
There are BIOS variants that check the structure of the boot sector (MBR) and erroneously display a virus warning after the installation of GRUB 2. Solve this problem by entering the BIOS and looking for corresponding adjustable settings. For example, switch off
. You can switch this option back on again later. It is unnecessary, however, if Linux is the only operating system you use.If an unexpected problem occurs during installation, information is needed to determine the cause of the problem. Use the following directions to help with troubleshooting:
Check the outputs on the various consoles. You can switch consoles with the key combination Ctrl–Alt–Fn. For example, obtain a shell in which to execute various commands by pressing Ctrl–Alt–F2.
Try launching the installation with “Safe Settings” (press
F5 on the installation screen and choose ). If the installation works without problems in this
case, there is an incompatibility that causes either
ACPI
or APIC
to fail. In
some cases, a BIOS or firmware update fixes this problem.
Check the system messages on a console in the installation system by
entering the command dmesg -T
.
To simplify the installation process and avoid accidental installations, the default setting on the installation DVD for SUSE Linux Enterprise Desktop is that your system is booted from the first hard disk. At this point, an installed boot loader normally takes over control of the system. This means that the boot DVD can stay in the drive during an installation. To start the installation, choose one of the installation possibilities in the boot menu of the media.
SUSE Linux Enterprise Desktop allows setting several parameters during boot, for example choosing the source of the installation data or setting the network configuration.
This chapter describes the procedure in which the data for SUSE Linux Enterprise Desktop is copied to the target device. Some basic configuration parameters for the newly installed system are set during the procedure. A graphical user interface will guide you through the installation. The procedure described in the following also applies to remote installation procedures as described in Chapter 7, Remote Installation. The text mode installation has the same steps and only looks different.
To get technical support and product updates, you need to register and activate SUSE Linux Enterprise Desktop with the SUSE Customer Center. It is recommended to register during the installation, since this will enable you to install the system with the latest updates and patches available. However, if you are offline or want to skip the registration step, you can register at any time later from the installed system.
Modules and extensions add features to your system and allow you to customize the system according to your needs. These components also need to be registered and can be managed with YaST or command line tools. For more details also refer to the Article “Modules and Extensions Quick Start”.
Sophisticated system configurations require specific disk setups. You can perform all common partitioning tasks during the installation.
The installation of SUSE® Linux Enterprise Desktop can be fully performed over the network. This chapter describes how to provide the required environment for booting, installing and controlling the installation via the network.
This section highlights some typical problems you may run into during installation and offers possible solutions or workarounds.
SUSE Linux Enterprise Desktop allows setting several parameters during boot, for example choosing the source of the installation data or setting the network configuration.
Using the appropriate set of boot parameters helps simplify your installation
procedure. Many parameters can also be configured later using the linuxrc
routines, but using the boot parameters is easier. In some automated setups,
the boot parameters can be provided with initrd
or an
info
file.
The way the system is started for the installation depends on the architecture—system start-up is different for PC (AMD64/Intel 64) or mainframe, for example. If you install SUSE Linux Enterprise Desktop as a VM Guest on a KVM or Xen hypervisor, follow the instructions for the AMD64/Intel 64 architecture.
The terms Boot Parameters and Boot Options are often used interchangeably. In this documentation, we mostly use the term Boot Parameters.
The boot parameters are described in detail in Chapter 4, Installation Steps. Generally, selecting starts the installation boot process.
If problems occur, use Chapter 8, Troubleshooting.
or . For more information about troubleshooting the installation process, refer toThe menu bar at the bottom of the screen offers some advanced functionality needed in some setups. Using the function keys (F1 ... F12), you can specify additional options to pass to the installation routines without having to know the detailed syntax of these parameters (see Chapter 3, Boot Parameters). A detailed description of the available function keys is available in Section 3.2.1, “The Boot Screen on Machines Equipped with Traditional BIOS”.
This section describes changing the boot parameters for AMD64, Intel 64, and Arm AArch64.
The boot screen displays several options for the installation procedure. Enter to boot it. The relevant options are:
boots the installed system and is selected by default, because the CD is often left in the drive. Select one of the other options with the arrow keys and pressThe normal installation mode. All modern hardware functions are enabled. In case the installation fails, see F5 for boot parameters that disable potentially problematic functions.
Perform a system upgrade. For more information refer to Book “Upgrade Guide”, Chapter 1 “Upgrade Paths and Methods”.
Starts a minimal Linux system without a graphical user interface. For more information, see Book “Administration Guide”, Chapter 37 “Common Problems and Their Solutions”, Section 37.5.2 “Using the Rescue System”. This option is not available on live CDs.
Boot a Linux system that is already installed. You will be asked from which partition to boot the system.
This option is only available when you install from media created from downloaded ISOs. In this case it is recommended to check the integrity of the installation medium. This option starts the installation system before automatically checking the media. In case the check was successful, the normal installation routine starts. If a corrupt media is detected, the installation routine aborts. Replace the broken medium and restart the installation process.
Tests your system RAM using repeated read and write cycles. Terminate the test by rebooting. For more information, see Section 8.4, “Boot Failure”. This option is not available on the live CDs.
Use the function keys shown at the bottom of the screen to change the language, screen resolution, installation source or to add an additional driver from your hardware vendor:
Get context-sensitive help for the active element of the boot screen. Use the arrow keys to navigate, Enter to follow a link, and Esc to leave the help screen.
Select the display language and a corresponding keyboard layout for the installation. The default language is English (US).
Select various graphical display modes for the installation. By
“Kernel Mode Setting”). If this setting does not
work on your system, choose and, optionally,
specify vga=ask
on the boot command line to get
prompted for the video resolution. Choose
if the graphical installation causes problems.
Normally, the installation is performed from the inserted installation medium. Here, select other sources, like FTP or NFS servers. If the installation is deployed on a network with an SLP server, select an installation source available on the server with this option. Find information about setting up an installation server with SLP at Chapter 12, Setting Up a Network Installation Source.
If you encounter problems with the regular installation, this menu offers to disable a few potentially problematic functions. If your hardware does not support ACPI (advanced configuration and power interface) select
to install without ACPI support. disables support for APIC (Advanced Programmable Interrupt Controllers) which may cause problems with some hardware. boots the system with the DMA mode (for CD/DVD-ROM drives) and power management functions disabled.If you are not sure, try the following options first:
or . Experts can also use the command line ( ) to enter or change kernel parameters.Press this key to notify the system that you have an optional driver update for SUSE Linux Enterprise Desktop. With or , load drivers directly before the installation starts. If you select , you are prompted to insert the update disk at the appropriate point in the installation process.
Driver updates for SUSE Linux Enterprise are provided at http://drivers.suse.com/. These drivers have been created via the SUSE SolidDriver Program.
UEFI (Unified Extensible Firmware Interface) is a new industry standard which replaces and extends the traditional BIOS. The latest UEFI implementations contain the “Secure Boot” extension, which prevents booting malicious code by only allowing signed boot loaders to be executed. See Book “Administration Guide”, Chapter 13 “UEFI (Unified Extensible Firmware Interface)” for more information.
The boot manager GRUB 2, used to boot machines with a traditional BIOS,
does not support UEFI, therefore GRUB 2 is replaced with GRUB 2 for EFI. If
Secure Boot is enabled, YaST will automatically select GRUB 2 for EFI for
installation. From an administrative and user perspective, both
boot manager implementations behave the same and are called
GRUB 2
in the following.
When installing with Secure Boot enabled, you cannot load drivers that are not shipped with SUSE Linux Enterprise Desktop. This is also true of drivers shipped via SolidDriver, because their signing key is not trusted by default.
To load drivers not shipped with SUSE Linux Enterprise Desktop, do either of the following:
Before the installation, add the needed keys to the firmware database via firmware/system management tools.
Use a bootable ISO that will enroll the needed keys in the MOK list on the first boot.
For more information, see Book “Administration Guide”, Chapter 13 “UEFI (Unified Extensible Firmware Interface)”, Section 13.1 “Secure Boot”.
The boot screen displays several options for the installation procedure. Change the selected option with the arrow keys and press Enter to boot it. The relevant options are:
The normal installation mode. All modern hardware functions are enabled. In case the installation fails, see F5 for boot parameters that disable potentially problematic functions.
Perform a system upgrade. For more information refer to Book “Upgrade Guide”, Chapter 1 “Upgrade Paths and Methods”.
Starts a minimal Linux system without a graphical user interface. For more information, see Book “Administration Guide”, Chapter 37 “Common Problems and Their Solutions”, Section 37.5.2 “Using the Rescue System”. This option is not available on Live CDs.
Boot a Linux system that is already installed. You will be asked from which partition to boot the system.
This option is only available when you install from media created from downloaded ISOs. In this case it is recommended to check the integrity of the installation medium. This option starts the installation system before automatically checking the media. In case the check was successful, the normal installation routine starts. If a corrupt media is detected, the installation routine aborts.
GRUB 2 for EFI on SUSE Linux Enterprise Desktop does not support a boot prompt or function keys for adding boot parameters. By default, the installation will be started with American English and the boot media as the installation source. A DHCP lookup will be performed to configure the network. To change these defaults or to add boot parameters you need to edit the respective boot entry. Highlight it using the arrow keys and press E. See the on-screen help for editing hints (note that only an English keyboard is available now). The entry will look similar to the following:
setparams 'Installation' set gfxpayload=keep echo 'Loading kernel ...' linuxefi /boot/x86_64/loader/linux splash=silent echo 'Loading initial ramdisk ...' initrdefi /boot/x86_64/loader/initrd
Add space-separated parameters to the end of the line starting with
linuxefi
. To boot the edited entry, press
F10. If you access the machine via serial console, press
Esc–0. A
complete list of parameters is available at
https://en.opensuse.org/Linuxrc.
This section contains a selection of important boot parameters.
autoyast=
URL
The autoyast
parameter specifies the location of the
autoinst.xml
control file for automatic
installation.
manual=<0|1>
The manual
parameter controls whether the other
parameters are only default values that still must be acknowledged by
the user. Set this parameter to 0
if all values
should be accepted and no questions asked. Setdeploy your instancesting
autoyast
implies setting manual
to
0
.
Info=
URL
Specifies a location for a file from which to read additional options.
upgrade=<0|1>
To upgrade SUSE Linux Enterprise Desktop, specify Upgrade=1
.
dud=
URLLoad driver updates from URL.
Set dud=ftp://ftp.example.com/PATH_TO_DRIVER
or dud=http://www.example.com/PATH_TO_DRIVER
to load drivers from a URL. When dud=1
you will
be asked for the URL during boot.
language=
LANGUAGE
Set the installation language. Some supported values are
cs_CZ
, de_DE
,
es_ES
, fr_FR
,
ja_JP
, pt_BR
,
pt_PT
, ru_RU
,
zh_CN
, and zh_TW
.
acpi=off
Disable ACPI support.
noapic
No logical APIC.
nomodeset
Disable KMS.
textmode=1
Start installer in text mode.
console=
SERIAL_DEVICE[,MODE]
SERIAL_DEVICE can be an actual serial or parallel
device (for example ttyS0
) or a virtual terminal
(for example tty1
). MODE
is the baud rate, parity and stop bit (for example 9600n8
).
The default for this setting is set by the mainboard firmware. If you do
not see output on your monitor, try setting console=tty1
.
It is possible to define multiple devices.
The settings discussed in this section apply only to the network interface used during installation. Configure additional network interfaces in the installed system by following the instructions given in Book “Administration Guide”, Chapter 19 “Basic Networking”, Section 19.6 “Configuring a Network Connection Manually”.
The network will only be configured if it is required during the installation.
To force the network to be configured, use the netsetup
parameter.
netsetup=VALUE
netsetup=dhcp
forces a configuration via DHCP.
Set netsetup=-dhcp
when configuring the network
with the boot parameters hostip
,
gateway
and nameserver
.
With the option
netsetup=hostip,netmask,gateway,nameserver
the
installer asks for the network settings during boot.
ifcfg=INTERFACE[.VLAN]=SETTINGS
INTERFACE can be *
to
match all interfaces or, for example, eth*
to match
all interfaces that start with eth
. It is also
possible to use MAC addresses as values.
Optionally, a VLAN can be set behind the interface name, separated by a period.
If SETTINGS is dhcp
, all
matching interfaces will be configured with DHCP. It is possible to
set static parameters. With static parameters, only the first matching
interface will be configured. The syntax for the static configuration is:
ifcfg=*="IPS_NETMASK,GATEWAYS,NAMESERVERS,DOMAINS"
Each comma separated value can in turn contain a list of space character
separated values. IPS_NETMASK is in the
CIDR notation, for example
10.0.0.1/24
. The quotes are only needed when using
space character separated lists. Example with two name servers:
ifcfg=*="10.0.0.10/24,10.0.0.1,10.0.0.1 10.0.0.2,example.com"
The ifcfg
boot parameter is very powerful and allows
you to set almost all networking parameters. In addition to the
parameters mentioned above, you can set values for all configuration
options (comma separated) from
/etc/sysconfig/network/ifcfg.template
and
/etc/sysconfig/network/config
. The following
example sets a custom MTU size on an interface otherwise configured via
DHCP:
ifcfg=eth0=dhcp,MTU=1500
hostname=host.example.com
Enter the fully qualified host name.
domain=example.com
Domain search path for DNS. Allows you to use short host names instead of fully qualified ones.
hostip=192.168.1.2[/24]
Enter the IP address of the interface to configure. The IP can contain
the subnet mask, for example hostip=192.168.1.2/24
.
This setting is only evaluated if the network is required during the
installation.
gateway=192.168.1.3
Specify the gateway to use. This setting is only evaluated if the network is required during the installation.
nameserver=192.168.1.4
Specify the DNS server in charge. This setting is only evaluated if the network is required during the installation.
domain=example.com
Domain search path. This setting is only evaluated if the network is required during the installation.
If you are not using the DVD for installation, specify an alternative installation source.
install=SOURCE
Specify the location of the installation source to use. Possible
protocols are cd
, hd
,
slp
, nfs
, smb
(Samba/CIFS), ftp
, tftp
http
, and https
. Not all source
types are available on all platforms.
The default option is cd
.
If an ftp
, tftp
or
smb
URL is given, specify the user name and password
with the URL. These parameters are optional and anonymous or guest login
is assumed if they are not given. Example:
install=ftp://USER:PASSWORD@SERVER/DIRECTORY/DVD1/
To install over an encrypted connection, use an
https
URL. If the certificate cannot be verified, use
the sslcerts=0
boot parameter to disable certificate
checking.
In case of a Samba or CIFS installation, you can also specify the domain that should be used:
install=smb://WORKDOMAIN;USER:PASSWORD@SERVER/DIRECTORY/DVD1/
To use cd
, hd
or slp
,
set them as the following example:
install=cd:/ install=hd:/?device=sda/PATH_TO_ISO install=slp:/
Only one of the different remote control methods should be specified at a time. The different methods are: SSH, VNC, remote X server. For information about how to use the parameters listed in this section, see Chapter 7, Remote Installation.
display_ip=
IP_ADDRESS
Display_IP
causes the installing system to
try to connect to an X server at the given address.
The direct installation with the X Window System relies on a primitive authentication mechanism based on host names. This mechanism is disabled on current SUSE Linux Enterprise Desktop versions. Installation with SSH or VNC is preferred.
vnc=1
Enables a VNC server during the installation.
vncpassword=
PASSWORDSets the password for the VNC server.
ssh=1
ssh
enables SSH installation.
ssh.password=
PASSWORDSpecifies an SSH password for the root user during installation.
To configure access to a local RMT or
supportconfig
server for the installation, you can
specify boot parameters to
set up these services during installation. The same applies if you need IPv6 support
during the installation.
By default, updates for SUSE Linux Enterprise Desktop are delivered by the SUSE Customer Center. If your network provides a so called RMT server to provide a local update source, you need to equip the client with the server's URL. Client and server communicate solely via HTTPS protocol, therefore you also need to enter a path to the server's certificate if the certificate was not issued by a certificate authority.
Providing parameters for accessing an RMT server is only needed for non-interactive installations. During an interactive installation the data can be provided during the installation (see Section 4.6, “Registration” for details).
regurl
URL of the RMT server. This URL has a fixed format of
https://FQN/center/regsvc/
.
FQN needs to be a fully qualified host name
of the RMT server. Example:
regurl=https://smt.example.com/center/regsvc/
Make sure the values you enter are correct. If regurl
has not been specified correctly, the registration of the update source
will fail.
regcert
Location of the RMT server's certificate. Specify one of the following locations:
Remote location (HTTP, HTTPS or FTP) from which the certificate can
be downloaded. In case regcert is not specified, it will default to
http://FQN/smt.crt
with
FQN
being the name of the RMT server. Example:
regcert=http://rmt.example.com/smt-ca.crt
Absolute path to the certificate on the local machine. Example:
regcert=/data/inst/smt/smt-ca.cert
Use ask
to open a pop-up menu during the
installation where you can specify the path to the certificate. Do
not use this option with AutoYaST. Example
regcert=ask
Use done
if the certificate will be
installed by an add-on product, or if you are using a certificate
issued by an official certificate authority. For example:
regcert=done
supportconfig
#Edit sourceThe data that supportconfig (see Book “Administration Guide”, Chapter 36 “Gathering System Information for Support” for more information) gathers is sent to the SUSE Customer Center by default. It is also possible to set up a local server to collect this data. If such a server is available on your network, you need to set the server's URL on the client. This information needs to be entered at the boot prompt.
supporturl
.
URL of the server. The URL has the format
http://FQN/Path/
, where
FQN is the fully qualified host name
of the server and Path is the location on the
server. For example:
supporturl=http://support.example.com/supportconfig/data/
By default you can only assign IPv4 network addresses to your machine. To enable IPv6 during installation, enter one of the following parameters at the boot prompt:
ipv6=1
ipv6only=1
In networks enforcing the usage of a proxy server for accessing remote Web sites, registration during installation is only possible when configuring a proxy server.
To use a proxy during the installation, press F4 on the boot screen and set the required parameters in the dialog.
Alternatively, provide the kernel parameter proxy
at the
boot prompt:
On the installation screen, press e to open the editor of boot parameters.
Add a new line with the following syntax:
proxy=http://USER:PASSWORD@proxy.example.com:PORT
Specifying USER and PASSWORD is optional—if the server allows anonymous access, the following data is sufficient:
http://proxy.example.com:PORT
The outcome will be similar to the following:
Press F10 to boot with the new proxy setting.
Enabling SELinux upon installation start-up enables you to configure it after the installation has been finished without having to reboot. Use the following parameters:
security=selinux selinux=1
During installation and upgrade, YaST can update itself as described
in Section 4.2, “Installer Self-Update” to solve potential bugs
discovered after release. The self_update
parameter can
be used to modify the behavior of this feature.
To enable the installer self-update, set the parameter to
1
:
self_update=1
To use a user-defined repository, specify a URL:
self_update=https://updates.example.com/
If your screen uses a very high DPI, use the boot parameter
QT_AUTO_SCREEN_SCALE_FACTOR
.
This scales font and user interface elements to the screen DPI.
QT_AUTO_SCREEN_SCALE_FACTOR=1
The boot parameter mitigations
lets you control mitigation
options for side-channel attacks on affected CPUs. Its possible values are:
auto
.
Enables all mitigations required for your CPU model, but does
not protect against cross-CPU thread attacks. This setting may impact
performance to some degree, depending on the workload.
nosmt
.
Provides the full set of available security mitigations. Enables all
mitigations required for your CPU model. In addition, it disables
Simultaneous Multithreading (SMT) to avoid side-channel attacks across
multiple CPU threads. This setting may further impact performance,
depending on the workload.
off
.
Disables all mitigations. Side-channel attacks against your CPU
are possible, depending on the CPU model. This setting has no impact
on performance.
Each value comes with a set of specific parameters, depending on the CPU architecture, the kernel version, and on the vulnerabilities that need to be mitigated. Refer to the kernel documentation for details.
You can find more information about boot parameters in the openSUSE wiki at https://en.opensuse.org/SDB:Linuxrc#Parameter_Reference.
This chapter describes the procedure in which the data for SUSE Linux Enterprise Desktop is copied to the target device. Some basic configuration parameters for the newly installed system are set during the procedure. A graphical user interface will guide you through the installation. The procedure described in the following also applies to remote installation procedures as described in Chapter 7, Remote Installation. The text mode installation has the same steps and only looks different.
If you are a first-time user of SUSE Linux Enterprise Desktop, you should follow the default YaST proposals in most parts, but you can also adjust the settings as described here to fine-tune your system according to your preferences. Help for each installation step is provided by clicking .
If the installer does not detect your mouse correctly, use →| for navigation, arrow keys to scroll, and Enter to confirm a selection. Various buttons or selection fields contain a letter with an underscore. Use Alt–Letter to select a button or a selection directly instead of navigating there with →|.
This section provides an overview of all installation steps. Each step contains a link to a more detailed description.
Before the installation starts, the installer can update itself. For details, see Section 4.2, “Installer Self-Update”.
The actual installation starts with choosing the language and the product. For details, see Section 4.3, “ Language, Keyboard, and Product Selection ”.
Accept the license agreement. For details, see Section 4.4, “License Agreement”.
Configure the network. This is only required when you need network access during the installation and the automatic network configuration via DHCP failed. If the automatic network configuration succeeded, this step is skipped. For details, see Section 4.5, “Network Settings”.
With a working network connection you can register the machine at the SUSE Customer Center or an RMT server. For details, see Section 4.6, “Registration”.
Select the modules you want to enable for the machine. This impacts the availability of system roles in the next step and packages later on. For details, see Section 4.7, “Extension and Module Selection”.
You can manually add repositories. For details, see Section 4.8, “Add-On Product”.
Select a role for your system. Among other things, this defines the default list of packages to install and makes a suggestion for partitioning the hard disks. For details, see Section 4.9, “System Role”.
Partition the hard disks of your system. For details, see Section 4.10, “Partitioning”.
Choose a time zone. For details, see Section 4.11, “Clock and Time Zone”.
Create a user. For details, see Section 4.12, “Create New User”.
Optionally, set a different password for the system administrator
root
. For details, see Section 4.13, “Authentication for the System Administrator “root””.
In a final step, the installer presents an overview of all settings. If required, you can change them. For details, see Section 4.14, “Installation Settings”.
The installer copies all required data and informs you about the progress. For details, see Section 4.15, “Performing the Installation”.
During the installation and upgrade process, YaST can update itself to
solve bugs in the installer that were discovered after the release. This
functionality is enabled by default; to disable it, set the boot parameter
self_update
to 0
. For more information,
see Section 3.4.6, “Enabling the Installer Self-Update”.
The installer self-update is only available if you use the GM
images of the Unified Installer and Packages ISOs. If you install from the ISOs published
as quarterly update (they can be identified by the string QU
in the name), the installer cannot update itself, because this feature has
been disabled in the updated media.
To download installer updates, YaST needs network access. By default, it tries to use DHCP on all network interfaces. If there is a DHCP server in the network, it will work automatically.
If you need a static IP setup, you can use the ifcfg
boot argument. For more details, see the linuxrc documentation at
https://en.opensuse.org/Linuxrc.
The installer self-update is executed before the language selection step. This means that progress and errors which happen during this process are displayed in English by default.
To use another language for this part of the installer, use the
language
boot parameter if available for your
architecture, for example, language=de_DE
. On machines
equipped with a traditional BIOS, alternatively, press F2
in the boot menu and select the language from the list.
Although this feature was designed to run without user intervention, it is worth knowing how it works. If you are not interested, you can jump directly to Section 4.3, “ Language, Keyboard, and Product Selection ” and skip the rest of this section.
The process can be broken down into two different parts:
Determine the update repository location.
Download and apply the updates to the installation system.
Installer Self-Updates are distributed as regular RPM packages via a dedicated repository, so the first step is to find out the repository URL.
No matter which of the following options you use, only the installer self-update repository URL is expected, for example:
self_update=https://www.example.com/my_installer_updates/
Do not supply any other repository URL—for example the URL of the software update repository.
YaST will try the following sources of information:
The self_update
boot parameter. (For more details,
see Section 3.4.6, “Enabling the Installer Self-Update”.) If you
specify a URL, it will take precedence over any other method.
The /general/self_update_url
profile element in case
you are using AutoYaST.
A registration server. YaST will query the registration server for the URL. The server to be used is determined in the following order:
By evaluating the regurl
boot
parameter (Section 3.4.1, “Providing Data to Access an RMT Server”).
By evaluating the /suse_register/reg_server
profile
element if you are using AutoYaST.
By performing an SLP lookup. If an SLP server is found, YaST will ask you whether it should be used because there is no authentication involved and everybody on the local network could announce a registration server.
By querying the SUSE Customer Center.
If none of the previous attempts worked, the fallback URL (defined in the installation media) will be used.
When the updates repository is determined, YaST will check whether an update is available. If so, all the updates will be downloaded and applied to the installation system.
Finally, YaST will be restarted to load the new version and the welcome screen will be shown. If no updates were available, the installation will continue without restarting YaST.
Update signatures will be checked to ensure integrity and authorship. If a signature is missing or invalid, you will be asked whether you want to apply the update.
Some packages distributed in the self-update repository provide additional data for the installer, like the installation defaults, system role definitions and similar. If the installer finds such packages in the self-update repository, a local temporary repository is created, to which those packages are copied. They are used during the installation process, but at the end of the installation, the temporary local repository is removed. Its packages are not installed onto the target system.
This additional repository is not displayed in the list of add-on
products, but during installation it may still be visible as
SelfUpdate0
repository in the package management.
YaST can use a user-defined repository instead of the official one by
specifying a URL through the self_update
boot parameter.
However, the following points should be considered:
Only HTTP/HTTPS and FTP repositories are supported.
Only RPM-MD repositories are supported (required by RMT).
Packages are not installed in the usual way: They are uncompressed only and no scripts are executed.
No dependency checks are performed. Packages are installed in alphabetical order.
Files from the packages override the files from the original installation media. This means that the update packages might not need to contain all files, only files that have changed. Unchanged files are omitted to save memory and download bandwidth.
Currently, it is not possible to use more than one repository as source for installer self-updates.
The
and settings are initialized with the language you chose on the boot screen. If you did not change the default, it will be English (US). Change the settings here, if necessary.Changing the language will automatically preselect a corresponding keyboard layout. Override this proposal by selecting a different keyboard layout from the drop-down box. Use the Chapter 20, Changing Language and Country Settings with YaST.
text box to test the layout. The language selected here is also used to assume a time zone for the system clock. This setting can be modified later in the installed system as described inWith the Unified Installer you can install all SUSE Linux Enterprise base products:
SUSE Linux Enterprise Server 15 SP1 (refer to https://documentation.suse.com/sles/ for installation instructions)
SUSE Linux Enterprise Desktop 15 SP1 (covered here)
SUSE Linux Enterprise High Performance Computing 15 SP1
SUSE Linux Enterprise Real Time 15 SP1 (refer to https://documentation.suse.com/sle-rt/ for installation instructions)
SUSE Linux Enterprise Server for SAP Applications 15 SP1 (refer to https://documentation.suse.com/sles-sap/ for installation instructions)
SUSE Manager Server 4.0 (refer to https://documentation.suse.com/suma/4.0/ for installation instructions)
SUSE Manager Proxy 4.0 (refer to https://documentation.suse.com/suma/4.0/ for installation instructions)
SUSE Manager Retail Branch Server 4.0 (refer to https://documentation.suse.com/suma-retail/4.0/ for installation instructions)
Select a product for installation. You need to have a registration code for the respective product. In this document it is assumed you have chosen SUSE Linux Enterprise Desktop. Proceed with .
If you have difficulties to read the labels in the installer, press Shift–F4 to switch to the color scheme for vision impaired users. Press the buttons again to switch back to the default scheme.
Read the License Agreement. It is presented in the language you have chosen on the boot screen. Translations are available via the If you agree to the terms, check SUSE Linux Enterprise Desktop; click to terminate the installation. and click to proceed with the installation. If you do not agree to the license agreement, you cannot install
drop-down box.After booting into the installation, the installation routine is set up. During this setup, an attempt to configure at least one network interface with DHCP is made. In case this attempt has failed, the
dialog launches now.Choose a network interface from the list and click Book “Administration Guide”, Chapter 19 “Basic Networking”, Section 19.4 “Configuring a Network Connection with YaST” for more details.
to change its settings. Use the tabs to configure DNS and routing. SeeIn case DHCP was successfully configured during installation setup, you can also access this dialog by clicking the and step. It lets you change the automatically provided settings.
at theIf at least one network interface has been configured via boot parameters (see Section 3.3.2, “Configuring the Network Interface”), automatic DHCP configuration is disabled and the boot parameter configuration is imported and used.
To access a SAN or a local RAID during the installation, you can use the libstorage command line client for this purpose:
Switch to a console with Ctrl–Alt–F2.
Install the libstoragemgmt extension by running extend
libstoragemgmt
.
Now you have access to the lsmcli
command. For more
information, run lsmcli --help
.
To return to the installer, press Alt–F7
Supported are Netapp Ontap, all SMI-S compatible SAN providers, and LSI MegaRAID.
To get technical support and product updates, you need to register and activate your product with the SUSE Customer Center or a local registration server. Registering SUSE Linux Enterprise Desktop at this stage also grants you immediate access to the update repository. This enables you to install the system with the latest updates and patches available.
When registering, repositories and dependencies for the modules and extensions, which you may install with the next step, are loaded from the registration server.
From this dialog, you can switch to the YaST Book “Administration Guide”, Chapter 19 “Basic Networking”, Section 19.4 “Configuring a Network Connection with YaST”.
module by clicking . For details, seeIf you are offline or want to skip registration, activate Section 4.6.3, “Installing without Registration” for instructions.
. SeeTo register with the SUSE Customer Center, enter your SUSE Linux Enterprise Desktop. If your organization provides a local registration server, you may alternatively register there. Activate and either choose a URL from the drop-down box or type in an address. Start the registration process with .
forDepending on your hardware, additional repositories containing hardware drivers may be added during the registration. If so, you will be asked to
each of these repositories.After SUSE Linux Enterprise Desktop has been successfully registered, you are asked whether to install the latest available online updates during the installation. If choosing , the system will be installed with the most current packages without having to apply the updates after installation. Activating this option is recommended.
If the system was successfully registered during installation, YaST will disable repositories from local installation media such as CD/DVD or flash disks when the installation has been completed. This prevents problems if the installation source is no longer available and ensures that you always get the latest updates from the online repositories.
To make the registration more convenient, you can also store your registration codes on a USB storage device such as a flash disk. YaST will automatically pre-fill the corresponding text box. This is particularly useful when testing the installation or if you need to register many systems or extensions.
Create a file named regcodes.txt
or
regcodes.xml
on the USB disk. If both are present, the
XML takes precedence.
In that file, identify the product with the name returned by
zypper search --type product
and assign it a
registration code as follows:
regcodes.txt
#SLES cc36aae1 SLED 309105d4 sle-we 5eedd26a sle-live-patching 8c541494
regcodes.xml
#<?xml version="1.0"?>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<suse_register>
<addons config:type="list">
<addon>
<name>SLES</name>
<reg_code>cc36aae1</reg_code>
</addon>
<addon>
<name>SLED</name>
<reg_code>309105d4</reg_code>
</addon>
<addon>
<name>sle-we</name>
<reg_code>5eedd26a</reg_code>
</addon>
<addon>
<name>sle-live-patching</name>
<reg_code>8c541494</reg_code>
</addon>
</addons>
</suse_register>
</profile>
Note that SLES
and SLED
are not
extensions, but listing them as add-ons allows for combining several base
product registration codes in a single file.
Currently flash disks are only scanned during installation or upgrade, but not when registering a running system.
To install the system without registration activate
. Accept the warning with and proceed with . The installation follows the same workflow as when registering, only the step for choosing the modules and extensions differs.Your system and extensions need to be registered to retrieve updates and to be eligible for support. If you do not register during the installation, you can do so at any time later from the running system. To do so, run
› .If you perform an installation without connecting to a registration server, you cannot register your system during the installation. Therefore you cannot receive the repository configuration for modules and extensions from the registration server. To enable a regular installation, SUSE offers a second installation medium, the SLE-15-SP1-Packages-ARCH-GM-DVD1.iso image.
To perform the installation without registration, make sure the contents of the SLE-15-SP1-Packages-ARCH-GM-DVD1.iso image can be accessed during the installation. This can be achieved by copying it to a local hard disk or a removable flash disk or by making it available in the local network. Choose a method that is supported by your hardware.
Use the following command to copy the contents of the installation image to a removable flash disk.
tux >
sudo
dd if=IMAGE of=FLASH_DISK bs=4M && sync
IMAGE needs to be replaced with the path to the
SLE-15-SP1-Installer-DVD-ARCH-GM-DVD1.iso
or SLE-15-SP1-Packages-ARCH-GM-DVD1.iso
image file. FLASH_DISK needs to be replaced
with the flash device. To identify the device, insert it and run:
root #
grep -Ff <(hwinfo --disk --short) <(hwinfo --usb --short)
disk:
/dev/sdc General USB Flash Disk
Make sure the size of the device is sufficient for the desired image. You can check the size of the device with:
root #
fdisk -l /dev/sdc | grep -e "^/dev"
/dev/sdc1 * 2048 31490047 31488000 15G 83 Linux
In this example, the device has a capacity of 15 GB. The command to use for
the SLE-15-SP1-Packages-ARCH-GM-DVD1.iso
would be:
dd if=SLE-15-SP1-Packages-ARCH-GM-DVD1.iso of=/dev/sdc bs=4M && sync
The device must not be mounted when running the dd
command. Note that all data on the partition will be erased!
In this dialog the installer lists modules and extensions that are available for SUSE Linux Enterprise Desktop. Modules are components which allow you to shape the product according to your needs. They are free of charge. Extensions add functionality to your product. They are offered as subscriptions and require a registration key that is liable for costs.
The availability of certain modules or extensions depends on the product you chose in the first step of this installation. For a description of the modules and their lifecycles, select a module to see the accompanying text. More detailed information is available in the Release Notes.
The selection of modules indirectly affects the scope of the installation, because it defines which software sources (repositories) are available for installation and in the running system.
The way you select modules and extensions depends on whether you registered your system in the previous step:
The following modules and extensions are available for SUSE Linux Enterprise Desktop:
This module adds a basic system on top of the Unified Installer. It is required by all other modules and extensions. The scope of an installation that only contains the base system is comparable to the installation pattern minimal system of previous SUSE Linux Enterprise Desktop versions. This module is selected for installation by default and should not be deselected.
Dependencies: None
Adds a graphical user interface and essential desktop applications to the system. This module is selected for installation by default; deselecting it is not recommended.
Dependencies: Basesystem
Contains compilers (including gcc) and libraries required for compiling and debugging applications. Replaces the former Software Development Kit (SDK).
Dependencies: Basesystem, Desktop Applications
SUSE Linux Enterprise 15 SP1 uses Python version 3. This module contains the Python 2 runtime and modules. It is selected for installation by default; deselecting it is not recommended.
Dependencies: Basesystem
Contains additional desktop tools such as an office suite or multimedia software such as music and video players. This extension is included in the SUSE Linux Enterprise Desktop subscription and is selected for installation by default; deselecting it is not recommended.
Dependencies: Basesystem, Desktop Applications
Provides access to packages for SUSE Linux Enterprise Desktop maintained by the openSUSE community. These packages are delivered without L3 support and do not interfere with the supportability of SUSE Linux Enterprise Desktop. For more information refer to https://packagehub.suse.com/.
Dependencies: Basesystem
Some modules depend on the installation of other modules. Therefore, when selecting a module, other modules may be selected automatically to fulfill dependencies.
Depending on the product, the registration server can mark modules and extensions as recommended. Recommended modules and extensions are preselected for registration and installation. To avoid installing these recommendations, deselect them manually.
Select the modules and extension you would like to install and proceed with
. In case you have chosen one or more extensions, you will be prompted to provide the respective registration codes. Depending on your choice, it may also be necessary to accept additional license agreements.If you have skipped the registration you need to access the SLE-15-SP1-Packages-ARCH-GM-DVD1.iso ISO image via the
dialog:On the
dialog, activate and specify the source for the SLE-15-SP1-Packages-ARCH-GM-DVD1.iso image. Check to download the files describing the repository now. If deactivated, they will be downloaded after the installation starts. Proceed with . If you chose as the data source, you will be prompted to insert the media.On the
you need to select a product, at least one module, and optionally, one or more extensions.The SLE-15-SP1-Packages-ARCH-GM-DVD1.iso images contain extensions and modules for all SUSE Linux Enterprise products. Make sure to only select modules and extensions listed below, otherwise you will end up with a system that may fail to install and is not covered by SUSE support.
Selecting a product is mandatory. Choose
.Modules extend the functionality of SUSE Linux Enterprise Desktop and are free of charge. Installing the is required. It is also recommended to install the .
Note that most modules depend on other modules. These dependencies cannot be resolved automatically here. Make sure to manually solve the dependencies, otherwise the installation will fail later on. Refer to the following list for details.
This module adds a basic system on top of the Unified Installer. It is required by all other modules and extensions. The scope of an installation that only contains the base system is comparable to the installation pattern minimal system of previous . SUSE Linux Enterprise Desktop versions. Dependencies: None
Adds a graphical user interface and essential desktop applications to the system. . Dependencies: Basesystem
Contains compilers (including . gcc) and libraries required for compiling and debugging applications.
SUSE Linux Enterprise 15SP 1 uses Python version 3. This module contains the Python 2 runtime and modules. . Dependencies: Basesystem
Contains additional desktop tools such as an office suite or multimedia software such as music and video players. The SUSE Linux Enterprise Workstation Extension for SUSE Linux Enterprise Desktop is free of charge and does not require an additional registration code. Installing
is recommended.Do not install any of the following selections on SUSE Linux Enterprise Desktop, otherwise you will end up with a system that may fail to install and is not covered by SUSE support.
When you have finished selecting modules and extensions, proceed with
.All modules selected for installation are listed on the Section 4.8, “Add-On Product” for details.
dialog. To change the list, use the or options. Using you may optionally add other add-on products from different sources. Refer toTo proceed with the installation, choose Section 4.9, “System Role”.
. Skip the following chapter and continue reading atThe “repositories”) to SUSE Linux Enterprise Desktop, that are not provided by the SUSE Customer Center. Such add-on products may include third-party products and drivers or additional software for your system.
dialog allows you to add additional software sources (so-calledFrom this dialog, you can switch to the YaST Book “Administration Guide”, Chapter 19 “Basic Networking”, Section 19.4 “Configuring a Network Connection with YaST”.
module by clicking . For details, seeYou can also add driver update repositories via the http://drivers.suse.com/. These drivers have been created via the SUSE SolidDriver Program.
dialog. Driver updates for SUSE Linux Enterprise are provided atIf you do not want to install add-ons, proceed with
. Otherwise activate . Specify the Media Type by choosing from CD, DVD, Hard Disk, USB Mass Storage, a Local Directory or a Local ISO Image. If network access has been configured you can choose from additional remote sources such as HTTP, SLP, FTP, etc. Alternatively you may directly specify a URL. Check to download the files describing the repository now. If deactivated, they will be downloaded after the installation starts. Proceed with and insert a CD or DVD if required.Depending on the add-on's content, it may be necessary to accept additional license agreements.
SUSE Linux Enterprise Desktop supports a broad range of features. To simplify the installation, the installer offers predefined use cases which adjust the system to be installed so it is tailored for the selected scenario.
Choose the
that meets your requirements best. The availability of system roles depends on your selection of modules and extensions. Therefore, the dialog is omitted under the following conditions:If from the enabled modules no role is suitable for the respective base product. In this case, the installation proceeds with the default settings for this product.
If from the enabled modules only one role is suitable for the respective base product. In this case, the installation proceeds with the settings of this particular role.
With the default selection, the following system roles are available:
Installs a fully featured GNOME desktop environment, including office suite, e-mail client, Web browser, and file manager. It is optimized for installation on physical systems, using the Wayland technology. Does not support accessing the desktop from a remote machine.
Dependencies: Basesystem, Desktop Applications, SUSE Linux Enterprise Workstation Extension
Installs a fully featured GNOME desktop environment, including office suite, e-mail client, Web browser, and file manager. Comes with support for accessing the desktop from a remote machine.
Dependencies: Basesystem, Desktop Applications, SUSE Linux Enterprise Workstation Extension
Installs a GNOME desktop environment with only essential graphical applications (for example file manager, Web browser). It is using the X11 technology.
Dependencies: Basesystem, Desktop Applications
Installs a lightweight IceWM desktop environment with only a bare minimum of graphical applications (for example xterm). It is using the X11 technology.
Dependencies: Basesystem
Read this section carefully before continuing with Section 4.10.2, “Suggested Partitioning”.
A UEFI machine requires an EFI system partition
that must be mounted to /boot/efi
. This partition
must be formatted with the FAT32
file system.
If an EFI system partition is already present on your system (for
example from a previous Windows installation) use it by mounting it to
/boot/efi
without formatting it.
If no EFI system partition is present on your UEFI machine, make sure to create it. The EFI system partition must be a physical partition or RAID 1. Other RAID levels, LVM and other technologies are not supported. It needs to be formatted with the FAT32 file system.
SUSE Linux Enterprise Desktop can be configured to use snapshots which provide the ability to do rollbacks of system changes.
SUSE Linux Enterprise Desktop uses Snapper together with Btrfs for this feature. Btrfs needs to be set up with snapshots enabled for the root partition.
If the disk is smaller than 16 GB, all Snapper features and
automatic snapshots are disabled to prevent the system partition
/
from running out of space.
Being able to create system snapshots that enable rollbacks
requires important system directories to be mounted on a
single partition, for example /usr
and
/var
. Only directories that are excluded
from snapshots may reside on separate partitions, for example
/usr/local
, /var/log
,
and /tmp
.
For details, see Book “Administration Guide”, Chapter 7 “System Recovery and Snapshot Management with Snapper”.
Snapshots occupy space on their partition. As a rule of thumb, the older a snapshot is, or the bigger the changeset they cover is, the bigger the snapshot. Plus, the more snapshots you keep, the more diskspace you need.
To prevent the root partition running full with snapshot data, you need to make sure it is big enough. In case you do frequent updates or other installations, consider at least 30 GB for the root partition. If you plan to keep snapshots activated for a system upgrade or a service pack migration (to be able to roll back), you should consider 40 GB or more.
Using Btrfs for data volumes is supported on SUSE Linux Enterprise Desktop 15 SP1. For applications that require Btrfs as a data volume, consider creating a separate file system with quota groups disabled. This is already the default for non-root file systems.
The default partitioning setup suggests the root partition as Btrfs. To encrypt the root partition, make sure to use the GPT partition table type instead of the MSDOS type. Otherwise the GRUB2 boot loader may not have enough space for the second stage loader.
Installing to and booting from existing software RAID volumes is supported for Disk Data Format (DDF) volumes and Intel Matrix Storage Manager (IMSM) volumes. IMSM is also known by the following names:
Intel Rapid Storage Technology
Intel Matrix Storage Technology
Intel Application Accelerator / Intel Application Accelerator RAID Edition
Intel Virtual RAID on CPU (Intel VROC, see https://www.intel.com/content/www/us/en/support/articles/000024498/memory-and-storage/ssd-software.html for more details)
FCoE and iSCSI devices will appear asynchronously during the
boot process. While the initrd guarantees that those devices are
set up correctly for the root file system, there are no such
guarantees for any other file systems or mount points like
/usr
. Hence any system mount points like
/usr
or /var
are not
supported. To use those devices, ensure correct
synchronization of the respective services and devices.
In case the disk selected for the suggested partitioning proposal contains a large Windows FAT or NTFS partition, it will automatically be resized to make room for the SUSE Linux Enterprise Desktop installation. To avoid data loss it is strongly recommended to
make sure the partition is not fragmented (run a defragmentation program from Windows prior to the SUSE Linux Enterprise Desktop installation)
double-check the suggested size for the Windows partition is big enough
back up your data prior to the SUSE Linux Enterprise Desktop installation
To adjust the proposed size of the Windows partition, use the
.Define a partition setup for SUSE Linux Enterprise Desktop in this step.
The installer creates a proposal for one of the available disks containing a root partition formatted with Btrfs and a swap partition. If one or more swap partitions have been detected on the available hard disks, these partitions will be used. You have several options to proceed:
To accept the proposal without any changes, click
to proceed with the installation workflow.To adjust the proposal, choose
. First, choose which hard disks and partitions to use. In the screen, you can enable Logical Volume Management (LVM) and activate disk encryption. Afterwards specify the . You can adjust the file system for the root partition and create a separate home and swap partitions. If you plan to suspend your machine, make sure to create a separate swap partition and check . If the root file system format is Btrfs, you can also enable or disable Btrfs snapshots here.To create a custom partition setup click
. Select either if you want start with the suggested disk layout, or to ignore the suggested layout and start with the existing layout on the disk. You can , , , or partitions.You can also set up Logical Volumes (LVM), configure software RAID and device mapping (DM), encrypt Partitions, mount NFS shares and manage tmpfs volumes with the Expert Partitioner. To fine-tune settings such as the subvolume and snapshot handling for each Btrfs partition, choose Section 6.1, “Using the Expert Partitioner”.
. For more information about custom partitioning and configuring advanced features, refer toIn this dialog, select your region and time zone. Both are preselected according to the installation language.
To change the preselected values, either use the map or the drop-down boxes for
and . When using the map, point the cursor at the rough direction of your region and left-click to zoom. Now choose your country or region by left-clicking. Right-click to return to the world map.To set up the clock, choose whether the
. If you run another operating system on your machine, such as Microsoft Windows, it is likely your system uses local time instead. If you run Linux on your machine, set the hardware clock to UTC and have the switch from standard time to daylight saving time performed automatically.The switch from standard time to daylight saving time (and vice versa) can only be performed automatically when the hardware clock (CMOS clock) is set to UTC. This also applies if you use automatic time synchronization with NTP, because automatic synchronization will only be performed if the time difference between the hardware and system clock is less than 15 minutes.
Since a wrong system time can cause serious problems (missed backups, dropped mail messages, mount failures on remote file systems, etc.), it is strongly recommended to always set the hardware clock to UTC.
If a network is already configured, you can configure time synchronization with an NTP server. Click Book “Administration Guide”, Chapter 31 “Time Synchronization with NTP” for more information on configuring the NTP service. When finished, click to continue the installation.
to either alter the NTP settings or to set the time. See
If running without NTP configured, consider setting
SYSTOHC=no
(sysconfig
variable) to
avoid saving unsynchronized time into the hardware clock.
Create a local user in this step.
After entering the first name and last name, either accept the proposal or
specify a new .
(dot), -
(hyphen) and
_
(underscore). Special characters, umlauts and accented
characters are not allowed.
Finally, enter a password for the user. Re-enter it for confirmation (to ensure that you did not type something else by mistake). To provide effective security, a password should be at least six characters long and consist of uppercase and lowercase letters, numbers and special characters (7-bit ASCII). Umlauts or accented characters are not allowed. Passwords you enter are checked for weakness. When entering a password that is easy to guess (such as a dictionary word or a name) you will see a warning. It is a good security practice to use strong passwords.
Remember both your user name and the password because they are needed each time you log in to the system.
If you install SUSE Linux Enterprise Desktop on a machine with one or more existing Linux installations, YaST allows you to import user data such as user names and passwords. Select and then for import.
If you do not want to configure any local users (for example when setting up a client on a network with centralized user authentication), skip this step by choosing Chapter 19, Managing Users with YaST for instructions.
and confirming the warning. Network user authentication can be configured at any time later in the installed system; refer toTwo additional options are available:
If checked, the same password you have entered for the user will be used
for the system administrator root
. This option is suitable for
stand-alone workstations or machines in a home network that are
administrated by a single user. When not checked, you are prompted for a
system administrator password in the next step of the installation
workflow (see Section 4.13, “Authentication for the System Administrator “root””).
This option automatically logs the current user in to the system when it starts. This is mainly useful if the computer is operated by only one user.
With the automatic login enabled, the system boots straight into your desktop with no authentication. If you store sensitive data on your system, you should not enable this option if the computer can also be accessed by others.
In an environment where users are centrally managed (for example by NIS or LDAP) you may want to skip the creation of local users. Select
in this case.
If you have not chosen root
or provide a public SSH
key. Otherwise this configuration step is skipped.
root
#
root
is the name of the superuser, or the administrator of the system.
Unlike regular users, root
has unlimited
rights to change the system configuration, install programs, and set up new
hardware. If users forget their passwords or have other problems with the
system, root
can help. The root
account should only be used for
system administration, maintenance, and repair. Logging in as root
for
daily work is rather risky: a single mistake could lead to irretrievable
loss of system files.
For verification purposes, the password for root
must be entered
twice. Do not forget the root
password. After having been entered,
this password cannot be retrieved.
It is recommended to only use US ASCII characters. In case of a system error or when you need to start your system in rescue mode, the keyboard may not be localized.
The root
password can be changed any time later in the installed
system. To do so run YaST and start › .
root
User
The user root
has all the permissions needed to make changes to the
system. To carry out such tasks, the root
password is required. You
cannot carry out any administrative tasks without this password.
In some situations it is preferred to access the system remotely via SSH using a public key. This screen allows you to select a public key from a medium.
The following procedure describes how to add a public SSH key from a USB stick. It works the same way with CD/DVD-ROM or from an existing partition. Proceed as follows:
root
#
Insert into your computer the USB storage device containing the public SSH key.
The public SSH key has the file extension .pub
.
Click
. You should see the device in the list selector under .Click
and select the public SSH key.Proceed with
.In the
summary, make sure to check under the SSH port. Click so it reads .After the installation is finished, you can log in through SSH using the provided public SSH key.
On the last step before the real installation takes place, you can alter installation settings suggested by the installer. To modify the suggestions, click the respective headline. After having made changes to a particular setting, you are always returned to the Installation Settings window, which is updated accordingly.
If you have added an SSH key for your root
as mentioned in Procedure 4.1,
make sure to open the SSH port in the
settings.
SUSE Linux Enterprise Desktop contains several software patterns for various application purposes. The available choice of patterns and packages depends on your selection of modules and extensions.
Click
to open the screen where you can modify the pattern selection according to your needs. Select a pattern from the list and see a description in the right-hand part of the window.Each pattern contains several software packages needed for specific functions (for example Multimedia or Office software). For a more detailed selection based on software packages to install, select to switch to the YaST Software Manager.
You can also install additional software packages or remove software packages from your system at any later time with the YaST Software Manager. For more information, refer to Chapter 16, Installing or Removing Software.
By default, SUSE Linux Enterprise Desktop uses the Wayland display server protocol.
The language you selected with the first step of the installation will be used as the primary (default) language for the system. You can add secondary languages from within the
dialog by choosing › › .The installer proposes a boot configuration for your system. Other operating systems found on your computer, such as Microsoft Windows or other Linux installations, will automatically be detected and added to the boot loader. However, SUSE Linux Enterprise Desktop will be booted by default. Normally, you can leave these settings unchanged. If you need a custom setup, modify the proposal according to your needs. For information, see Book “Administration Guide”, Chapter 14 “The Boot Loader GRUB 2”, Section 14.3 “Configuring the Boot Loader with YaST”.
Booting a configuration where /boot
resides on a
software RAID 1 device is supported, but it requires to install the boot
loader into the MBR ( › ). Having
/boot
on software RAID devices with a level other
than RAID 1 is not supported.
The
refer to kernel boot command line parameters for software mitigations that have been deployed to prevent CPU side-channel attacks. Click the highlighted entry to choose a different option.
By default firewalld
is enabled on all configured network interfaces.
To globally disable the firewall for this computer, click
(not recommended).
If the firewall is activated, all interfaces are configured to be in the “External Zone”, where all ports are closed by default, ensuring maximum security. The only port you can open during the installation is port 22 (SSH), to allow remote access. All other services requiring network access (such as FTP, Samba, Web server, etc.) will only work after having adjusted the firewall settings. Refer to Book “Security and Hardening Guide”, Chapter 23 “Masquerading and Firewalls” for more information.
To enable remote access via the secure shell (SSH), make sure the
SSH service
is enabled and the SSH
port
is open.
If you install SUSE Linux Enterprise Desktop on a machine with existing Linux installations, the installation routine imports an SSH host key. It chooses the host key with the most recent access time by default. See also Section 4.14.6, “. ”
If you are performing a remote administration over VNC, you can also specify whether the machine should be accessible via VNC after the installation. Note that enabling VNC also requires you to set the
to .This category displays the current network settings (as automatically configured after booting into the installation, see Section 4.5) or as manually configured from the or dialog during the respective steps of the installation process. If you want to check or adjust the network settings at this stage (before performing the installation), click . This takes you to the YaST module. For details, see Book “Administration Guide”, Chapter 19 “Basic Networking”, Section 19.4 “Configuring a Network Connection with YaST”.
SUSE Linux Enterprise Desktop can boot into two different targets (formerly known as “runlevels”). The target starts a display manager, whereas the target starts the command line interface.
The default target is
. In case you have not installed the patterns, you need to change it to . If the system should be accessible via VNC, you need to choose .
If an existing Linux installation on your computer was detected, YaST
will import the most recent SSH host key found in
/etc/ssh
by default, optionally including other files
in the directory as well. This makes it possible to reuse the SSH identity
of the existing installation, avoiding the REMOTE HOST
IDENTIFICATION HAS CHANGED
warning on the first connection. Note
that this item is not shown in the installation summary if YaST has not
discovered any other installations. You have the following choices:
Select this option to import the SSH host key and optionally the configuration of an installed system. You can select the installation to import from in the option list below.
Enable this to copy other files in /etc/ssh
to the
installed system in addition to the host keys.
This screen lists all the hardware information the installer could obtain about your computer. When opened for the first time, the hardware detection is started. Depending on your system, this may take some time. Select any item in the list and click
to see detailed information about the selected item. Use to save a detailed list to either the local file system or a removable device.Advanced users can also change the
and kernel settings by choosing . A screen with two tabs opens:Each kernel driver contains a list of device IDs of all devices it supports. If a new device is not in any driver's database, the device is treated as unsupported, even if it can be used with an existing driver. You can add PCI IDs to a device driver here. Only advanced users should attempt to do so.
To add an ID, click /sys/bus/pci/drivers
—if
empty, the name is used as the directory name.
Existing entries can be managed with and
.
Change the Book “System Analysis and Tuning Guide”, Chapter 12 “Tuning I/O Performance” for details on I/O tuning.
here. If is chosen, the default setting for the respective architecture will be used. This setting can also be changed at any time later from the installed system. Refer toAlso activate the https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html for details.
here. These keys will let you issue basic commands (such as rebooting the system or writing kernel dumps) in case the system crashes. Enabling these keys is recommended when doing kernel development. Refer toAfter configuring all installation settings, click
in the Installation Settings window to start the installation. Some software may require a license confirmation. If your software selection includes such software, license confirmation dialogs are displayed. Click to install the software package. When not agreeing to the license, click and the software package will not be installed. In the dialog that follows, confirm with again.The installation usually takes between 15 and 30 minutes, depending on the system performance and the selected software scope. After having prepared the hard disk and having saved and restored the user settings, the software installation starts. Choose
to switch to the installation log or to read important up-to-date information that was not available when the manuals were printed.After the software installation has completed, the system reboots into the new installation where you can log in. To customize the system configuration or to install additional software packages, start YaST.
To get technical support and product updates, you need to register and activate SUSE Linux Enterprise Desktop with the SUSE Customer Center. It is recommended to register during the installation, since this will enable you to install the system with the latest updates and patches available. However, if you are offline or want to skip the registration step, you can register at any time later from the installed system.
Modules and extensions add features to your system and allow you to customize the system according to your needs. These components also need to be registered and can be managed with YaST or command line tools. For more details also refer to the Article “Modules and Extensions Quick Start”.
Registering with the SUSE Customer Center requires a SUSE account. In case you do not have a SUSE account yet, go to the SUSE Customer Center home page (https://scc.suse.com/) to create one.
To completely deregister a system including all modules and extensions use
the command line tool SUSEConnect
. Deregistering a system
removes its entry on the registration server and also removes all
repositories for modules, extensions, and the product itself.
tux >
sudo SUSEConnect -d
The easiest and recommended way to register is to do it during the installation. It will not only allow you to install the latest patch level of SUSE Linux Enterprise Desktop, but you will also get access to all modules and extensions without having to provide an additional installation media. This also applies to all modules or extension you install. For details on the registration process refer to Section 4.6, “Registration”.
If the system was successfully registered during installation, YaST will add online repositories provided by SUSE Customer Center. This prevents problems if local installation sources are no longer available and ensures that you always get the latest updates from the online repositories.
If you have skipped the registration during the installation or want to
re-register your system, you can do so at any time using the
YaST module SUSEConnect
.
To register the system start SUSE Linux Enterprise Desktop, then choose the modules and extensions you want to make available.
› › . First registerIf you have installed the system by skipping the registration and installing from the SLE-15-SP1-Packages-ARCH-GM-DVD1.iso media, make sure to register all the modules and extension you have chosen during the installation. You will only receive security updates and patches for modules and extensions that have been registered.
Start
› › .Provide the SUSE Linux Enterprise Desktop.
associated with the SUSE account you or your organization uses to manage subscriptions. Also enter the you received with your copy ofBy default the system is registered with the SUSE Customer Center. Proceed to the next step to make this happen.
If your organization provides local registration servers you can either choose one form the list of auto-detected servers or provide the URL at
.Choose SUSE Linux Enterprise Desktop is registered with the chosen server and the associated repositories are added to your system. The dialog opens.
to start the registration process.Select all modules and extensions you would like to make available in the system. You should at least choose the preselected modules (, ). Also make sure to choose any additional module or extension that you have added during the installation. Note that all extensions require additional registration codes which are liable for cost. Proceed with and .
Depending on your selection, you may have to accept one or more license agreements now. All components are registered with the chosen server and the associated repositories are added to your system.
The YaST package installer opens to install release-packages for each module and, depending on your choice of modules and extensions, additional packages. It is strongly recommended not to deselect any of the preselected packages; you may, however, add additional packages.
Choose
and to conclude the registration process.
Registering the system plus modules and extensions is also possible from
the command line using SUSEConnect
. For information that
go beyond the scope of this section, refer to the inline documentation with
man 8 SUSEConnect
To register SUSE Linux Enterprise Desktop with SUSE Customer Center run SUSEConnect
as follows:
tux >
sudo SUSEConnect -r REGISTRATION_CODE -e EMAIL_ADDRESS
To register with a local registration server, additionally provide the URL to the server:
tux >
sudo SUSEConnect -r REGISTRATION_CODE -e EMAIL_ADDRESS \
--url "https://suse_register.example.com/"
Replace REGISTRATION_CODE with the registration code you received with your copy of SUSE Linux Enterprise Desktop. Replace EMAIL_ADDRESS with the E-mail address associated with the SUSE account you or your organization uses to manage subscriptions.
This process will register the , and add the associated repositories to your system. and
SUSE Linux Enterprise Desktop including the two default repositories is now registered. In case you want to register additional modules or extensions, proceed as outlined in Section 5.3, “Managing Modules and Extensions in a Running System”.
Even after a system is installed and registered, adding and removing modules
and extensions is still possible. You can either use YaST or
SUSEConnect
for this task. For more details also refer to
the Article “Modules and Extensions Quick Start”.
Start
› › .To add modules or extensions, select all components you would like to install. Note that all extensions require additional registration codes which are liable for cost.
All additional components are registered with the registration server and the associated repositories are added to your system.
The YaST package installer opens to install release-packages for each module and, depending on your choice of modules and extensions, additional packages. It is strongly recommended not to deselect any of the preselected packages; you may, however, add additional packages.
Choose
and to conclude the process.Similar to software packages, which may depend on other packages to function, a module may have dependencies on other modules. If this is the case, the modules on which it depends are automatically selected for installation.
Start
› › .Choose the module or extension that should be removed and click
. Confirm the warning saying that all packages from the selected component will be removed.
The YaST Software Manager opens and shows a list of all installed
packages from the deleted module or extension. Click
*-release
package for each
module or extension that gets deleted.
Proceed with
and then .Note that you should never delete the , . and
. It is also not recommended to delete theIf you choose to keep packages from deleted modules or extensions, you will no longer receive updates for these packages. Because this includes security fixes, keeping such packages may introduce a security risk to your system.
Run SUSEConnect -list-extensions
to get an overview of
available extensions:
tux >
sudo SUSEConnect -list-extensions
AVAILABLE EXTENSIONS AND MODULES
Basesystem Module 15 SP1 x86_64 (Installed)
Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64
Desktop Applications Module 15 SP1 x86_64 (Installed)
Deactivate with: SUSEConnect -d -p sle-module-desktop-applications/15.1/x86_64
Development Tools Module 15 SP1 x86_64
Activate with: SUSEConnect -p sle-module-development-tools/15.1/x86_64
SUSE Linux Enterprise Workstation Extension 15 SP1 x86_64 (Installed)
Deactivate with: SUSEConnect -d -p sle-we/15.1/x86_64
SUSE Cloud Application Platform Tools Module 15 SP1 x86_64
Activate with: SUSEConnect -p sle-module-cap-tools/15.1/x86_64
SUSE Package Hub 15 SP1 x86_64
Activate with: SUSEConnect -p PackageHub/15.1/x86_64
MORE INFORMATION
You can find more information about available modules here:
https://www.suse.com/products/server/features/modules.html
Run the commands in the listing for activating/deactivating a module or extension to add or delete a component. Note that adding an extensions requires additional registration codes which are liable for cost.
Note that you should never delete the , . and
. It is also not recommended to delete the
When using SUSEConnect
to add or delete modules and
extensions, the components get de-registered and the respective
repositories or services get removed from the system. No installation or
removal of packages will be done. If you want this to be done
automatically, use YaST to add or delete modules and extensions.
When adding a module or extension, this means no automatic installation of default packages or patterns is performed. You need to do this manually with Zypper on the command line or by running
› .
When deleting a module or extension, this means no automatic cleanup will
be done. All packages that belonged to the module or extension will remain
installed on the system, but are longer associated with a repository and
therefore will no longer receive updates. To remove these so-called
“orphaned” packages use Zypper on the command
line. zypper packages --orphaned
lists these packages
and zypper remove
deletes one or more
packages. Alternatively use
› to list and delete orphaned packages.
If you choose to keep packages from deleted modules or extensions, you will no longer receive updates for these packages. Because this includes security fixes, keeping such packages may introduce a security risk to your system.
Sophisticated system configurations require specific disk setups. You can perform all common partitioning tasks during the installation.
To get persistent device naming with block devices, use the block devices
below /dev/disk/by-id
or
/dev/disk/by-uuid
.
Logical Volume Management (LVM) is a disk partitioning scheme that is designed to be much more flexible than the physical partitioning used in standard setups. Its snapshot functionality enables easy creation of data backups. Redundant Array of Independent Disks (RAID) offers increased data integrity, performance, and fault tolerance. SUSE Linux Enterprise Desktop also supports multipath I/O . There is also the option to use iSCSI as a networked disk.
With the Expert Partitioner, shown in Figure 6.1, “The YaST Partitioner”, manually modify the partitioning of one or several hard disks. You can add, delete, resize, and edit partitions, or access the soft RAID, and LVM configuration.
Although it is possible to repartition your system while it is running, the risk of making a mistake that causes data loss is very high. Try to avoid repartitioning your installed system and always create a complete backup of your data before attempting to do so.
All existing or suggested partitions on all connected hard disks are
displayed in the list of /dev/sda
. Partitions are listed as parts of
these devices, such as
/dev/sda1
. The size, type,
encryption status, file system, and mount point of the hard disks and their
partitions are also displayed. The mount point describes where the partition
appears in the Linux file system tree.
Several functional views are available on the left hand RAID
, Volume Management
,
Crypt Files
), and view file systems with additional
features, such as Btrfs, NFS, or TMPFS
.
If you run the expert dialog during installation, any free hard disk space is also listed and automatically selected. To provide more disk space to SUSE Linux Enterprise Desktop, free the needed space by going from the bottom toward the top in the list of partitions.
SUSE Linux Enterprise Desktop allows to use and create different partition tables. In some cases the partition table is called disk label. The partition table is important to the boot process of your computer. To boot your machine from a partition in a newly created partition table, make sure that the table format is supported by the firmware.
To change the partition table, click the relevant disk name in the
and choose › .The master boot record (MBR) is the legacy partition table used on IBM PCs. It is sometimes also called an MS-DOS partition table. The MBR only supports four primary partitions. If the disk already has an MBR, SUSE Linux Enterprise Desktop allows you to create additional partitions in it which can be used as the installation target.
The limit of four partitions can be overcome by creating an extended partition. The extended partition itself is a primary partition and can contain more logical partitions.
UEFI firmwares usually support booting from MBR in the legacy mode.
UEFI computers use a GUID Partition Table (GPT) by default. SUSE Linux Enterprise Desktop will create a GPT on a disk if no other partition table exists.
Old BIOS firmwares do not support booting from GPT partitions.
You need a GPT partition table to use one of the following features:
More than four primary partitions
UEFI Secure Boot
Use disks larger than 2 TB
GPT partitions created with Parted 3.1 or earlier used the Microsoft
Basic Data partition type instead of the newer Linux-specific GPT GUID.
Newer versions of Parted will set the misleading flag
msftdata
on such partitions. This will also lead to
various disk tools labeling the partition as a Windows Data
Partition or similar.
To remove the flag, run:
root #
parted DEVICE set PARTITION_NUMBER msftdata off
The YaST Partitioner can create and format partitions with several
file systems. The default file system used by SUSE Linux Enterprise Desktop is
Btrfs
. For details, see
Section 6.1.2.2, “Btrfs Partitioning”.
Other commonly used file systems are available:
Ext2
, Ext3
,
Ext4
, FAT
,
XFS
, Swap
, and UDF
.
To create a partition select
and then a hard disk with free space. The actual modification can be done in the tab:Click MBR, specify to create a primary or extended partition. Within the extended partition, you can create several logical partitions. For details, see Section 6.1.1, “Partition Tables”.
to create a new partition. When usingSpecify the size of the new partition. You can either choose to occupy all the free unpartitioned space, or enter a custom size.
Select the file system to use and a mount point. YaST suggests a mount point for each partition created. To use a different mount method, like mount by label, select
.Specify additional file system options if your setup requires them. This is necessary, for example, if you need persistent device names. For details on the available options, refer to Section 6.1.3, “Editing a Partition”.
Click
to apply your partitioning setup and leave the partitioning module.If you created the partition during installation, you are returned to the installation overview screen.
The default file system for the root partition is Btrfs. For details, see Book “Administration Guide”, Chapter 7 “System Recovery and Snapshot Management with Snapper”. The root file system is the default subvolume and it is not listed in the list of created subvolumes. As a default Btrfs subvolume, it can be mounted as a normal file system.
The default partitioning setup suggests the root partition as
Btrfs with /boot
being a directory. To
encrypt the root partition, make sure to use the GPT partition
table type instead of the default MSDOS type. Otherwise the GRUB2
boot loader may not have enough space for the second stage loader.
It is possible to create snapshots of Btrfs subvolumes—either
manually, or automatically based on system events. For example when
making changes to the file system, zypper
invokes the snapper
command to create snapshots
before and after the change. This is useful if you are not
satisfied with the change zypper
made and want
to restore the previous state. As snapper
invoked by zypper
creates snapshots of the
root file system by default, it makes sense to
exclude specific directories from snapshots. This is the reason
YaST suggests creating the following separate subvolumes:
/boot/grub2/i386-pc
,
/boot/grub2/x86_64-efi
,
/boot/grub2/powerpc-ieee1275
,
/boot/grub2/s390x-emu
A rollback of the boot loader configuration is not supported. The directories listed above are architecture-specific. The first two directories are present on AMD64/Intel 64 machines, the latter two on IBM POWER and on IBM Z, respectively.
/home
If /home
does not reside on a separate partition, it
is excluded to avoid data loss on rollbacks.
/opt
Third-party products usually get installed to /opt
. It
is excluded to avoid uninstalling these applications on rollbacks.
/srv
Contains data for Web and FTP servers. It is excluded to avoid data loss on rollbacks.
/tmp
All directories containing temporary files and caches are excluded from snapshots.
/usr/local
This directory is used when manually installing software. It is excluded to avoid uninstalling these installations on rollbacks.
/var
This directory contains many variable files, including logs, temporary
caches, third party products in /var/opt
, and is the
default location for virtual machine images and databases. Therefore this
subvolume is created to exclude all of this variable data from snapshots
and has Copy-On-Write disabled.
Since saved snapshots require more disk space, it is recommended to
reserve enough space for Btrfs. While the minimum size for a root Btrfs
partition with snapshots and default subvolumes is 16 GB, SUSE
recommends at least 32 GB, or more if /home
does not reside on a separate partition.
Subvolumes of a Btrfs partition can be now managed with the YaST
module. You can add new or remove existing subvolumes.Choose
in the left side pane.Select the Btrfs partition whose subvolumes you need to manage.
Depending on whether you want to edit, add, or remove subvolumes, do the following:
To edit a subvolume, select it from the list and click
copy-on-write
(check
) for the volume or limit it's size.
Click to finish.
To add a new subvolume, click copy-on-write
(check
) for the volume or limit it's size.
Click to finish.
To remove a subvolume, select it from the list and click
. Confirm the deletion by clicking .Leave the partitioner with
.When you create a new partition or modify an existing partition, you can set various parameters. For new partitions, the default parameters set by YaST are usually sufficient and do not require any modification. To edit your partition setup manually, proceed as follows:
Select the partition.
Click
to edit the partition and set the parameters:Even if you do not want to format the partition at this stage, assign it a file system ID to ensure that the partition is registered correctly. Typical values are
, , , and .To change the partition file system, click
and select file system type in the list.SUSE Linux Enterprise Desktop supports several types of file systems. Btrfs is the Linux file system of choice for the root partition because of its advanced features. It supports copy-on-write functionality, creating snapshots, multi-device spanning, subvolumes, and other useful techniques. XFS, Ext3, and Ext4 are journaling file systems. These file systems can restore the system very quickly after a system crash, using write processes logged during the operation. Ext2 is not a journaling file system, but it is adequate for smaller partitions because it does not require much disk space for management.
The default file system for the root partition is Btrfs. The default file system for additional partitions is XFS.
The UDF file system can be used on optical rewritable and non-rewritable media, USB flash drives and hard drives. It is supported by multiple operating systems.
Swap is a special format that allows the partition to be used as a virtual memory. Create a swap partition of at least 256 MB. However, if you use up your swap space, consider adding memory to your system instead of adding swap space.
Changing the file system and reformatting partitions irreversibly deletes all data from the partition.
For details on the various file systems, refer to Storage Administration Guide.
If you activate the encryption, all data is written to the hard disk in encrypted form. This increases the security of sensitive data, but reduces the system speed, as the encryption takes some time to process. More information about the encryption of file systems is provided in Book “Security and Hardening Guide”, Chapter 14 “Encrypting Partitions and Files”.
Specify the directory where the partition should be mounted in the file system tree. Select from YaST suggestions or enter any other name.
Specify various parameters contained in the global file system
administration file (/etc/fstab
). The default
settings should suffice for most setups. You can, for example, change
the file system identification from the device name to a volume label.
In the volume label, use all characters except /
and
space.
To get persistent devices names, use the mount option SUSE Linux Enterprise Desktop, persistent device names are enabled by default.
, or . In
If you prefer to mount the partition by its label, you need to define
one in the HOME
for a partition
intended to mount to /home
.
If you intend to use quotas on the file system, use the mount option Section 19.3.3, “Managing Quotas”.
. This must be done before you can define quotas for users in the YaST module. For further information on how to configure user quota, refer toSelect
to save the changes.To resize an existing file system, select the partition and use
. Note, that it is not possible to resize partitions while mounted. To resize partitions, unmount the relevant partition before running the partitioner.After you select a hard disk device (like
) in the pane, you can access the menu in the lower right part of the window. The menu contains the following commands:This option helps you create a new partition table on the selected device.
Creating a new partition table on a device irreversibly removes all the partitions and their data from that device.
This option helps you clone the device partition layout (but not the data) to other available disk devices.
After you select the host name of the computer (the top-level of the tree in the
pane), you can access the menu in the lower right part of the window. The menu contains the following commands:To access SCSI over IP block devices, you first need to configure iSCSI. This results in additionally available devices in the main partition list.
Selecting this option helps you configure the multipath enhancement to the supported mass storage devices.
The following section includes a few hints and tips on partitioning that should help you make the right decisions when setting up your system.
Note, that different partitioning tools may start counting the cylinders of
a partition with 0
or with 1
. When
calculating the number of cylinders, you should always use the difference
between the last and the first cylinder number and add one.
swap
#Edit sourceSwap is used to extend the available physical memory. It is then possible to use more memory than physical RAM available. The memory management system of kernels before 2.4.10 needed swap as a safety measure. Then, if you did not have twice the size of your RAM in swap, the performance of the system suffered. These limitations no longer exist.
Linux uses a page called “Least Recently Used” (LRU) to select pages that might be moved from memory to disk. Therefore, running applications have more memory available and caching works more smoothly.
If an application tries to allocate the maximum allowed memory, problems with swap can arise. There are three major scenarios to look at:
The application gets the maximum allowed memory. All caches are freed, and thus all other running applications are slowed. After a few minutes, the kernel's out-of-memory kill mechanism activates and kills the process.
At first, the system slows like a system without swap. After all physical RAM has been allocated, swap space is used as well. At this point, the system becomes very slow and it becomes impossible to run commands from remote. Depending on the speed of the hard disks that run the swap space, the system stays in this condition for about 10 to 15 minutes until the out-of-memory kill mechanism resolves the issue. Note that you will need a certain amount of swap if the computer needs to perform a “suspend to disk”. In that case, the swap size should be large enough to contain the necessary data from memory (512 MB–1GB).
It is better to not have an application that is out of control and swapping excessively in this case. If you use such application, the system will need many hours to recover. In the process, it is likely that other processes get timeouts and faults, leaving the system in an undefined state, even after terminating the faulty process. In this case, do a hard machine reboot and try to get it running again. Lots of swap is only useful if you have an application that relies on this feature. Such applications (like databases or graphics manipulation programs) often have an option to directly use hard disk space for their needs. It is advisable to use this option instead of using lots of swap space.
If your system is not out of control, but needs more swap after some time, it is possible to extend the swap space online. If you prepared a partition for swap space, add this partition with YaST. If you do not have a partition available, you can also use a swap file to extend the swap. Swap files are generally slower than partitions, but compared to physical RAM, both are extremely slow so the actual difference is negligible.
To add a swap file in the running system, proceed as follows:
Create an empty file in your system. For example, to add a
swap file with 128 MB swap at
/var/lib/swap/swapfile
, use the commands:
tux >
sudo
mkdir -p /var/lib/swaptux >
sudo
dd if=/dev/zero of=/var/lib/swap/swapfile bs=1M count=128
Initialize this swap file with the command
tux >
sudo
mkswap /var/lib/swap/swapfile
mkswap
Do not reformat existing swap partitions with mkswap
if possible. Reformatting with mkswap
will change
the UUID value of the swap partition. Either reformat via YaST (which
will update /etc/fstab
) or adjust
/etc/fstab
manually.
Activate the swap with the command
tux >
sudo
swapon /var/lib/swap/swapfile
To disable this swap file, use the command
tux >
sudo
swapoff /var/lib/swap/swapfile
Check the current available swap spaces with the command
tux >
cat /proc/swaps
Note that at this point, it is only temporary swap space. After the next reboot, it is no longer used.
To enable this swap file permanently, add the following line to
/etc/fstab
:
/var/lib/swap/swapfile swap swap defaults 0 0
From the
, access the LVM configuration by clicking the item in the pane. However, if a working LVM configuration already exists on your system, it is automatically activated upon entering the initial LVM configuration of a session. In this case, all disks containing a partition (belonging to an activated volume group) cannot be repartitioned. The Linux kernel cannot reread the modified partition table of a hard disk when any partition on this disk is in use. If you already have a working LVM configuration on your system, physical repartitioning should not be necessary. Instead, change the configuration of the logical volumes.
At the beginning of the physical volumes (PVs), information about the volume
is written to the partition. To reuse such a partition for other non-LVM
purposes, it is advisable to delete the beginning of this volume. For
example, in the VG system
and PV
/dev/sda2
, do this with the command:
dd
if=/dev/zero of=/dev/sda2 bs=512 count=1
The file system used for booting (the root file system or
/boot
) must not be stored on an LVM logical volume.
Instead, store it on a normal physical partition.
This section explains specific steps to take when configuring LVM.
Using LVM is sometimes associated with increased risk such as data loss. Risks also include application crashes, power failures, and faulty commands. Save your data before implementing LVM or reconfiguring volumes. Never work without a backup.
The YaST LVM configuration can be reached from the YaST Expert Partitioner (see Section 6.1, “Using the Expert Partitioner”) within the item in the pane. The Expert Partitioner allows you to edit and delete existing partitions and create new ones that need to be used with LVM.
The first task is to create physical volumes that provide space to a volume group:
Select a hard disk from
.Change to the
tab.Click
and enter the desired size of the PV on this disk.Use
and change the to . Do not mount this partition.Repeat this procedure until you have defined all the desired physical volumes on the available disks.
If no volume group exists on your system, you must add one (see Figure 6.3, “Creating a Volume Group”). It is possible to create additional groups by clicking in the pane, and then on . One single volume group is usually sufficient.
Enter a name for the VG, for example, system
.
Select the desired
. This value defines the size of a physical block in the volume group. All the disk space in a volume group is handled in blocks of this size.Add the prepared PVs to the VG by selecting the device and clicking Ctrl while selecting the devices.
. Selecting several devices is possible by holdingSelect
to make the VG available to further configuration steps.If you have multiple volume groups defined and want to add or remove PVs, select the volume group in the
list and click . In the following window, you can add or remove PVs to the selected volume group.After the volume group has been filled with PVs, define the LVs which the operating system should use in the next dialog. Choose the current volume group and change to the
tab. , , , and LVs as needed until all space in the volume group has been occupied. Assign at least one LV to each volume group.Click
and go through the wizard-like pop-up that opens:
Enter the name of the LV. For a partition that should be mounted to
/home
, a name like HOME
could be
used.
Select the type of the LV. It can be either
, , or . Note that you need to create a thin pool first, which can store individual thin volumes. The big advantage of thin provisioning is that the total sum of all thin volumes stored in a thin pool can exceed the size of the pool itself.Select the size and the number of stripes of the LV. If you have only one PV, selecting more than one stripe is not useful.
Choose the file system to use on the LV and the mount point.
By using stripes it is possible to distribute the data stream in the LV among several PVs (striping). However, striping a volume can only be done over different PVs, each providing at least the amount of space of the volume. The maximum number of stripes equals to the number of PVs, where Stripe "1" means "no striping". Striping only makes sense with PVs on different hard disks, otherwise performance will decrease.
YaST cannot, at this point, verify the correctness of your entries concerning striping. Any mistake made here is apparent only later when the LVM is implemented on disk.
If you have already configured LVM on your system, the existing logical volumes can also be used. Before continuing, assign appropriate mount points to these LVs. With
, return to the YaST Expert Partitioner and finish your work there.This section describes actions required to create and configure various types of RAID. .
The YaST Section 6.1, “Using the Expert Partitioner”. This partitioning tool enables you to edit and delete existing partitions and create new ones to be used with soft RAID:
configuration can be reached from the YaST Expert Partitioner, described inSelect a hard disk from
.Change to the
tab.Click
and enter the desired size of the raid partition on this disk.Use
and change the to . Do not mount this partition.Repeat this procedure until you have defined all the desired physical volumes on the available disks.
For RAID 0 and RAID 1, at least two partitions are needed—for RAID 1, usually exactly two and no more. If RAID 5 is used, at least three partitions are required, RAID 6 and RAID 10 require at least four partitions. It is recommended to use partitions of the same size only. The RAID partitions should be located on different hard disks to decrease the risk of losing data if one is defective (RAID 1 and 5) and to optimize the performance of RAID 0. After creating all the partitions to use with RAID, click
› to start the RAID configuration.In the next dialog, choose between RAID levels 0, 1, 5, 6 and 10. Then, select all partitions with either the “Linux RAID” or “Linux native” type that should be used by the RAID system. No swap or DOS partitions are shown.
For RAID types where the order of added disks matters, you can mark individual disks with one of the letters A to E. Click the
button, select the disk and click of the buttons, where X is the letter you want to assign to the disk. Assign all available RAID disks this way, and confirm with . You can easily sort the classified disks with the or buttons, or add a sort pattern from a text file with .To add a previously unassigned partition to the selected RAID volume, first click the partition then
. Assign all partitions reserved for RAID. Otherwise, the space on the partition remains unused. After assigning all partitions, click to select the available .
In this last step, set the file system to use, encryption and the mount
point for the RAID volume. After completing the configuration with
/dev/md0
device and
others indicated with RAID in the Expert Partitioner.
Check the file /proc/mdstat
to find out whether a RAID
partition has been damaged. If the system fails, shut down your Linux system
and replace the defective hard disk with a new one partitioned the same way.
Then restart your system and enter the command mdadm /dev/mdX --add
/dev/sdX
. Replace 'X' with your particular device identifiers.
This integrates the hard disk automatically into the RAID system and fully
reconstructs it.
Note that although you can access all data during the rebuild, you may encounter some performance issues until the RAID has been fully rebuilt.
Configuration instructions and more details for soft RAID can be found at:
Linux RAID mailing lists are available, such as http://marc.info/?l=linux-raid.
The installation of SUSE® Linux Enterprise Desktop can be fully performed over the network. This chapter describes how to provide the required environment for booting, installing and controlling the installation via the network.
For a remote installation you need to consider how to boot, how to control the installation, and the source of the installation data. All available options can be combined with each other, if they are available for your hardware platform.
Depending on the hardware, several options for booting a system exist. Common options are DVD, USB drive or PXE boot. For more information about your platform, refer to Part I, “Installation Preparation”.
To set up a server for booting via PXE, refer to Chapter 13, Preparing Network Boot Environment.
Most commonly, DVDs or USB drives are used as a source for installing
SUSE Linux Enterprise Desktop. Alternatively, installation servers can be used. In this
case, use the install
boot parameter to specify the
source. For details, refer to
Section 3.3.3, “Specifying the Installation Source”.
To use a network source for the installation, prepare a server as described in Chapter 12, Setting Up a Network Installation Source.
Instead of using a keyboard and monitor directly attached to the target machine, the installation can be controlled via SSH, VNC, or by using the serial console of a machine. This is described in the sections Section 7.3, “Monitoring Installation via VNC”, Section 7.4, “Monitoring Installation via SSH” and Section 7.5, “Monitoring Installation via Serial Console”.
This section introduces the most common installation scenarios for remote installations. For each scenario, carefully check the list of prerequisites and follow the procedure outlined for that scenario. If in need of detailed instructions for a particular step, follow the links provided for each one of them.
This type of installation still requires some degree of physical access to the target system to boot for installation. The installation is controlled by a remote workstation using VNC to connect to the installation program. User interaction is required as with the manual installation in Chapter 4, Installation Steps.
For this type of installation, make sure that the following requirements are met:
Target system with working network connection.
Controlling system with working network connection and VNC viewer software or JavaScript-enabled browser (Firefox, Chromium, Internet Explorer, Opera, etc.).
Installation DVD.
To perform this kind of installation, proceed as follows:
Boot the target system using DVD1 of the SUSE Linux Enterprise Desktop media kit.
When the boot screen of the target system appears, use the boot parameters prompt to set the VNC options and, if required, the static network configuration. For information about boot parameters, see Chapter 3, Boot Parameters.
Boot parameters for a static network configuration:
netdevice=NETDEVICE hostip=IP_ADDRESS netmask=NETMASK gateway=IP_GATEWAY vnc=1 VNCPassword=PASSWORD
Boot parameters for a dynamic (DHCP) network configuration:
vnc=1 VNCPassword=PASSWORD
The target system boots to a text-based environment, giving the network
address and display number under which the graphical installation
environment can be addressed by any VNC viewer application or browser.
VNC installations announce themselves over OpenSLP and if the firewall
settings permit. They can be found using slptool
as
described in
Section 7.3.1, “Preparing for VNC Installation”.
On the controlling workstation, open a VNC viewing application or Web browser and connect to the target system as described in Section 7.3, “Monitoring Installation via VNC”.
Perform the installation as described in Chapter 4, Installation Steps.
Reconnect to the target system after it reboots for the initial system configuration. For details, see Part V, “Initial System Configuration”.
This type of installation does not require a direct interaction with the target machine. The system is booted via PXE and the installation data is fetched from a server.
To perform this type of installation, make sure that the following requirements are met:
At least one machine that can be used for installing a DHCP, NFS, HTTP, FTP, TFTP, or SMB server.
Target system capable of PXE boot, networking, and Wake on LAN, plugged in and connected to the network.
Controlling system with working network connection and VNC viewer software or JavaScript-enabled browser (Firefox, Chromium, Microsoft Edge, Opera, etc.).
To perform this type of installation, proceed as follows:
Set up the server that contains the installation data. For details, see Part IV, “Setting Up an Installation Server”.
Set up a DHCP and TFTP server for the network. This is described in Chapter 13, Preparing Network Boot Environment. Add the required boot parameters to enable the VNC server.
Enable PXE boot in the target machine firmware. For more information, see Section 13.4, “Preparing the Target System for PXE Boot”.
Initiate the boot process of the target system using Wake on LAN. This is described in Section 13.5, “Using Wake-on-LAN for Remote Wakeups”.
On the controlling workstation, open a VNC viewing application or Web browser and connect to the target system as described in Section 7.3, “Monitoring Installation via VNC”.
Perform the installation as described in Chapter 4, Installation Steps.
Reconnect to the target system after it reboots for the initial system configuration. For details, see Part V, “Initial System Configuration”.
This type of installation still requires some degree of physical access to the target system to boot for installation and to determine the IP address of the installation target. The installation itself is entirely controlled from a remote workstation using SSH to connect to the installer. User interaction is required as with the regular installation described in Chapter 4, Installation Steps.
For this type of installation, make sure that the following requirements are met:
Target system with working network connection.
Controlling system with working network connection and working SSH client software.
Installation DVD.
To perform this kind of installation, proceed as follows:
Set up the installation target and installation server as described in Part IV, “Setting Up an Installation Server”.
Boot the target system using DVD1 of the SUSE Linux Enterprise Desktop media kit.
When the boot screen of the target system appears, use the boot parameters prompt to set the SSH options and, if required, the static network configuration. For information about boot parameters, see Chapter 3, Boot Parameters.
Boot parameters for a static network configuration:
netdevice=NETDEVICE hostip=IP_ADDRESS netmask=NETMASK gateway=IP_GATEWAY ssh=1 ssh.password=PASSWORD
Boot parameters for a dynamic (DHCP) network configuration:
ssh=1 ssh.password=PASSWORD
The target system boots to a text-based environment, giving the network address under which the graphical installation environment can be addressed by any SSH client.
On the controlling workstation, open a terminal window and connect to the target system as described in Section 7.4.2, “Connecting to the Installation Program”.
Perform the installation as described in Chapter 4, Installation Steps.
Reconnect to the target system after it reboots for the initial system configuration. For details, see Part V, “Initial System Configuration”.
This type of installation does not require a direct interaction with the target machine. The system is booted via PXE and the installation data is fetched from a server.
To perform this type of installation, make sure that the following requirements are met:
At least one machine that can be used for installing a DHCP, NFS, HTTP, FTP, TFTP, or SMB server.
Target system capable of PXE boot, networking, and Wake on LAN, plugged in and connected to the network.
Controlling system with working network connection and SSH viewer software.
To perform this type of installation, proceed as follows:
Set up the server that contains the installation data. For details, see Part IV, “Setting Up an Installation Server”.
Set up a DHCP and TFTP server for the network. This is described in Chapter 13, Preparing Network Boot Environment. Add the required boot parameters to enable the SSH server.
Enable PXE boot in the target machine firmware. For more information, see Section 13.4, “Preparing the Target System for PXE Boot”.
Initiate the boot process of the target system using Wake on LAN. This is described in Section 13.5, “Using Wake-on-LAN for Remote Wakeups”.
On the controlling workstation, open an SSH client software and connect to the target system as described in Section 7.4, “Monitoring Installation via SSH”.
Perform the installation as described in Chapter 4, Installation Steps.
Reconnect to the target system after it reboots for the initial system configuration. For details, see Part V, “Initial System Configuration”.
Using any VNC viewer software, you can remotely control the installation of SUSE Linux Enterprise Desktop from virtually any operating system. This section introduces the setup using a VNC viewer application or a Web browser.
To enable VNC on the installation target, specify the appropriate boot parameters at the initial boot for installation (see Chapter 3, Boot Parameters). The target system boots into a text-based environment and waits for a VNC client to connect to the installation program.
The installation program announces the IP address and display number needed to connect for installation. If you have physical access to the target system, this information is provided right after the system booted for installation. Enter this data when your VNC client software prompts for it and provide your VNC password.
Because the installation target announces itself via OpenSLP, you can retrieve the address information of the installation target via an SLP browser. There is no need for any physical contact with the installation target itself, provided your network setup and all machines support OpenSLP:
Run slptool findsrvtypes | grep vnc
to get a list of
all services offering VNC. The VNC installation targets should be
available under a service named
YaST.installation.suse
.
Run slptool findsrvs
YaST.installation.suse to get a list of
installations available. Use the IP address and the port (usually
5901
) provided with your VNC viewer.
There are two ways to connect to a VNC server (the installation target in this case). You can either start an independent VNC viewer application on any operating system or connect using a JavaScript-enabled Web browser.
Using VNC, you can control the installation of a Linux system from any other operating system, including other Linux flavors, Windows, or macOS.
On a Linux machine, make sure that the package
tightvnc
is installed. On a Windows machine,
install the Windows port of this application, which can be obtained at the
TightVNC home page
(http://www.tightvnc.com/download.html).
To connect to the installation program running on the target machine, proceed as follows:
Start the VNC viewer.
Enter the IP address and display number of the installation target as provided by the SLP browser or the installation program itself:
IP_ADDRESS:DISPLAY_NUMBER
A window opens on your desktop displaying the YaST screens as in a normal local installation.
Using a Web browser to connect to the installation program makes you totally independent of any VNC software or the underlying operating system. As long as the browser application has JavaScript support enabled, you can use any browser (Firefox, Internet Explorer, Chromium, Opera, etc.) to perform the installation of your Linux system.
Note that the browser VNC connection is not encrypted.
To perform a VNC installation, proceed as follows:
Launch your preferred Web browser.
Enter the following at the address prompt:
http://IP_ADDRESS_OF_TARGET:5801
Enter your VNC password when prompted to do so. The browser window now displays the YaST screens as in a normal local installation.
Using SSH, you can remotely control the installation of your Linux machine using any SSH client software.
In addition to installing the required software package (OpenSSH for Linux and PuTTY for Windows), you need to specify the appropriate boot parameters to enable SSH for installation. See Chapter 3, Boot Parameters for details. OpenSSH is installed by default on any SUSE Linux–based operating system.
After you have started the SSH installation, use this procedure to connect to the SSH session.
Retrieve the installation target's IP address. If you have physical access to the target machine, take the IP address the installation routine provides in the console after the initial boot. Otherwise take the IP address that has been assigned to this particular host in the DHCP server configuration.
In a command line, enter the following command:
ssh -X root@TARGET_IP_ADDRESS
Replace TARGET_IP_ADDRESS with the actual IP address of the installation target.
When prompted for a user name, enter root
.
When prompted for the password, enter the password that has been set with the SSH boot parameter. After you have successfully authenticated, a command line prompt for the installation target appears.
Enter yast
to launch the installation program. A
window opens showing the normal YaST screens as described in
Chapter 4, Installation Steps.
For this installation method, you need a second computer connected by a null modem cable to the computer on which to install SUSE Linux Enterprise Desktop. Hardware and firmware of both machines need to support the serial console. Some firmware implementations are already configured to send the boot console output to a serial console (by providing a device tree with /chosen/stdout-path set appropriately). In this case no additional configuration is required.
If the firmware does not use the serial console for the boot console
output, set the following boot parameter for the installation:
console=TTY,BAUDRATE
.
For details, see Book “Administration Guide”, Chapter 14 “The Boot Loader GRUB 2”, Section 14.2.5 “Editing Menu Entries during the Boot Procedure” and Chapter 3, Boot Parameters.
BAUDRATE needs to be replaced by the baud rate for the interface. Valid values are 115200, 38400, or 9600. TTY needs to be replaced by the name of the interface. On most computers, there is one or more serial interfaces. Depending on the hardware, the names of the interfaces may vary:
ttyS0 for APM
ttyAMA0 for Server Base System Architecture (SBSA)
ttyPS0 for Xilinx
For the installation, you need a terminal program like minicom
or screen
. To initiate the serial connection, launch the
screen program in a local console by entering the following command:
tux >
screen
/dev/ttyUSB0 115200
This means that screen listens to the first serial port with a baud rate of 115200. From this point on, the installation proceeds similarly to the text-based installation over this terminal.
This section highlights some typical problems you may run into during installation and offers possible solutions or workarounds.
If you encounter any problems using the SUSE Linux Enterprise Desktop installation media, check the integrity of your installation media. Boot from the media and choose › from the boot menu. A minimal system boots and lets you choose which device to check. Select the respective device and confirm with to perform the check.
In a running system, start YaST and choose
› . Insert the medium click . Checking may take several minutes.If errors are detected during the check, do not use this medium for installation. Media problems may, for example, occur when having burned the medium on DVD yourself. Burning the media at a low speed (4x) helps to avoid problems.
If your computer does not contain a built-in bootable DVD drive there are several alternatives. This is also an option if your drive is not supported by SUSE Linux Enterprise Desktop.
Linux supports most existing DVD drives. If the system has no DVD drive, it is still possible that an external DVD drive, connected through USB, FireWire, or SCSI, can be used to boot the system. Sometimes a BIOS update may help if you encounter problems.
If a machine lacks a DVD drive, but provides a working Ethernet connection, perform a completely network-based installation. See Section 7.2.2, “Installation from Network via VNC” and Section 7.2.4, “Installation from Network via SSH” for details.
You can use a USB flash drive if your machine lacks a DVD drive and network connection. For details, see:
One reason a machine does not boot the installation media can be an incorrect boot sequence setting in BIOS. The BIOS boot sequence must have DVD drive set as the first entry for booting. Otherwise the machine would try to boot from another medium, typically the hard disk. Guidance for changing the BIOS boot sequence can be found in the documentation provided with your mainboard, or in the following paragraphs.
The BIOS is the software that enables the very basic functions of a computer. Motherboard vendors provide a BIOS specifically made for their hardware. Normally, the BIOS setup can only be accessed at a specific time—when the machine is booting. During this initialization phase, the machine performs several diagnostic hardware tests. One of them is a memory check, indicated by a memory counter. When the counter appears, look for a line, usually below the counter or somewhere at the bottom, mentioning the key to press to access the BIOS setup. Usually the key to press is one of Del, F1, or Esc. Press this key until the BIOS setup screen appears.
Enter the BIOS using the proper key as announced by the boot routines and wait for the BIOS screen to appear.
To change the boot sequence in an AWARD BIOS, look for the Enter.
entry. Other manufacturers may have a different name for this, such as . When you have found the entry, select it and confirm withIn the screen that opens, look for a subentry called Page ↑ or Page ↓ until the DVD drive is listed first.
or . Change the settings by pressingLeave the BIOS setup screen by pressing Esc. To save the changes, select , or press F10. To confirm that your settings should be saved, press Y.
Open the setup by pressing Ctrl–A.
Select
. The connected hardware components are now displayed.Make note of the SCSI ID of your DVD drive.
Exit the menu with Esc.
Open Enter.
. Under , select and pressEnter the ID of the DVD drive and press Enter again.
Press Esc twice to return to the start screen of the SCSI BIOS.
Exit this screen and confirm with
to boot the computer.Regardless of what language and keyboard layout your final installation will be using, most BIOS configurations use the US keyboard layout as shown in the following figure:
Some hardware types, mainly very old or very recent ones, fail to boot. Reasons can be missing support for hardware in the installation kernel or drivers causing problems on some specific hardware.
If your system fails to install using the standard
mode from the first installation boot screen, try the following:With the DVD still in the drive, reboot the machine with Ctrl–Alt–Del or using the hardware reset button.
When the boot screen appears, press F5, use the arrow keys of your keyboard to navigate to and press Enter to launch the boot and installation process. This option disables the support for ACPI power management techniques.
Proceed with the installation as described in Chapter 4, Installation Steps.
If this fails, proceed as above, but choose
instead. This option disables ACPI and DMA support. Most hardware will boot with this option.
If both of these options fail, use the boot parameters prompt to pass any
additional parameters needed to support this type of hardware to the
installation kernel. For more information about the parameters available as
boot parameters, refer to the kernel documentation located in
/usr/src/linux/Documentation/kernel-parameters.txt
.
Install the kernel-source
package to view the kernel documentation.
There are other ACPI-related kernel parameters that can be entered at the boot prompt prior to booting for installation:
acpi=off
This parameter disables the complete ACPI subsystem on your computer. This may be useful if your computer cannot handle ACPI or if you think ACPI in your computer causes trouble.
acpi=force
Always enable ACPI even if your computer has an old BIOS dated before
the year 2000. This parameter also enables ACPI if it is set in addition
to acpi=off
.
acpi=noirq
Do not use ACPI for IRQ routing.
acpi=ht
Run only enough ACPI to enable hyper-threading.
acpi=strict
Be less tolerant of platforms that are not strictly ACPI specification compliant.
pci=noacpi
Disable PCI IRQ routing of the new ACPI system.
pnpacpi=off
This option is for serial or parallel problems when your BIOS setup contains wrong interrupts or ports.
notsc
Disable the time stamp counter. This option can be used to work around timing problems on your systems. It is a recent feature, so if you see regressions on your machine, especially time related or even total hangs, this option is worth a try.
nohz=off
Disable the nohz feature. If your machine hangs, this option may help. Otherwise it is of no use.
When you have determined the right parameter combination, YaST automatically writes them to the boot loader configuration to make sure that the system boots properly next time.
If inexplicable errors occur when the kernel is loaded or during the installation, select
in the boot menu to check the memory. If returns an error, it is usually a hardware error.After you insert the medium into your drive and reboot your machine, the installation screen comes up, but after you select
, the graphical installer does not start.There are several ways to deal with this situation:
Try to select another screen resolution for the installation dialogs.
Select
for installation.Do a remote installation via VNC using the graphical installer.
Boot for installation.
Press F3 to open a menu from which to select a lower resolution for installation purposes.
Select Chapter 4, Installation Steps.
and proceed with the installation as described inBoot for installation.
Press F3 and select .
Select Chapter 4, Installation Steps.
and proceed with the installation as described inBoot for installation.
Enter the following text at the boot parameters prompt:
vnc=1 vncpassword=SOME_PASSWORD
Replace SOME_PASSWORD with the password to use for VNC installation.
Select Enter to start the installation.
then pressInstead of starting right into the graphical installation routine, the system continues to run in a text mode. The system then halts, displaying a message containing the IP address and port number at which the installer can be reached via a browser interface or a VNC viewer application.
If using a browser to access the installer, launch the browser and enter the address information provided by the installation routines on the future SUSE Linux Enterprise Desktop machine and press Enter:
http://IP_ADDRESS_OF_MACHINE:5801
A dialog opens in the browser window prompting you for the VNC password. Enter it and proceed with the installation as described in Chapter 4, Installation Steps.
Installation via VNC works with any browser under any operating system, provided Java support is enabled.
Provide the IP address and password to your VNC viewer when prompted. A window opens, displaying the installation dialogs. Proceed with the installation as usual.
You inserted the medium into the drive, the BIOS routines are finished, but the system does not start with the graphical boot screen. Instead it launches a very minimalist text-based interface. This may happen on any machine not providing sufficient graphics memory for rendering a graphical boot screen.
Although the text boot screen looks minimalist, it provides nearly the same functionality as the graphical one:
Unlike the graphical interface, the different boot parameters cannot be selected using the cursor keys of your keyboard. The boot menu of the text mode boot screen offers some keywords to enter at the boot prompt. These keywords map to the options offered in the graphical version. Enter your choice and press Enter to launch the boot process.
After selecting a boot parameter, enter the appropriate keyword at the boot prompt or enter some custom boot parameters as described in Section 8.4, “Boot Failure”. To launch the installation process, press Enter.
Use the function keys (F1 ... F12) to determine the screen resolution for installation. If you need to boot in text mode, choose F3.
This chapter describes how to use cloned images for installing SUSE Linux Enterprise Desktop. This is mostly used in virtualized environments.
mksusecd
is a useful tool for creating a customized
installation image. Use it to modify the regular SUSE Linux Enterprise installation images,
adding and removing files, creating a minimal network installation image,
customizing boot and repository options, and creating a minimal boot image
as an alternative to booting a system from a PXE server.
You may customize the standard SUSE Linux Enterprise installation images by
editing a file in the installation ISO image,
media.1/products
.
Add modules and extensions to create a single
customized installation image. Then copy your
custom image to a CD, DVD, or USB device to create a bootable customized
installation medium. See How to Create a Custom Installation
Medium for SUSE Linux Enterprise 15
https://documentation.suse.com/sbp/all/single-html/SBP-SLE15-Custom-Installation-Medium/
for complete instructions.
This chapter describes how to use cloned images for installing SUSE Linux Enterprise Desktop. This is mostly used in virtualized environments.
SUSE Linux Enterprise Desktop provides a script to clean up configuration that is unique
to each installation. With the introduction of systemd
, unique system
identifiers are used and set in different locations and files. Therefore,
cloning is no longer the recommended way to build system images.
Images can be created with KIWI, see
https://doc.suse.com/kiwi/.
To clone disks of machines, refer to the documentation of your virtualization environment.
Executing the following procedure permanently deletes important system configuration data. If the source system for the clone is used in production, run the clean up script on the cloned image.
To clean all unique system identifiers, execute the following procedure
before or after cloning a disk image. If run on the clone, this procedure
needs to be run on each clone. Therefore, we recommend to create a
golden image
that is not used in production and only
serves as a source for new clones. The golden image is already cleaned
up and clones can be used immediately.
The clone-master-clean-up
command for example removes:
Swap files
Zypper repositories
SSH host and client keys
Temporary directories, like /tmp/*
Postfix data
HANA firewall script
systemd journal
Use zypper
to install clone-master-clean-up:
tux >
sudo
zypper
install clone-master-clean-up
Configure the behavior of clone-master-clean-up
by
editing /etc/sysconfig/clone-master-clean-up
.
This configuration file defines whether users with a UID larger than 1000,
the /etc/sudoers
file, Zypper repositories and
Btrfs snapshots should be removed.
Remove existing configuration and unique identifiers by running the script:
tux >
sudo
clone-master-clean-up
mksusecd
is a useful tool for creating a customized
installation image. Use it to modify the regular SUSE Linux Enterprise installation images,
adding and removing files, creating a minimal network installation image,
customizing boot and repository options, and creating a minimal boot image
as an alternative to booting a system from a PXE server.
In SLE 15 mksusecd
is in the Development
Tools Module
. If you have not enabled this module you must enable
it. First find the exact module name with zypper
:
tux >
zypper search-packages mksusecd
Following packages were found in following modules:
Package Module or Repository
-------------------- -----------------------------------------------------------------
mksusecd Development Tools Module (sle-module-development-tools/15/x86_64)
mksusecd-debuginfo Development Tools Module (sle-module-development-tools/15/x86_64)
mksusecd-debugsource Development Tools Module (sle-module-development-tools/15/x86_64)
mksusecd Available
srcpackage:mksusecd Available
To activate the respective module or product, use SUSEConnect --product.
Use SUSEConnect --help for more details.
Enable it with SUSEConnect:
tux >
sudo
SUSEConnect -p sle-module-development-tools/15/x86_64
In SLE 15.1 and later it is in the Main Update
Repository
, which is enabled by default.
Install mksusecd
in the usual way:
tux >
sudo
zypper se mksusecd
Run mksusecd --help
to see a complete list of commands.
After you create your custom image, copy it to a CD/DVD using your preferred
disk-writing program such as Brasero or mybashburn
.
Create a bootable USB drive using the dd
command. Make
sure the device is not mounted, then run the following command:
root #
dd
if=min-install.iso of=/dev/SDB bs=4M
Then your new bootable device is ready to use.
Use mksusecd
to create a minimal boot image to start
client machines from a CD/DVD or USB drive, in place of starting them from a
PXE boot server. The minimal boot image launches the kernel and initrd, and
then the remaining installation files are fetched from a local NFS server
(see Section 12.1, “Setting Up an Installation Server Using YaST”).
Run the following command to create the minimal ISO image:
tux >
sudo
mksusecd
--create min-install.iso \ --net=nfs://192.168.1.1:/srv/install/ARCH/OS_VERSION/SP_VERSION/cd1 \ /srv/tftpboot/EFI/ARCH/boot
Replace the NFS server address with your own. Replace ARCH with the directory corresponding to the target system architecture. Also replace OS_version and SP_VERSION (service pack) according to your paths in Section 12.1, “Setting Up an Installation Server Using YaST”".
Rather than waiting for a boot prompt to enter your custom kernel boot
parameters, configure them in a custom mksusecd
image:
tux >
sudo
mksusecd --create install.iso \ --boot "textmode=1 splash=silent mitigations=auto"
Verify that your custom parameters loaded correctly after startup by
querying /proc
:
tux >
cat /proc/cmdline
SUSE Linux Enterprise 15 supports Modules (not to be confused with kernel modules) and Extensions for different product components. These are add-ons to the default Basesystem, such as Development Tools, Desktop Applications, and SUSE Linux Enterprise Live Patching. For more information refer to the Modules and Extensions Quick Start guide.
With mksusecd
you may create an installation image
containing all the additional Modules and Extensions you want. Start by
querying existing images, like this example for SUSE Linux Enterprise 15 SP1:
tux >
sudo
mksusecd --list-repos SLE-15-SP1-Installer-DVD-ARCH-GM-DVD1.iso \ SLE-15-SP1-Packages-ARCH-GM-DVD1.iso Repositories: SLES15-SP1 [15.1-0] SLES15 [15.1-0] Basesystem-Module [15.1-0] SUSE-CAP-Tools-Module [15.1-0] Containers-Module [15.1-0] Desktop-Applications-Module [15.1-0] Development-Tools-Module [15.1-0] [...]
Create a new installation image that is built from the Modules, Extensions, and repositories that you select, and automatically enable them:
tux >
sudo
mksusecd --create myinstaller.iso\ --enable-repos auto --include-repos Basesystem-Module,Desktop-Applications-Module \ SLE-15-SP1-Installer-DVD-ARCH-GM-DVD1.iso \ SLE-15-SP1-Packages-ARCH-GM-DVD1.iso
This creates and adds the add_on_products.xml
file to
the new image. Replace --enable-repos auto
with
--enable-repos ask
to have the installer present a dialog
for choosing modules.
If you are using AutoYaST to configure your installations, it is not necessary
to list these modules in the AutoYaST control file when you use the
--enable-repos
option.
To create a minimal installation image to launch a network installation, use
the --nano
option:
tux >
sudo
mksusecd --create netinstall.iso \ --nano SLE-15-SP1-Installer-DVD-ARCH-GM-DVD1.iso
To set a different repository, such as your own local repository,
use the --net
option:
tux >
sudo
mksusecd --create localinstall.iso \ --net "https://example.com/local" SLE-15-SP1-Installer-DVD-ARCH-GM-DVD1.iso
You may customize the standard SUSE Linux Enterprise installation images by
editing a file in the installation ISO image,
media.1/products
.
Add modules and extensions to create a single
customized installation image. Then copy your
custom image to a CD, DVD, or USB device to create a bootable customized
installation medium. See How to Create a Custom Installation
Medium for SUSE Linux Enterprise 15
https://documentation.suse.com/sbp/all/single-html/SBP-SLE15-Custom-Installation-Medium/
for complete instructions.
This chapter describes how to create a server that provides the data required for installing SUSE Linux Enterprise Desktop over the network.
This chapter describes how to configure a DHCP and a TFTP server that provide the required infrastructure for booting with PXE.
Rolling out customized preinstallations of SUSE Linux Enterprise Desktop to many identical machines spares you from installing each one of them separately and provides a standardized installation for the end users.
This chapter describes how to create a server that provides the data required for installing SUSE Linux Enterprise Desktop over the network.
Depending on the operating system of the machine used as the network installation source for SUSE Linux Enterprise Desktop, there are several options for the server configuration. The easiest way to set up an installation server is to use YaST.
You can even use a Microsoft Windows machine as the installation server for your Linux deployment. See Section 12.5, “Managing an SMB Repository” for details.
YaST offers a graphical tool for creating network repositories. It supports HTTP, FTP, and NFS network installation servers.
Log in as root
to the machine that should act as installation
server.
Start
› › .Select the repository type (HTTP, FTP, or NFS). The selected service is started automatically every time the system starts. If a service of the selected type is already running on your system and you want to configure it manually for the server, deactivate the automatic configuration of the server service with
. In both cases, define the directory in which the installation data should be made available on the server.Configure the required repository type. This step relates to the automatic configuration of server services. It is skipped when automatic configuration is deactivated.
Define an alias for the root directory of the FTP or HTTP server on which
the installation data should be found. The repository will later be
located under
ftp://Server-IP/Alias/Name
(FTP) or under
http://Server-IP/Alias/Name
(HTTP). Name stands for the name of the
repository, which is defined in the following step. If you selected NFS in
the previous step, define wild cards and export options. The NFS server
will be accessible under
nfs://Server-IP/Name
.
Details of NFS and exports can be found in Book “Administration Guide”, Chapter 32 “Sharing File Systems with NFS”.
Make sure that the firewall settings of your server system allow traffic on ports for HTTP, NFS, and FTP. If they currently do not, enable
or check first.Configure the repository. Before the installation media are copied to their destination, define the name of the repository (ideally, an easily remembered abbreviation of the product and version). YaST allows providing ISO images of the media instead of copies of the installation DVDs. If you want this, activate the relevant check box and specify the directory path under which the ISO files can be found locally. Depending on the product to distribute using this installation server, it might be necessary to add media, such as service pack DVDs as extra repositories. To announce your installation server in the network via OpenSLP, activate the appropriate option.
Consider announcing your repository via OpenSLP if your network setup supports this option. This saves you from entering the network installation path on every target machine. The target systems are booted using the SLP boot parameter and find the network repository without any further configuration. For details on this option, refer to Chapter 3, Boot Parameters.
Configuring extra repositories. YaST follows a specific naming
convention to configure add-on CD or service pack CD repositories.
Configuration is accepted only if the repository name of the
add-on CDs starts with the repository name of the installation
media. In other words, if you chose SLES12SP1
as repository name for DVD1 then you should choose
SLES12SP1addon
as repository name for DVD2.
Upload the installation data. The most lengthy step in configuring an installation server is copying the actual installation media. Insert the media in the sequence requested by YaST and wait for the copying procedure to end. When the sources have been fully copied, return to the overview of existing repositories and close the configuration by selecting
.Your installation server is now fully configured and ready for service. It is automatically started every time the system is started. No further intervention is required. You only need to configure and start this service correctly manually if you deactivated the automatic configuration of the selected network service with YaST as an initial step.
To deactivate a repository, select the repository to remove then select
. The installation data are removed from the system. To deactivate the network service, use the respective YaST module.If your installation server needs to provide the installation data for more than one product of the product version, start the YaST installation server module. Then select
in the overview of existing repositories to configure the new repository.Configuring a server to be an installation server with YaST automatically installs and configures the Apache web server, listening on port 80.
However, configuring a machine to be an RMT server (Repository Mirroring Tool) automatically installs the NGINX web server and configures it to listen on port 80.
Do not try to enable both these functions on the same server. It is not possible for a single server to host both simultaneously.
This assumes that you are using some kind of SUSE Linux-based operating system on the machine that will serve as installation server. If this is not the case, turn to the other vendor's documentation on NFS instead of following these instructions.
Setting up an NFS source for installation is done in two main steps. In the first step, create the directory structure holding the installation data and copy the installation media over to this structure. Second, export the directory holding the installation data to the network.
To create a directory to hold the installation data, proceed as follows:
Log in as root
.
Create a directory that will later hold all installation data and change into this directory. For example:
root #
mkdir -p /srv/install/PRODUCT/PRODUCTVERSIONroot #
cd /srv/install/PRODUCT/PRODUCTVERSION
Replace PRODUCT with an abbreviation of the product name and PRODUCTVERSION with a string that contains the product name and version.
For each DVD contained in the media kit execute the following commands:
Copy the entire content of the installation DVD into the installation server directory:
root #
cp -a /media/PATH_TO_YOUR_DVD_DRIVE .
Replace PATH_TO_YOUR_DVD_DRIVE with the
actual path under which your DVD drive is addressed. Depending on the
type of drive used in your system, this can be
cdrom
, cdrecorder
,
dvd
, or dvdrecorder
.
Rename the directory to the DVD number:
root #
mv PATH_TO_YOUR_DVD_DRIVE DVDX
Replace X with the actual number of your DVD.
On SUSE Linux Enterprise Desktop, you can export the repository with NFS using YaST. Proceed as follows:
Log in as root
.
Start
› › .Select
and and click .
Select PRODUCTVERSION
.
Select exports
man page.
Click SUSE Linux Enterprise Desktop repository is automatically started and integrated into the boot process.
. The NFS server holding theIf you prefer manually exporting the repository via NFS instead of using the YaST NFS Server module, proceed as follows:
Log in as root
.
Open the file /etc/exports
and enter the following
line:
/PRODUCTVERSION *(ro,root_squash,sync)
This exports the directory
/PRODUCTVERSION
to any
host that is part of this network or to any host that can connect to this
server. To limit the access to this server, use netmasks or domain names
instead of the general wild card *
. Refer to the
export
man page for details. Save and exit this
configuration file.
To add the NFS service to the list of servers started during system boot, execute the following commands:
root #
systemctl enable nfsserver
Start the NFS server with systemctl start nfsserver
. If
you need to change the configuration of your NFS server later, modify the
configuration file and restart the NFS daemon with systemctl
restart nfsserver
.
Announcing the NFS server via OpenSLP makes its address known to all clients in your network.
Log in as root
.
Create the /etc/slp.reg.d/install.suse.nfs.reg
configuration file with the following lines:
# Register the NFS Installation Server service:install.suse:nfs://$HOSTNAME/PATH_TO_REPOSITORY/DVD1,en,65535 description=NFS Repository
Replace PATH_TO_REPOSITORY with the actual path to the installation source on your server.
Start the OpenSLP daemon with systemctl start slpd
.
Creating an FTP repository is very similar to creating an NFS repository. An FTP repository can be announced over the network using OpenSLP as well.
Create a directory holding the installation sources as described in Section 12.2, “Setting Up an NFS Repository Manually”.
Configure the FTP server to distribute the contents of your installation directory:
Log in as root
and install the package
vsftpd
using the YaST software management.
Enter the FTP server root directory:
root #
cd/srv/ftp
Create a subdirectory holding the installation sources in the FTP root directory:
root #
mkdir REPOSITORY
Replace REPOSITORY with the product name.
Mount the contents of the installation repository into the change root environment of the FTP server:
root #
mount --bind PATH_TO_REPOSITORY /srv/ftp/REPOSITORY
Replace PATH_TO_REPOSITORY and
REPOSITORY with values matching your setup.
If you need to make this permanent, add it to
/etc/fstab
.
Start vsftpd with vsftpd
.
Announce the repository via OpenSLP, if this is supported by your network setup:
Create the /etc/slp.reg.d/install.suse.ftp.reg
configuration file with the following lines:
# Register the FTP Installation Server service:install.suse:ftp://$HOSTNAME/REPOSITORY/DVD1,en,65535 description=FTP Repository
Replace REPOSITORY with the actual name of
the repository directory on your server. The service:
line should be entered as one continuous line.
Start the OpenSLP daemon with systemctl start slpd
.
Creating an HTTP repository is very similar to creating an NFS repository. An HTTP repository can be announced over the network using OpenSLP as well.
Create a directory holding the installation sources as described in Section 12.2, “Setting Up an NFS Repository Manually”.
Configure the HTTP server to distribute the contents of your installation directory:
Install the Web server Apache.
Enter the root directory of the HTTP server
(/srv/www/htdocs
) and create the subdirectory that
will hold the installation sources:
root #
mkdir REPOSITORY
Replace REPOSITORY with the product name.
Create a symbolic link from the location of the installation sources to
the root directory of the Web server
(/srv/www/htdocs
):
root #
ln -s /PATH_TO_REPOSITORY/srv/www/htdocs/REPOSITORY
Modify the configuration file of the HTTP server
(/etc/apache2/default-server.conf
) to make it
follow symbolic links. Replace the following line:
Options None
with
Options Indexes FollowSymLinks
Reload the HTTP server configuration using systemctl reload
apache2
.
Announce the repository via OpenSLP, if this is supported by your network setup:
Create the /etc/slp.reg.d/install.suse.http.reg
configuration file with the following lines:
# Register the HTTP Installation Server service:install.suse:http://$HOSTNAME/REPOSITORY/DVD1/,en,65535 description=HTTP Repository
Replace REPOSITORY with the actual path to
the repository on your server. The service:
line
should be entered as one continuous line.
Start the OpenSLP daemon using systemctl start slpd
.
Using SMB, you can import the installation sources from a Microsoft Windows server and start your Linux deployment even with no Linux machine around.
To set up an exported Windows Share holding your SUSE Linux Enterprise Desktop repository, proceed as follows:
Log in to your Windows machine.
Create a new directory that will hold the entire installation tree and
name it INSTALL
, for example.
Export this share according to the procedure outlined in your Windows documentation.
Enter this share and create a subdirectory, called
PRODUCT
. Replace
PRODUCT with the actual product name.
Enter the INSTALL/PRODUCT
directory and copy each DVD to a separate directory, such as
DVD1
and DVD2
.
To use an SMB mounted share as a repository, proceed as follows:
Boot the installation target.
Select
.Press F4 for a selection of the repository.
Choose SMB and enter the Windows machine's name or IP address, the share
name
(INSTALL/PRODUCT/DVD1
, in
this example), user name, and password. The syntax looks like this:
smb://workdomain;user:password@server/INSTALL/DVD1
After you press Enter, YaST starts and you can perform the installation.
Instead of copying physical media into your server directory manually, you can also mount the ISO images of the installation media into your installation server and use them as a repository. To set up an HTTP, NFS or FTP server that uses ISO images instead of media copies, proceed as follows:
Download the ISO images and save them to the machine to use as the installation server.
Log in as root
.
Choose and create an appropriate location for the installation data, as described in Section 12.2, “Setting Up an NFS Repository Manually”, Section 12.3, “Setting Up an FTP Repository Manually”, or Section 12.4, “Setting Up an HTTP Repository Manually”.
Create subdirectories for each DVD.
To mount and unpack each ISO image to the final location, issue the following command:
root #
mount -o loop PATH_TO_ISO PATH_TO_REPOSITORY/PRODUCT/MEDIUMX
Replace PATH_TO_ISO with the path to your local copy of the ISO image. Replace PATH_TO_REPOSITORY with the source directory of your server. Replace PRODUCT with the product name and replace MEDIUMX with the type (CD or DVD) and number of media you are using.
Repeat the previous step to mount all ISO images needed for your product.
Start your installation server as usual, as described in Section 12.2, “Setting Up an NFS Repository Manually”, Section 12.3, “Setting Up an FTP Repository Manually”, or Section 12.4, “Setting Up an HTTP Repository Manually”.
To automatically mount the ISO images at boot time, add the respective mount
entries to /etc/fstab
. An entry according to the
previous example would look like the following:
PATH_TO_ISO PATH_TO_REPOSITORY/PRODUCTMEDIUM auto loop
This chapter describes how to configure a DHCP and a TFTP server that provide the required infrastructure for booting with PXE.
SUSE® Linux Enterprise Desktop can be installed via a Preboot Execution Environment (PXE). The client hardware needs to support booting via PXE. The network needs to provide a DHCP server and a TFTP server providing the required data to the clients. This chapter guides you through setting up the required servers.
PXE only boots a kernel and initrd. This can be used to boot into an installation environment or into live systems. To set up the installation sources, see Chapter 12, Setting Up a Network Installation Source.
This section covers the configuration tasks needed in complex boot scenarios. It contains ready-to-apply configuration examples for DHCP, PXE boot, TFTP, and Wake on LAN.
The examples assume that the DHCP, TFTP and NFS server reside on the
same machine with the IP 192.168.1.1
. All services
can reside on different machines without any problems. Make sure to
change the IP addresses as required.
A DHCP server provides both dynamic (Section 13.1.1, “Dynamic Address Assignment”) and static IP address assignments (Section 13.1.2, “Assigning Static IP Addresses”) to your network clients. It advertises servers, routes, and domains. For TFTP servers, DHCP also provides the kernel and initrd files. Which files are loaded depends on the architecture of the target machine, and whether legacy BIOS or UEFI boot is used. The clients transmit their architecture type in their DHCP requests. Based on this information, the DHCP server decides which files the client must download for booting.
Starting with SUSE Linux Enterprise 15.0, there are special conditions that cause PXE boot and AutoYaST installations to fail. See Section 13.1.3, “PXE and AutoYaST Installation Failures” for more information and the solution.
The following example shows how to set up a DHCP server that dynamically assigns IP addresses to clients, and advertises servers, routers, domains, and boot files.
Log in as root
to the machine hosting the DHCP server.
Enable the DHCP server by executing systemctl enable
dhcpd
.
Append the following lines to a subnet configuration of your DHCP
server's configuration file located under
/etc/dhcpd.conf
:
# The following lines are optional option domain-name "my.lab"; option domain-name-servers 192.168.1.1; option routers 192.168.1.1; option ntp-servers 192.168.1.1; ddns-update-style none; default-lease-time 3600; # The following lines are required option arch code 93 = unsigned integer 16; # RFC4578 subnet 192.168.1.0 netmask 255.255.255.0 { next-server 192.168.1.1; range 192.168.1.100 192.168.1.199; default-lease-time 3600; max-lease-time 3600; if option arch = 00:07 or option arch = 00:09 { filename "/EFI/x86/grub.efi"; } else if option arch = 00:0b { filename "/EFI/aarch64/bootaa64.efi"; } else { filename "/BIOS/x86/pxelinux.0"; } }
This configuration example uses the subnet
192.168.1.0/24
with the DHCP, DNS and gateway on the
server with the IP 192.168.1.1
. Make sure that all
IP addresses are changed according to your network layout. For more
information about the options available in
dhcpd.conf
, refer to the
dhcpd.conf
manual page.
Restart the DHCP server by executing systemctl restart
dhcpd
.
A DHCP server may also assign static IP addresses and host names to network clients. One use case is assigning static addresses to servers. Another use case is restricting which clients may join the network to those with assigned static IP addresses, and providing no dynamic address pools.
Modify the above DHCP configuration according to the following example:
group { host test { hardware ethernet MAC_ADDRESS; fixed-address IP_ADDRESS; } }
The host statement assigns a host name to the installation target. To bind the host name and IP address to a specific host, you must specify the client's hardware (MAC) address. Replace all the variables used in this example with the actual values that match your environment, then save your changes and restart the DHCP server.
Starting with SUSE Linux Enterprise 15.0 and ISC DHCP 4.3.x, there are special circumstances that cause PXE boot and AutoYaST installations to fail. If your DHCP server does not have a pool of available dynamic IP addresses, but allows only pre-defined static addresses per client, and the clients send RFC 4361 client identifiers, then PXE/AutoYaST installations will not work. (Allowing only addresses assigned to specific network clients, and providing no dynamic address pools, prevents random machines from joining the network.)
When a new system starts in PXE, it sends a request to the DHCP server and
identifies itself using a client identifier constructed from the hardware type plus
the MAC address of the network interface. This is a RFC 2132 client-id
. The DHCP
server then offers the assigned IP address. Next, the installation kernel is loaded,
and sends another DHCP request, but this client-id
is different, and is sent in
RFC 4361 format. The DHCP server will not recognize this as the same client, and
will look for a free dynamic IP address, which is not available, and the installation stops.
The solution is to configure clients to send RFC 2132 client IDs.
To send a RFC 2132 client-id
during the installation, use
linuxrc
to pass
the following ifcfg
command:
ifcfg=eth0=dhcp,DHCLIENT_CLIENT_ID=01:03:52:54:00:02:c2:67, DHCLIENT6_CLIENT_ID=00:03:52:54:00:02:c2:67
The traditionally-used RFC 2132 DHCPv4 client-id
on
Ethernet is constructed from the hardware type (01
for
Ethernet) and followed by the hardware address (the MAC address), for
example:
01:52:54:00:02:c2:67
The RFC 4361 DHCPv4 client-id
attempts to correct the problem
of identifying a machine that has more than one network interface. The new
DHCPv4 client-id
has the same format as the DHCPv6
client-id
. It starts with the
0xff
prefix, instead of the hardware type, followed by the
DHCPv6 IAID (the interface-address association ID that describes the
interface on the machine), followed by the DHCPv6 DHCP Unique
Identifier (DUID), which uniquely identifies the machine.
Using the above hardware type-based and hardware address-based DUID, the new
RFC 4361 DHCPv4 client-id
would be:
Using the last bytes of the MAC address as the IAID:
ff:00:02:c2:67:00:01:xx:xx:xx:xx:52:54:00:02:c2:67
When the IAID is a simple incremented number:
ff:00:00:00:01:00:01:xx:xx:xx:xx:52:54:00:02:c2:67
The xx:xx:xx:xx fields in the DUID-Link-Layer Timestamp
(DUID-LLT) is a creation timestamp. A DUID-Link-Layer (DUID-LL) (00:03:00:01:$MAC
)
does not have a timestamp.
For more information on using linuxrc
, see the AutoYaST Guide.
Also see man 4 initrd
, and the
documentation for the options dhcp4
"create-cid"
, dhcp6 "default-duid"
in
man 5 wicked-config
, wicked duid
--help
, and wicked iaid --help
.
The following procedures describe how to prepare the server for target machines with UEFI and BIOS on x86 architectures with 32 and 64 bits. The prepared structure also already provides for AArch64 systems.
To install a TFTP server, use the following procedure:
Install the tftp
package.
tux >
sudo
zypper in tftp
Review the tftpd
configuration in
/etc/sysconfig/tftp
and add or change options as
required. Refer to man 8 tftpd
for more details.
The TFTP daemon works without changing the configuration. The default root
directory for the files is /srv/tftpboot
.
Ensure that tftpd
is started at
boot time, and restart it to read the new configuration.
tux >
sudo
systemctl enable tftp.socket
tux >
sudo
systemctl restart tftp.socket
SUSE Linux Enterprise Desktop provides the required files for booting via a PXE on BIOS or UEFI machines in an RPM. Install the files on the machine running the TFTP server:
tux >
sudo
zypper in tftpboot-installation-SLE-OS_VERSION-ARCHITECTURE
Replace OS_VERSION with the version of your
SUSE Linux Enterprise Desktop installation, for example SLE-15-SP1-x86_64
with the architecture of your
system, for example x86_64
. Run
zypper se tftpboot
to search for all available
versions and architectures.
The files will be installed in
/srv/tftpboot/SLE-OS_VERSION-ARCHITECTURE
.
You can also copy the files for other versions and
architectures of SUSE Linux Enterprise Desktop to the
/srv/tftpboot
directory.
/srv/tftpboot/
Directory
If the directory /srv/tftpboot/
already
exists on your machine, then all files will be installed to
/usr/share/tftpboot-installation/
. This is
the case if you are upgrading your PXE server from a previous
SLES release.
To fix this problem, copy the files manually from
/usr/share/tftpboot-installation/
to
/srv/tftpboot/
. Alternatively, remove
/srv/tftpboot/
and reinstall the
tftpboot-installation-SLE-OS_VERSION-ARCHITECTURE
package.
Open the file
/srv/tftpboot/SLE-OS_VERSION-ARCHITECTURE/net/pxelinux.cfg/default
in an editor. Replace the path for the install
parameter according to your setup as described in Chapter 12, Setting Up a Network Installation Source. Also replace
TFTP_SERVER with the IP address of the
TFTP server. For an overview of the PXELINUX configuration options,
see Section 13.3, “PXELINUX Configuration Options”.
default linux # install label linux ipappend 2 kernel boot/ARCHITECTURE/loader/linux append initrd=boot/ARCHITECTURE/loader/initrd instsys=tftp://TFTP_SERVER/SLE-OS_VERSION-ARCHITECTURE/boot/ARCHITECTURE/root install=PROTOCOL://SERVER_IP:/PATH display message implicit 1 prompt 1 timeout 50
For details about the boot parameters that are used in the append
line,
see Section 3.3, “List of Important Boot Parameters”.
If required, edit the
/srv/tftpboot/SLE-OS_VERSION-ARCHITECTURE/net/pxelinux.cfg/message
to display a message in the boot menu.
There is no need to change the GRUB2 configuration files. However,
in the default settings no network source for the installation system
is provided. If you want to fully install SUSE Linux Enterprise Desktop via the
network, add the install
parameter to the
linuxefi
lines in the file
/srv/tftpboot/SLE-OS_VERSION-ARCHITECTURE/EFI/BOOT/grub.cfg
.
Set the install
parameter according to your setup as described in
Chapter 12, Setting Up a Network Installation Source. For details about other
boot parameters that are used in the efilinux
lines, see Section 3.3, “List of Important Boot Parameters”.
The options listed here are a subset of all the options available for the PXELINUX configuration file.
APPEND OPTIONS
Adds one or more options to the kernel command line. These are added for both automatic and manual boots. The options are added at the very beginning of the kernel command line, usually permitting explicitly entered kernel options to override them.
APPEND -
Appends nothing. APPEND
with a single hyphen as argument
in a LABEL
section can be used to override a global
APPEND
.
DEFAULT KERNEL_OPTIONS...
Sets the default kernel command line. If PXELINUX boots automatically, it acts as if the entries after DEFAULT had been typed in at the boot prompt, except the auto option is automatically added, indicating an automatic boot.
If no configuration file exists or no DEFAULT entry is defined in the configuration file, the default is the kernel name “linux” with no options.
IFAPPEND FLAG
Adds a specific option to the kernel command line depending on the
FLAG value. The IFAPPEND
option is available only on PXELINUX. FLAG
expects a value, described in
Table 13.1, “Generated and Added Kernel Command Line Options from IFAPPEND
”:
IFAPPEND
#
Argument |
Generated Kernel Command Line / Description |
---|---|
|
ip=CLIENT_IP:BOOT_SERVER_IP:GW_IP:NETMASK The placeholders are replaced based on the input from the DHCP/BOOTP or PXE boot server. Note, this option is not a substitute for running a DHCP client in the booted system. Without regular renewals, the lease acquired by the PXE BIOS will expire, making the IP address available for reuse by the DHCP server. |
|
BOOTIF=MAC_ADDRESS_OF_BOOT_INTERFACE This option is useful to avoid timeouts when the installation server probes one LAN interface after another until it gets a reply from a DHCP server. This option allows an initrd program to determine from which interface the system has been booted. linuxrc reads this option and uses this network interface. |
|
SYSUUID=SYSTEM_UUID
Adds UUIDs in lowercase hexadecimals, see
|
LABEL LABEL KERNEL IMAGE
APPEND OPTIONS...
Indicates that if LABEL is entered as the
kernel to boot, PXELINUX should instead boot
IMAGE and the specified
APPEND
options should be used. They replace the ones
specified in the global section of the file, before the first
LABEL
command. The default for
IMAGE is the same as
LABEL and, if no APPEND
is
given, the default is to use the global entry (if any). Up to 128
LABEL
entries are permitted.
PXELINUX uses the following syntax:
label MYLABEL kernel MYKERNEL append MYOPTIONS
Labels are mangled as if they were file names and they must be unique after mangling. For example, the two labels “v2.6.30” and “v2.6.31” would not be distinguishable under PXELINUX because both mangle to the same DOS file name.
The kernel does not need to be a Linux kernel. It can also be a boot sector or a COMBOOT file.
LOCALBOOT TYPE
On PXELINUX, specifying LOCALBOOT 0
instead of a
KERNEL
option means invoking this particular label and
causes a local disk boot instead of a kernel boot.
Argument |
Description |
---|---|
|
Perform a normal boot |
|
Perform a local boot with the Universal Network Driver Interface (UNDI) driver still resident in memory |
|
Perform a local boot with the entire PXE stack, including the UNDI driver, still resident in memory |
All other values are undefined. If you do not know what the UNDI or PXE
stacks are, specify 0
.
TIMEOUT TIME-OUT
Indicates how long to wait at the boot prompt until booting automatically, in units of 1/10 second. The time-out is canceled when the user types anything on the keyboard, assuming the user will complete the command begun. A time-out of zero disables the time-out completely (this is also the default). The maximum possible time-out value is 35996 (just less than one hour).
PROMPT flag_val
If flag_val
is 0, displays the boot prompt only if
Shift or Alt is pressed or
Caps Lock or Scroll Lock is set (this
is the default). If flag_val
is 1, always displays the
boot prompt.
F2 FILENAME F1 FILENAME ..etc... F9 FILENAME F10 FILENAME
Displays the indicated file on the screen when a function key is pressed
at the boot prompt. This can be used to implement preboot online help
(presumably for the kernel command line options). For backward
compatibility with earlier releases, F10 can be also
entered as F0
. Note that there is currently no way to
bind file names to F11 and F12.
Prepare the system's BIOS for PXE boot by including the PXE option in the BIOS boot order.
Do not place the PXE option ahead of the hard disk boot parameter in the BIOS. Otherwise this system would try to re-install itself every time you boot it.
Wake-on-LAN (WOL) is an Ethernet standard for remotely waking up a computer by sending it a wakeup signal over a network. This signal is called the "magic packet". Install WOL on client machines to enable remote wakeups, and on every machine you want to use for sending the wakeup signal. The magic packet is broadcast over UDP port 9 to the MAC address of the network interface on the client machine.
When computers are shutdown they usually are not turned all the way off, but remain in a low power mode. When the network interface supports WOL it listens for the magic packet wakeup signal when the machine is powered off. You can send the magic packet manually, or schedule wakeups in a cron job on the sending machine.
WOL works with both wired and wireless Ethernet cards that support it.
You may need to enable WOL in your system BIOS/UEFI.
Check your BIOS/UEFI settings for PXE boot, and make sure it is disabled to prevent accidental re-installations.
Adjust your firewall to allow traffic over UDP port 9.
Run the following command to see if a wired Ethernet interface supports WOL:
tux >
sudo
ethtool eth0 | grep -i wake-on Supports Wake-on: pumbg Wake-on: g
The example output shows that eth0 supports WOL, indicated by the
g
flag on the Supports Wake-on
line.
Wake-on: g
shows that WOL is already enabled, so this
interface is ready to receive wakeup signals. If WOL is not enabled,
enable it with this command:
tux >
sudo
ethtool -s wol g
Wakeup-over-wifi, or WoWLAN, requires a wireless network interface that
supports WoWLAN. Test it with the iw
, command, which
is provided by the iw package:
tux >
sudo
zypper in iw
Find your device name:
tux >
sudo
iw dev phy#0 Interface wlan2 ifindex 3 wdev 0x1 addr 9c:ef:d5:fe:01:7c ssid accesspoint type managed channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz txpower 20.00 dBm
In this example, the device name to use for querying WoWLAN support is
phy#0
. This example shows that it is not supported:
tux >
sudo
iw phy#0 wowlan show command failed: Operation not supported (-95)
This example shows an interface that supports WoWLAN, but it is not enabled:
tux >
sudo
iw phy#0 wowlan show WoWLAN is disabled
Enable it:
tux >
sudo
iw phy#0 wowlan enable magic-packet WoWLAN is enabled: * wake up on magic packet
To use WOL, install the wol package on the client and sending machines:
tux >
sudo
zypper in wol
Install wol-udev-rules on your client machines. This package installs a udev rule that enables WOL automatically at startup.
Get the MAC address of the network interface on the client machine:
tux >
sudo
ip addr show eth0|grep ether link/ether 7c:ef:a5:fe:06:7c brd ff:ff:ff:ff:ff:ff
In the example output, 7c:ef:a5:fe:06:7c
is the MAC
address.
Shut down your client machine, and send it a wakeup signal from another computer on the same subnet:
tux >
wol 7c:ef:a5:fe:06:7c
When your target machine and second device are on the same network but in different subnets, specify the broadcast address for your target machine:
tux >
wol -i 192.168.0.63 7c:ef:a5:fe:06:7c
Because WOL relies on broadcast domains the sending machine must be on the same network, though it can be in a different network segment.
It is possible to send the magic packet from a different network. One way is with port forwarding, if your router supports port forwarding to a broadcast address. A more secure method is to SSH to a host inside your network, and send the magic packet from there.
Rolling out customized preinstallations of SUSE Linux Enterprise Desktop to many identical machines spares you from installing each one of them separately and provides a standardized installation for the end users.
With YaST firstboot, create customized preinstallation images and determine the workflow for the final personalization steps that involve end user interaction (as opposed to AutoYaST, which allows completely automated installations).
Creating a custom installation, rolling it out to your hardware, and personalizing the final product involves the following steps:
Prepare the master machine whose disk needs to be cloned to the client machines. For more information, refer to Section 14.1, “Preparing the Master Machine”.
Customize the firstboot workflow. For more information, refer to Section 14.2, “Customizing the Firstboot Installation”.
Clone the master machine's disk and roll this image out to the clients' disks. For more information, refer to Section 14.3, “Cloning the Master Installation”.
Have the end user personalize the instance of SUSE Linux Enterprise Desktop. For more information, refer to Section 14.4, “Personalizing the Installation”.
To prepare a master machine for a firstboot workflow, proceed as follows:
Insert the installation media into the master machine.
Boot the machine.
Perform a normal installation including all necessary configuration
steps, and make sure to select the yast2-firstboot
package for installation.
To define your own workflow of YaST configuration steps for the end user or to add your own YaST modules to this workflow, proceed to Section 14.2, “Customizing the Firstboot Installation”. Otherwise proceed directly to Step 5.
Enable firstboot as root
:
Create an empty file
/var/lib/YaST2/reconfig_system
to trigger
firstboot's execution. This file will be deleted after the firstboot
configuration has been successfully accomplished. Create this file
using the following command:
touch /var/lib/YaST2/reconfig_system
Proceed to Section 14.3, “Cloning the Master Installation”.
Customizing the firstboot installation workflow may involve several different components. Customizing them is recommended. If you do not make any changes, firstboot performs the installation using the default settings. The following options are available:
Customizing messages to the user, as described in Section 14.2.1, “Customizing YaST Messages”.
Customizing licenses and license actions, as described in Section 14.2.2, “Customizing the License Action”.
Customizing the release notes to display, as described in Section 14.2.3, “Customizing the Release Notes”.
Customizing the order and number of components involved in the installation, as described in Section 14.2.4, “Customizing the Workflow”.
Configuring additional optional scripts, as described in Section 14.2.5, “Configuring Additional Scripts”.
To customize any of these components, modify the following configuration files:
/etc/sysconfig/firstboot
Configure various aspects of firstboot (such as release notes, scripts, and license actions).
/etc/YaST2/firstboot.xml
Configure the installation workflow by enabling or disabling components or adding custom ones.
Provide translations for such a customized installation workflow, as described in Section 14.2.6, “Providing Translations of the Installation Workflow”.
/etc/YaST2/firstboot.xml
is the default path for
the control file, installed by the
yast2-firstboot
package. If you need to
define a different location for the control file, edit
/etc/sysconfig/firstboot
, and change the
FIRSTBOOT_CONTROL_FILE
variable to your preferred
location.
If you want to customize more than the workflow components, refer to the
control.xml
documentation at
http://doc.opensuse.org/projects/YaST/SLES11/tdg/inst_in_general_chap.html#product_control.
By default, an installation of SUSE Linux Enterprise Desktop contains several default messages that are localized and displayed at certain stages of the installation process. These include a welcome message, a license message, and a congratulatory message at the end of installation. You can replace any of these with your own versions and include localized versions of them in the installation. To include your own welcome message, proceed as follows:
Log in as root
.
Open the /etc/sysconfig/firstboot
configuration
file and apply the following changes:
Set FIRSTBOOT_WELCOME_DIR
to the directory path where
you want to store the files containing the welcome message and the
localized versions, for example:
FIRSTBOOT_WELCOME_DIR="/usr/share/firstboot/"
If your welcome message has file names other than
welcome.txt
and
welcome_locale.txt
(where locale matches the ISO 639
language codes such as “cs” or “de”),
specify the file name pattern in
FIRSTBOOT_WELCOME_PATTERNS
. For example:
FIRSTBOOT_WELCOME_PATTERNS="mywelcome.txt"
If unset, the default value of welcome.txt
is
assumed.
Create the welcome file and the localized versions and place them in
the directory specified in the
/etc/sysconfig/firstboot
configuration file.
Proceed in a similar way to configure customized license and finish
messages. These variables are FIRSTBOOT_LICENSE_DIR
and
FIRSTBOOT_FINISH_FILE
.
Change the SHOW_Y2CC_CHECKBOX
to “yes” if
the user needs to be able to start YaST directly after performing the
installation.
You can customize the way the installation system reacts to a user's refusal to accept the license agreement. There are three different ways which the system could react to this scenario:
The firstboot installation is aborted and the entire system shuts down. This is the default setting.
The firstboot installation continues.
The firstboot installation is aborted, but the system attempts to boot.
Make your choice and set LICENSE_REFUSAL_ACTION
to the
appropriate value.
Depending on if you have changed the instance of SUSE Linux Enterprise Desktop you are deploying with firstboot, you probably need to educate the end users about important aspects of their new operating system. A standard installation uses release notes (displayed during one of the final stages of the installation) to provide important information to the users. To have your own modified release notes displayed as part of a firstboot installation, proceed as follows:
Create your own release notes file. Use the RTF format as in the
example file in /usr/share/doc/release-notes
and
save the result as RELEASE-NOTES.en.rtf
(for
English).
Store optional localized versions next to the original version and
replace the en
part of the file name with the
actual ISO 639 language code, such as de
for
German.
Open the firstboot configuration file from
/etc/sysconfig/firstboot
and set
FIRSTBOOT_RELEASE_NOTES_PATH
to the actual directory
where the release notes files are stored.
The provided /etc/YaST2/firstboot.xml
example, defines
a standard workflow which includes the following enabled components:
Language Selection
Welcome
License Agreement
Time and Date
Users
Root Password
Finish Setup
Bear in mind that this workflow is just a template. You may adjust
it properly, manually editing the firstboot configuration file
/etc/YaST2/firstboot.xml
. This XML file is a subset
of the standard control.xml
file that is used by
YaST to control the installation workflow. See Example 14.2, “Configuring the Workflow Section”
to learn more about how to configure the workflow section.
For an overview about proposals, see Example 14.1, “Configuring the Proposal Screens”. This provides you with enough background to modify the firstboot installation workflow. The basic syntax of the firstboot configuration file (plus how the key elements are configured) is explained with this example.
… <proposals config:type="list">1 <proposal>2 <name>firstboot_hardware</name>3 <mode>installation</mode>4 <stage>firstboot</stage>5 <label>Hardware Configuration</label>6 <proposal_modules config:type="list">7 <proposal_module>printer</proposal_module>8 </proposal_modules> </proposal> <proposal> … </proposal> </proposals>
The container for all proposals that should be part of the firstboot workflow. | |
The container for an individual proposal. | |
The internal name of the proposal. | |
The mode of this proposal. Do not make any changes here. For a
firstboot installation, this must be set to
| |
The stage of the installation process at which this proposal is
invoked. Do not make any changes here. For a firstboot installation,
this must be set to | |
The label to be displayed on the proposal. | |
The container for all modules that are part of the proposal screen. | |
One or more modules that are part of the proposal screen. |
The next section of the firstboot configuration file consists of the workflow definition. All modules that should be part of the firstboot installation workflow must be listed here.
<workflows config:type="list"> <workflow> <defaults> <enable_back>yes</enable_back> <enable_next>yes</enable_next> <archs>all</archs> </defaults> <stage>firstboot</stage> <label>Configuration</label> <mode>installation</mode> … <!–– list of modules ––> </modules> </workflow> </workflows> …
The overall structure of the workflows
section is
very similar to that of the proposals
section. A
container holds the workflow elements and the workflow elements all
include stage, label and mode information (just as the proposals
introduced in Example 14.1, “Configuring the Proposal Screens”). The most notable
difference is the defaults
section, which contains
basic design information for the workflow components:
enable_back
Include the
button in all dialogs.enable_next
Include the
button in all dialogs.archs
Specify the hardware architectures on which this workflow should be used.
<modules config:type="list">1 <module>2 <label>Language</label>3 <enabled config:type="boolean">false</enabled>4 <name>firstboot_language</name>5 </module> <modules>
The container for all components of the workflow. | |
The module definition. | |
The label displayed with the module. | |
The switch to enable or disable this component in the workflow. | |
The module name. The module itself must be located under
|
To make changes to the number or order of proposal screens during the firstboot installation, proceed as follows:
Open the firstboot configuration file at
/etc/YaST2/firstboot.xml
.
Delete or add proposal screens or change the order of the existing ones:
To delete an entire proposal, remove the proposal
element including all its sub-elements from the
proposals
section and remove the respective
module
element (with sub-elements) from the
workflow.
To add a new proposal, create a new proposal
element and fill in all the required sub-elements. Make sure that
the proposal exists as a YaST module in
/usr/share/YaST2/clients
.
To change the order of proposals, move the respective
module
elements containing the proposal screens
around in the workflow. Note that there may be dependencies to other
installation steps that require a certain order of proposals and
workflow components.
Apply your changes and close the configuration file.
You can always change the workflow of the configuration steps when the default does not meet your needs. Enable or disable certain modules in the workflow (or add your own custom ones).
To toggle the status of a module in the firstboot workflow, proceed as follows:
Open the /etc/YaST2/firstboot.xml
configuration
file.
Change the value for the enabled
element from
true
to false
to disable the
module or from false
to true
to
enable it again.
<module> <label>Time and Date</label> <enabled config:type="boolean">true</enabled> <name>firstboot_timezone</name> </module>
Apply your changes and close the configuration file.
To add a custom made module to the workflow, proceed as follows:
Create your own YaST module and store the module file
module_name.rb
in
/usr/share/YaST2/clients
.
Open the /etc/YaST2/firstboot.xml
configuration
file.
Determine at which point in the workflow your new module should be run. In doing so, make sure that possible dependencies to other steps in the workflow are taken into account and resolved.
Create a new module
element inside the
modules
container and add the appropriate
sub-elements:
<modules config:type="list"> … <module> <label>my_module</label> <enabled config:type="boolean">true</enabled> <name>filename_my_module</name> </module> </modules>
Enter the label to be displayed on your module in the
label
element.
Make sure that enabled
is set to
true
to have your module included in the
workflow.
Enter the file name of your module in the name
element. Omit the full path and the .rb
suffix.
Apply your settings and close the configuration file.
If the target hardware may feature more than one network interface add
the network-autoconfig
package to the
application image. network-autoconfig
cycles
through all available Ethernet interfaces until one is successfully configured via DHCP.
Firstboot can be configured to execute additional scripts after the firstboot workflow has been completed. To add additional scripts to the firstboot sequence, proceed as follows:
Open the /etc/sysconfig/firstboot
configuration
file and make sure that the path specified for
SCRIPT_DIR
is correct. The default value is
/usr/share/firstboot/scripts
.
Create your shell script, store it in the specified directory, and apply the appropriate file permissions.
Depending on the end user it could be desirable to offer translations of
the customized workflow. Those translations could be necessary, if you
customized the workflow by changing the
/etc/YaST2/firstboot.xml
file, as described in
Section 14.2.4, “Customizing the Workflow”.
If you have changed /etc/YaST2/firstboot.xml
and
introduced string changes, generate a new translation template file
(.pot
file) and use the
gettext
tool chain to translate and finally
install the translated files in the YaST locale directories
(/usr/share/YaST2/locale
) as compiled
.mo
files. Proceed as follows:
Change the textdomain
setting from:
<textdomain>firstboot</textdomain>
to, for example,
<textdomain>firstboot-oem</textdomain>
Use xgettext
to extract the translatable strings to
the translation template file (.pot
file), for
example to firstboot-oem.pot
:
xgettext -L Glade -o firstboot-oem.pot /etc/YaST2/firstboot.xml
Start the translation process. Then package the translated files
(.LL_code.po
files)
the same way as translations of the other projects and install the
compiled firstboot-oem.mo
files.
If you need translations for additional or changed YaST modules, provide translations within such a module itself. If you changed an existing module, make sure to change also its text-domain statement to avoid undesired side effects.
For more information about YaST development, refer to https://en.opensuse.org/openSUSE:YaST_development. Detailed information about YaST firstboot can be found at http://doc.opensuse.org/projects/YaST/SLES11/tdg/bk09ch01s02.html.
Clone the master machine's disk using any of the imaging mechanisms available to you, and roll these images out to the target machines. For more information about imaging, see https://doc.suse.com/kiwi/.
As soon as the cloned disk image is booted, firstboot starts and the installation proceeds exactly as laid out in Section 14.2.4, “Customizing the Workflow”. Only the components included in the firstboot workflow configuration are started. All other installation steps are skipped. The end user adjusts language, keyboard, network, and password settings to personalize the workstation. After this process is finished, a firstboot installed system behaves as any other instance of SUSE Linux Enterprise Desktop.
YaST allows you to configure hardware items such as audio hardware, your system keyboard layout or printers.
Use YaST's software management module to search for software components you want to add or remove. YaST resolves all dependencies for you. To install packages not shipped with the installation media, add software repositories to your setup and let YaST manage them. Keep your system up-to-date by managing software updates with the update applet.
Modules and extensions add parts or functionality to the system. This chapter covers their installation, scope, support status and lifecycle.
SUSE Linux Enterprise Desktop supports the parallel installation of multiple kernel versions. When installing a second kernel, a boot entry and an initrd are automatically created, so no further manual configuration is needed. When rebooting the machine, the newly added kernel is available as an additional boot parameter.
Using this functionality, you can safely test kernel updates while being able to always fall back to the proven former kernel. To do this, do not use the update tools (such as the YaST Online Update or the updater applet), but instead follow the process described in this chapter.
During installation, you could have created a local user for your system. With the YaST module
you can add users or edit existing ones. It also lets you configure your system to authenticate users with a network server.This chapter explains how to configure language and country settings. You can change the language globally for the whole system, individually for certain users or desktops, or temporarily for single applications. Additionally, you can configure secondary languages and adjust the date and country settings.
YaST allows you to configure hardware items such as audio hardware, your system keyboard layout or printers.
Graphics card, monitor, mouse and keyboard can be configured with GNOME tools. See Book “GNOME User Guide”, Chapter 3 “Customizing Your Settings” for details.
The YaST
module lets you define the default keyboard layout for the system (also used for the console). Users can modify the keyboard layout in their individual X sessions, using the desktop's tools.
Start the YaST sudo yast2 keyboard
.
Select the desired
from the list.Optionally, you can also define the keyboard repeat rate or keyboard delay rate in the
.Try the selected settings in the
text box.
If the result is as expected, confirm your changes and close the dialog.
The settings are written to /etc/sysconfig/keyboard
.
The result is stored in the files /etc/vconsole.conf
(for text consoles) and
/etc/X11/xorg.conf.d/00-keyboard.conf
(for X11).
Advanced keyboard settings can be configured in /etc/sysconfig/keyboard
.
YaST detects most sound cards automatically and configures them with the appropriate values. To change the default settings, or to set up a sound card that could not be configured automatically, use the YaST sound module. There, you can also set up additional sound cards or switch their order.
To start the sound module, start YaST and click yast2 sound &
as user root
from a command line. If the sound module is not available, install it using
the sudo zypper install yast2-sound
command.
The dialog shows all sound cards that were detected.
If you have added a new sound card or YaST could not automatically configure an existing sound card, follow the steps below. For configuring a new sound card, you need to know your sound card vendor and model. If in doubt, refer to your sound card documentation for the required information. For a reference list of sound cards supported by ALSA with their corresponding sound modules, see http://www.alsa-project.org/main/index.php/Matrix:Main.
During configuration, you can choose between the following setup options:
You are not required to go through any of the further configuration steps—the sound card is configured automatically. You can set the volume or any options you want to change later.
Allows you to adjust the output volume and play a test sound during the configuration.
For experts only. Allows you to customize all parameters of the sound card.
Only use this option if you know exactly what you are doing. Otherwise leave the parameters untouched and use the normal or the automatic setup options.
Start the YaST sound module.
To configure a detected, but
sound card, select the respective entry from the list and click .To configure a new sound card, click
. Select your sound card vendor and model and click .Choose one of the setup options and click
.If you have chosen
, you can now your sound configuration and make adjustments to the volume. You should start at about ten percent volume to avoid damage to your hearing or the speakers.If all options are set according to your wishes, click
.The
dialog shows the newly configured or modified sound card.To remove a sound card configuration that you no longer need, select the respective entry and click
.Click
to save the changes and leave the YaST sound module.To change the configuration of an individual sound card (for experts only!), select the sound card entry in the
dialog and click .This takes you to the
where you can fine-tune several parameters. For more information, click .To adjust the volume of an already configured sound card or to test the sound card, select the sound card entry in the
dialog and click . Select the respective menu item.
The YaST mixer settings provide only basic options. They are intended
for troubleshooting (for example, if the test sound is not audible).
Access the YaST mixer settings from alsasound
command line
tool.
For playback of MIDI files, select
› .When a supported sound card is detected, you can install SoundFonts for playback of MIDI files:
Insert the original driver CD-ROM into your CD or DVD drive.
Select /usr/share/sfbank/creative/
.
If you have configured more than one sound card in your system you can
adjust the order of your sound cards. To set a sound card as primary
device, select the sound card in the 0
is the default device and thus used by the system and
the applications.
By default, SUSE Linux Enterprise Desktop uses the PulseAudio sound system. This is an abstraction layer that helps to mix multiple audio streams, bypassing any restrictions the hardware may have. To enable or disable the PulseAudio sound system, click › . If enabled, PulseAudio daemon is used to play sounds. Disable to use something else system-wide.
The volume and configuration of all sound cards are saved when you click
/etc/asound.state
. The ALSA
configuration data is appended to the end of the file
/etc/modprobe.d/sound
and written to
/etc/sysconfig/sound
.
YaST can be used to configure a local printer connected to your machine via USB and to set up printing with network printers. It is also possible to share printers over the network. Further information about printing (general information, technical details, and troubleshooting) is available in Book “Administration Guide”, Chapter 20 “Printer Operation”.
In YaST, click
› to start the printer module. By default it opens in the view, displaying a list of all printers that are available and configured. This is especially useful when having access to a lot of printers via the network. From here you can also and configure printers.To print from your system, CUPS must be running. In case it is not running, you are asked to start it. Answer with
, or you cannot configure printing. In case CUPS is not started at boot time, you will also be asked to enable this feature. It is recommended to say , otherwise CUPS would need to be started manually after each reboot.Usually a USB printer is automatically detected. There are two possible reasons it is not automatically detected:
The USB printer is switched off.
Communication between printer and computer is not possible. Check the cable and the plugs to make sure that the printer is properly connected. If this is the case, the problem may not be printer-related, but rather a USB-related problem.
Configuring a printer is a three-step process: specify the connection type, choose a driver, and name the print queue for this setup.
For many printer models, several drivers are available. When configuring the
printer, YaST defaults to those marked recommended
as a
general rule. Normally it is not necessary to change the driver. However, if
you want a color printer to print only in black and white, you can use a driver that does not support color printing. If you experience performance problems with a PostScript printer
when printing graphics, try to switch from a PostScript driver to a
PCL driver (provided your printer understands PCL).
If no driver for your printer is listed, try to select a generic driver with an appropriate standard language from the list. Refer to your printer's documentation to find out which language (the set of commands controlling the printer) your printer understands. If this does not work, refer to Section 15.3.1.1, “Adding Drivers with YaST” for another possible solution.
A printer is never used directly, but always through a print queue. This ensures that simultaneous jobs can be queued and processed one after the other. Each print queue is assigned to a specific driver, and a printer can have multiple queues. This makes it possible to set up a second queue on a color printer that prints black and white only, for example. Refer to Book “Administration Guide”, Chapter 20 “Printer Operation”, Section 20.1 “The CUPS Workflow” for more information about print queues.
Start the YaST printer module with
› .In the
screen click .
If your printer is already listed under Specify the
Connection
, proceed with the next step. Otherwise, try to
or start the .
In the text box under Find and Assign a Driver
enter
the vendor name and the model name and click .
Choose a driver that matches your printer. It is recommended to choose the driver listed first. If no suitable driver is displayed:
Check your search term.
Broaden your search by clicking
.Add a driver as described in Section 15.3.1.1, “Adding Drivers with YaST”.
Specify the Default paper size
.
In the
field, enter a unique name for the print queue.The printer is now configured with the default settings and ready to use. Click
to return to the view. The newly configured printer is now visible in the list of printers.Not all printer drivers available for SUSE Linux Enterprise Desktop are installed by default. If no suitable driver is available in the dialog when adding a new printer install a driver package containing drivers for your printers:
Start the YaST printer module with
› .In the
screen, click .
In the Find and Assign a Driver
section, click
.
Choose one or more suitable driver packages from the list. Do not specify the path to a printer description file.
Choose
and confirm the package installation.To directly use these drivers, proceed as described in Procedure 15.3, “Adding a New Printer”.
PostScript printers do not need printer driver software. PostScript printers need only a PostScript Printer Description (PPD) file which matches the particular model. PPD files are provided by the printer manufacturer.
If no suitable PPD file is available in the
dialog when adding a PostScript printer, install a PPD file for your printer:Several sources for PPD files are available. It is recommended to first try additional driver packages that are shipped with SUSE Linux Enterprise Desktop but not installed by default (see below for installation instructions). If these packages do not contain suitable drivers for your printer, get PPD files directly from your printer vendor or from the driver CD of a PostScript printer. For details, see Book “Administration Guide”, Chapter 20 “Printer Operation”, Section 20.8.2 “No Suitable PPD File Available for a PostScript Printer”. Alternatively, find PPD files at http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/databaseintro, the “OpenPrinting.org printer database”. When downloading PPD files from OpenPrinting, keep in mind that it always shows the latest Linux support status, which is not necessarily met by SUSE Linux Enterprise Desktop.
Start the YaST printer module with
› .In the
screen, click .
In the Find and Assign a Driver
section, click
.
Enter the full path to the PPD file into the text box under Make
a Printer Description File Available
.
Click Add New Printer
Configuration
screen.
To directly use this PPD file, proceed as described in Procedure 15.3, “Adding a New Printer”.
By editing an existing configuration for a printer you can change basic settings such as connection type and driver. It is also possible to adjust the default settings for paper size, resolution, media source, etc. You can change identifiers of the printer by altering the printer description or location.
Start the YaST printer module with
› .In the
screen, choose a local printer configuration from the list and click .Change the connection type or the driver as described in Procedure 15.3, “Adding a New Printer”. This should only be necessary in case you have problems with the current configuration.
Optionally, make this printer the default by checking
.
Adjust the default settings by clicking +
sign. Change the default by
clicking an option. Apply your changes with .
Network printers are not detected automatically. They must be configured manually using the YaST printer module. Depending on your network setup, you can print to a print server (CUPS, LPD, SMB, or IPX) or directly to a network printer (preferably via TCP). Access the configuration view for network printing by choosing
from the left pane in the YaST printer module.In a Linux environment CUPS is usually used to print via the network. The simplest setup is to only print via a single CUPS server which can directly be accessed by all clients. Printing via more than one CUPS server requires a running local CUPS daemon that communicates with the remote CUPS servers.
CUPS servers announce their print queues over the network either via the
traditional CUPS browsing protocol or via Bonjour/DNS-SD. Clients need
to browse these lists, so users can select specific printers to
send their print jobs to. To browse network print queues, the
service cups-browsed
provided by
the package
cups-filters-cups-browsed
must run on all clients that print via CUPS
servers. cups-browsed
is started
automatically when configuring network printing with YaST.
In case browsing does not work after having started
cups-browsed
, the CUPS server(s)
probably announce the network print queues via Bonjour/DNS-SD. In this
case you need to additionally install the package
avahi
and start the associated
service with sudo systemctl start avahi-daemon
on all
clients.
Start the YaST printer module with
› .From the left pane, launch the
screen.Check
and specify the name or IP address of the server.Click
to make sure you have chosen the correct name or IP address.Click
to return to the screen. All printers available via the CUPS server are now listed.Start the YaST printer module with
› .From the left pane, launch the
screen.Check
.
Under General Settings
specify which servers to use.
You may accept connections from all networks available or from specific
hosts. If you choose the latter option, you need to specify the host
names or IP addresses.
Confirm by clicking
and then when asked to start a local CUPS server. After the server has started YaST will return to the screen. Click to see the printers detected so far. Click this button again, in case more printers are available.If your network offers print services via print servers other than CUPS, start the YaST printer module with
› and launch the screen from the left pane. Start the and choose the appropriate . Ask your network administrator for details on configuring a network printer in your environment.
You can configure a USB or SCSI scanner with YaST. The
sane-backends
package contains
hardware drivers and other essentials needed to use a scanner. If you own
an HP All-In-One device, see Section 15.4.1, “Configuring an HP All-In-One Device”,
instructions on how to configure a network scanner are available at
Section 15.4.3, “Scanning over the Network”.
Connect your USB or SCSI scanner to your computer and turn it on.
Start YaST and select
› . YaST builds the scanner database and tries to detect your scanner model automatically.If a USB or SCSI scanner is not properly detected, try
› .To activate the scanner select it from the list of detected scanners and click
.Choose your model form the list and click
and .Use
› to make sure you have chosen the correct driver.Leave the configuration screen with
.An HP All-In-One device can be configured with YaST even if it is made available via the network. If you own a USB HP All-In-One device, start configuring as described in Procedure 15.9, “Configuring a USB or SCSI Scanner”. If it is detected properly and the succeeds, it is ready to use.
If your USB device is not properly detected, or your HP All-In-One device is connected to the network, run the HP Device Manager:
Start YaST and select
› . YaST loads the scanner database.Start the HP Device Manager with
› and follow the on-screen instructions. After having finished the HP Device Manager, the YaST scanner module automatically restarts the auto detection.Test it by choosing
› .Leave the configuration screen with
.SUSE Linux Enterprise Desktop allows the sharing of a scanner over the network. To do so, configure your scanner as follows:
Configure the scanner as described in Section 15.4, “Setting Up a Scanner”.
Choose
› .Enter the host names of the clients (separated by a comma) that should be allowed to use the scanner under
› and leave the configuration dialog with .To use a scanner that is shared over the network, proceed as follows:
Start YaST and select
› .Open the network scanner configuration menu by
› .Enter the host name of the machine the scanner is connected to under
›Leave with
. The network scanner is now listed in the Scanner Configuration window and is ready to use.Use YaST's software management module to search for software components you want to add or remove. YaST resolves all dependencies for you. To install packages not shipped with the installation media, add software repositories to your setup and let YaST manage them. Keep your system up-to-date by managing software updates with the update applet.
Change the software collection of your system with the YaST Software Manager. This YaST module is available in two flavors: a graphical variant for X Window and a text-based variant to be used on the command line. The graphical flavor is described here—for details on the text-based YaST, see Book “Administration Guide”, Chapter 5 “YaST in Text Mode”.
When installing, updating or removing packages, any changes in the Software Manager are only applied after clicking
or . YaST maintains a list with all actions, allowing you to review and modify your changes before applying them to the system.The following terms are important for understanding installing and removing software in SUSE Linux Enterprise Desktop.
A local or remote directory containing packages, plus additional information about these packages (package metadata).
A short name for a repository (called Alias
within
Zypper and within YaST). It can be
chosen by the user when adding a repository and must be unique.
Each repository provides files describing content of the repository (package names, versions, etc.). These repository description files are downloaded to a local cache that is used by YaST.
Represents a whole product, for example SUSE® Linux Enterprise Desktop.
A pattern is an installable group of packages dedicated to a certain
purpose. For example, the Laptop
pattern
contains all packages that are needed in a mobile computing environment.
Patterns define package dependencies (such as required or recommended
packages) and come with a preselection of packages marked for
installation. This ensures that the most important packages needed for a
certain purpose are available on your system after installation of the
pattern. If necessary, you can manually select or deselect
packages within a pattern.
A package is a compressed file in rpm
format that
contains the files for a particular program.
A patch consists of one or more packages and may be applied by means of delta RPMs. It may also introduce dependencies to packages that are not installed yet.
A generic term for product, pattern, package or patch. The most commonly used type of resolvable is a package or a patch.
A delta RPM consists only of the binary diff between two defined versions of a package, and therefore has the smallest download size. Before being installed, the full RPM package is rebuilt on the local machine.
Certain packages are dependent on other packages, such as shared
libraries. In other terms, a package may require
other
packages—if the required packages are not available, the package
cannot be installed. In addition to dependencies (package requirements)
that must be fulfilled, some packages recommend
other
packages. These recommended packages are only installed if they are
actually available, otherwise they are ignored and the package
recommending them is installed nevertheless.
If you skipped registration during installation or want to re-register your
system, you can register the system at any time. Use the YaST module
Product Registration or the command line tool
SUSEConnect
.
To register the system, start YaST and switch to
, then .By default the system is registered with the SUSE Customer Center. If your organization provides local registration servers, you can either choose one from the list of auto-detected servers or provide the URL manually.
To register from the command line, use the command
tux >
sudo
SUSEConnect -r REGISTRATION_CODE -e EMAIL_ADDRESS
Replace REGISTRATION_CODE with the registration code you received with your copy of SUSE Linux Enterprise Server. Replace EMAIL_ADDRESS with the e-mail address associated with the SUSE account you or your organization uses to manage subscriptions.
To register with a local registration server, also provide the URL to the server:
tux >
sudo
SUSEConnect -r REGISTRATION_CODE -e EMAIL_ADDRESS --url "URL"
Start the software manager from the
by choosing › .The YaST software manager can install packages or patterns from all currently enabled repositories. It offers different views and filters to make it easier to find the software you are searching for. The
view is the default view of the window. To change view, click and select one of the following entries from the drop-down box. The selected view opens in a new tab.Lists all patterns available for installation on your system.
Lists all packages sorted by groups such as
, , or .A filter to list all packages needed to add a new system language.
A filter to list packages by repository. To select more than one repository, hold the Ctrl key while clicking repository names. The “pseudo repository” lists all packages currently installed.
Shows which packages belong to a certain module or extension. Select an
entry (for example, Basesystem
or High
Availability
) to display a list of packages that
belong to this module or extension.
Lets you search for a package according to certain criteria. Enter a search term and press Enter. Refine your search by specifying where to and by changing the . For example, if you do not know the package name but only the name of the application that you are searching for, try including the package in the search process.
If you have already selected packages for installation, update or removal, this view shows the changes that will be applied to your system when you click Shift–F1 for details on the status flags.
. To filter for packages with a certain status in this view, activate or deactivate the respective check boxes. PressTo list all packages that do not belong to an active repository, choose
› › and then choose › . This is useful, for example, if you have deleted a repository and want to make sure no packages from that repository remain installed.Certain packages are dependent on other packages, such as shared libraries. On the other hand, some packages cannot coexist with others on the system. If possible, YaST automatically resolves these dependencies or conflicts. If your choice results in a dependency conflict that cannot be automatically solved, you need to solve it manually as described in Section 16.3.4, “Package Dependencies”.
When removing any packages, by default YaST only removes the selected packages. If you want YaST to also remove any other packages that become unneeded after removal of the specified package, select
› from the main menu.Search for packages as described in Section 16.3.1, “Views for Searching Packages or Patterns”.
The packages found are listed in the right pane. To install a package or remove it, right-click it and choose Shift–F1 for help.
or . If the relevant option is not available, check the package status indicated by the symbol in front of the package name—pressTo apply an action to all packages listed in the right pane, go to the main menu and choose an action from
› .To install a pattern, right-click the pattern name and choose
.It is not possible to remove a pattern. Instead, select the packages of a pattern you want to remove and mark them for removal.
To select more packages, repeat the steps mentioned above.
Before applying your changes, you can review or modify them by clicking
› . By default, all packages that will change status, are listed.To revert the status for a package, right-click the package and select one of the following entries:
if the package was scheduled to be deleted or updated, or if it was scheduled for installation. To abandon all changes and quit the Software Manager, click and .When you are finished, click
to apply your changes.In case YaST found dependencies on other packages, a list of packages that have additionally been chosen for installation, update or removal is presented. Click
to accept them.After all selected packages are installed, updated or removed, the YaST Software Manager automatically terminates.
Installing source packages with YaST Software Manager is not possible at
the moment. Use the command line tool zypper
for this
purpose. For more information, see
Book “Administration Guide”, Chapter 6 “Managing Software with Command Line Tools”, Section 6.1.3.5 “Installing or Downloading Source Packages”.
Instead of updating individual packages, you can also update all installed packages or all packages from a certain repository. When mass updating packages, the following aspects are generally considered:
priorities of the repositories that provide the package,
architecture of the package (for example, AMD64/Intel 64),
version number of the package,
package vendor.
Which of the aspects has the highest importance for choosing the update candidates depends on the respective update option you choose.
To update all installed packages to the latest version, choose
› › from the main menu.All repositories are checked for possible update candidates, using the following policy: YaST first tries to restrict the search to packages with the same architecture and vendor like the installed one. If the search is positive, the “best” update candidate from those is selected according to the process below. However, if no comparable package of the same vendor can be found, the search is expanded to all packages with the same architecture. If still no comparable package can be found, all packages are considered and the “best” update candidate is selected according to the following criteria:
Repository priority: Prefer the package from the repository with the highest priority.
If more than one package results from this selection, choose the one with the “best” architecture (best choice: matching the architecture of the installed one).
If the resulting package has a higher version number than the installed one, the installed package will be updated and replaced with the selected update candidate.
This option tries to avoid changes in architecture and vendor for the installed packages, but under certain circumstances, they are tolerated.
If you choose
› › instead, the same criteria apply but any candidate package found is installed unconditionally. Thus, choosing this option might actually lead to downgrading some packages.To make sure that the packages for a mass update derive from a certain repository:
Choose the repository from which to update as described in Section 16.3.1, “Views for Searching Packages or Patterns” .
On the right hand side of the window, click
. This explicitly allows YaST to change the package vendor when replacing the packages.When you proceed with
, all installed packages will be replaced by packages deriving from this repository, if available. This may lead to changes in vendor and architecture and even to downgrading some packages.To refrain from this, click
. Note that you can only cancel this until you click the button.Before applying your changes, you can review or modify them by clicking
› . By default, all packages that will change status, are listed.If all options are set according to your wishes, confirm your changes with
to start the mass update.Most packages are dependent on other packages. If a package, for example, uses a shared library, it is dependent on the package providing this library. On the other hand, some packages cannot coexist, causing a conflict (for example, you can only install one mail transfer agent: sendmail or postfix). When installing or removing software, the Software Manager makes sure no dependencies or conflicts remain unsolved to ensure system integrity.
In case there exists only one solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved manually. If solving a conflict involves a vendor or architecture change, it also needs to be solved manually. When clicking
to apply any changes in the Software Manager, you get an overview of all actions triggered by the automatic resolver which you need to confirm.By default, dependencies are automatically checked. A check is performed every time you change a package status (for example, by marking a package for installation or removal). This is generally useful, but can become exhausting when manually resolving a dependency conflict. To disable this function, go to the main menu and deactivate
› . Manually perform a dependency check with › . A consistency check is always performed when you confirm your selection with .To review a package's dependencies, right-click it and choose
. A map showing the dependencies opens. Packages that are already installed are displayed in a green frame.Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens,
the Software Manager, all your changes and start again.In addition to the hard dependencies required to run a program (for example a certain library), a package can also have weak dependencies, that add for example extra functionality or translations. These weak dependencies are called package recommendations.
The way package recommendations are handled has slightly changed starting with SUSE Linux Enterprise Desktop 12 SP1. Nothing has changed when installing a new package—recommended packages are still installed by default.
Prior to SUSE Linux Enterprise Desktop 12 SP1, missing recommendations for already installed
packages were installed automatically. Now these packages will no longer
be installed automatically. To switch to the old default, set
PKGMGR_REEVALUATE_RECOMMENDED="yes"
in
/etc/sysconfig/yast2
. To install all missing
recommendations for already installed packages, start › and choose › .
To disable the installation of recommended packages when installing new
packages, deactivate --no-recommends.
To install third-party software, add software repositories to your system. By default, the product repositories such as SUSE Linux Enterprise Desktop-DVD 15 SP1 and a matching update repository are automatically configured after you have registered your system. For more information about registration, see Section 4.6, “Registration” or Book “Upgrade Guide”, Chapter 4 “Upgrading Offline”, Section 4.7 “Registering Your System”. Depending on the initially selected product, an additional repository containing translations, dictionaries, etc. might also be configured.
To manage repositories, start YaST and select
› . The dialog opens. Here, you can also manage subscriptions to so-called by changing the at the right corner of the dialog to . A Service in this context is a (RIS) that can offer one or more software repositories. Such a Service can be changed dynamically by its administrator or vendor.Each repository provides files describing content of the repository (package names, versions, etc.). These repository description files are downloaded to a local cache that is used by YaST. To ensure their integrity, software repositories can be signed with the GPG Key of the repository maintainer. Whenever you add a new repository, YaST offers the ability to import its key.
Before adding external software repositories to your list of repositories, make sure this repository can be trusted. SUSE is not responsible for any problems arising from software installed from third-party software repositories.
You can either add repositories from DVD/CD, removable mass storage devices (such as flash disks), a local directory, an ISO image or a network source.
To add repositories from the
dialog in YaST proceed as follows:Click
.Select one of the options listed in the dialog:
To scan your network for installation servers announcing their services via SLP, select
and click .To add a repository from a removable medium, choose the relevant option and insert the medium or connect the USB device to the machine, respectively. Click
to start the installation.For the majority of repositories, you will be asked to specify the path (or URL) to the media after selecting the respective option and clicking
. Specifying a is optional. If none is specified, YaST will use the product name or the URL as repository name.The option
is activated by default. If you deactivate the option, YaST will automatically download the files later, if needed.Depending on the repository you have added, you may be prompted to import the repository's GPG key or asked to agree to a license.
After confirming these messages, YaST will download and parse the metadata. It will add the repository to the list of
.If needed, adjust the repository Section 16.4.2, “Managing Repository Properties”.
as described inConfirm your changes with
to close the configuration dialog.After having successfully added the repository, the software manager starts and you can install packages from this repository. For details, refer to Chapter 16, Installing or Removing Software.
The
overview of the lets you change the following repository properties:The repository status can either be
or . You can only install packages from repositories that are enabled. To turn a repository off temporarily, select it and deactivate . You can also double-click a repository name to toggle its status. To remove a repository completely, click .When refreshing a repository, its content description (package names, versions, etc.) is downloaded to a local cache that is used by YaST. It is sufficient to do this once for static repositories such as CDs or DVDs, whereas repositories whose content changes often should be refreshed frequently. The easiest way to keep a repository's cache up-to-date is to choose
. To do a manual refresh click and select one of the options.
Packages from remote repositories are downloaded before being installed.
By default, they are deleted upon a successful installation. Activating
/etc/zypp/zypp.conf
, by default it is
/var/cache/zypp/packages
.
The 1
and 200
, with
1
being the highest priority and
200
the lowest priority. Any new repositories that are
added with YaST get a priority of 99
by default. If
you do not care about a priority value for a certain repository, you can
also set the value to 0
to apply the default priority
to that repository (99
). If a package is available in
more than one repository, then the repository with the highest priority
takes precedence. This is useful to avoid downloading
packages unnecessarily from the Internet by giving a local repository
(for example, a DVD) a higher priority.
The repository with the highest priority takes precedence in any case. Therefore, make sure that the update repository always has the highest priority, otherwise you might install an outdated version that will not be updated until the next online update.
To change a repository name or its URL, select it from the list with a single-click and then click
.To ensure their integrity, software repositories can be signed with the GPG Key of the repository maintainer. Whenever you add a new repository, YaST offers to import its key. Verify it as you would do with any other GPG key and make sure it does not change. If you detect a key change, something might be wrong with the repository. Disable the repository as an installation source until you know the cause of the key change.
To manage all imported keys, click
in the dialog. Select an entry with the mouse to show the key properties at the bottom of the window. , or keys with a click on the respective buttons.SUSE offers a continuous stream of software security patches and updates for your product. They can be installed using tools available with your desktop or by running the YaST Online Update module. This section describes how to update the system from the GNOME desktop using the .
Contrary to the YaST Online Update module, the GNOME
not only offers to install patches from the update repositories, but also new versions of packages that are already installed. (Patches fix security issues or malfunctions; the functionality and version number is usually not changed. New versions of a package increase the version number and usually add functionality or introduce major changes).Whenever new patches or package updates are available, GNOME shows a notification in the notification area or on the lock screen.
To configure the notification settings for the
, start GNOME and choose › .
To install the patches and updates, click the notification message. This
opens the GNOME package
U
and choosing .
Updates are sorted into four categories:
Fix severe security hazards and should always be installed.
Fix issues that could compromise your computer. Installing them is strongly recommended.
Fix non-security relevant issues or provide enhancements.
New versions of packages that are installed.
All available updates are preselected for installation. If you do not want to install all updates, deselect unwanted updates first. It is strongly recommended to always install all security and recommended updates.
To get detailed information on an update, click its title and then
. The information will be displayed in a box beneath the package list.Click
to start the installation.Some updates may require to restart the machine or to log out. Check the message that is displayed after the installation for instructions.
In addition to the GNOME
, GNOME provides which has the following functionality:Install, update, and remove software delivered as an RPM via PackageKit
Install, update, and remove software delivered as a Flatpak
Install, update, and remove GNOME shell extensions (https://extensions.gnome.org)
Update firmware for hardware devices using Linux Vendor Firmware Service (LVFS, https://fwupd.org)
In addition to this,
provides screenshots, ratings and reviews for software.SUSE Linux Enterprise Desktop:
has the following differences to other tools provided onUnlike YaST or Zypper, for installing software packaged as an RPM,
is restricted to software that provides AppStream metadata. This includes most desktop applications.While the GNOME
updates packages within the running system (forcing you to restart the respective applications), downloads the updates but only applies them at the next reboot of the system.Modules and extensions add parts or functionality to the system. This chapter covers their installation, scope, support status and lifecycle.
Modules are fully supported parts of SUSE Linux Enterprise Desktop with a different life cycle and update timeline. They are a set of packages, have a clearly defined scope and are delivered via online channel only. For a list of modules, their dependencies and lifecycles see https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/#Intro.ModuleExtensionRelated.
Extensions, such as the SUSE Linux Enterprise Workstation Extension or the High Availability Extension, add functionality to the system and require an own registration key that is liable for costs. Extensions are delivered via online channel or physical media. Registering at the SUSE Customer Center or a local registration server is a prerequisite for subscribing to the online channels. The Package Hub (Section 17.3, “SUSE Package Hub”) extension is an exception which does not require a registration key and is not covered by SUSE support agreements. Some extensions do require a registration key with one base product but not with another, because YaST will automatically register them with their base product's key.
A list of modules and extensions for your product is available after having registered your system at SUSE Customer Center or a local registration server. If you skipped the registration step during the installation, you can register your system at any time using the For details, refer to Book “Upgrade Guide”, Chapter 4 “Upgrading Offline”, Section 4.7 “Registering Your System”.
module in YaST.
Some add-on products are also provided by third parties, for example,
binary-only drivers that are needed by certain hardware to function
properly. If you have such hardware, refer to the release notes for more
information about availability of binary drivers for your system. The
release notes are available from
https://www.suse.com/releasenotes/,
from YaST or from /usr/share/doc/release-notes/
in
your installed system.
As of SUSE Linux Enterprise 12, SUSE Linux Enterprise Desktop is not only available as a separate product, but also as a Workstation Extension for SUSE Linux Enterprise Server. If you register at the SUSE Customer Center, the Workstation Extension can be selected for installation. Note that installing it requires a valid registration key.
The following procedure requires that you have registered your system with SUSE Customer Center, or a local registration server. When registering your system, you will see a list of extensions and modules immediately after having completed Step 5 of Book “Upgrade Guide”, Chapter 4 “Upgrading Offline”, Section 4.7 “Registering Your System”. In that case, skip the next steps and proceed with Step 2.
To view already installed add-ons, start YaST and select
›Start YaST and select
› .YaST connects to the registration server and displays a list of
.The amount of available extensions and modules depends on the registration server. A local registration server may only offer update repositories and no additional extensions.
Click an entry to see its description.
Select one or multiple entries for installation by activating their check marks.
Click
to proceed.Depending on the repositories to be added for the extension or module, you may be prompted to import the repository's GPG key or asked to agree to a license.
After confirming these messages, YaST will download and parse the metadata. The repositories for the selected extensions will be added to your system—no additional installation sources are required.
If needed, adjust the repository Section 16.4.2, “Managing Repository Properties”.
as described inWhen installing an extension or add-on product from media, you can select various types of product media, like DVD/CD, removable mass storage devices (such as flash disks), or a local directory or ISO image. The media can also be provided by a network server, for example, via HTTP, FTP, NFS, or Samba.
Start YaST and select sudo yast2 add-on
.
The dialog will show an overview of already installed add-on products, modules and extensions.
Choose
to install a new add-on product.In the
dialog, select the option that matches the type of medium from which you want to install:To scan your network for installation servers announcing their services via SLP, select
and click .To add a repository from a removable medium, choose the relevant option and insert the medium or connect the USB device to the machine, respectively. Click
to start the installation.For most media types, you will prompted to specify the path (or URL) to the media after selecting the respective option and clicking
. Specifying a is optional. If none is specified, YaST will use the product name or the URL as the repository name.The option
is activated by default. If you deactivate the option, YaST will automatically download the files later, if needed.Depending on the repository you have added, you may be prompted to import the repository's GPG key or asked to agree to a license.
After confirming these messages, YaST will download and parse the metadata. It will add the repository to the list of
.If needed, adjust the repository Section 16.4.2, “Managing Repository Properties”.
as described inConfirm your changes with
to close the configuration dialog.After having successfully added the repository for the add-on media, the software manager starts and you can install packages. For details, refer to Chapter 16, Installing or Removing Software.
In the list of Available Extensions and Modules you find the SUSE Package Hub. It is available without any additional fee. It provides a large set of additional community packages for SUSE Linux Enterprise that can easily be installed but are not supported by SUSE.
More information about SUSE Package Hub and how to contribute is available at https://packagehub.suse.com/
Be aware that packages provided in the SUSE Package Hub are not officially supported by SUSE. SUSE only provides support for enabling the Package Hub repository and help with installation or deployment of the RPM packages.
SUSE Linux Enterprise Desktop supports the parallel installation of multiple kernel versions. When installing a second kernel, a boot entry and an initrd are automatically created, so no further manual configuration is needed. When rebooting the machine, the newly added kernel is available as an additional boot parameter.
Using this functionality, you can safely test kernel updates while being able to always fall back to the proven former kernel. To do this, do not use the update tools (such as the YaST Online Update or the updater applet), but instead follow the process described in this chapter.
Be aware that you lose your entire support entitlement for the machine when installing a self-compiled or a third-party kernel. Only kernels shipped with SUSE Linux Enterprise Desktop and kernels delivered via the official update channels for SUSE Linux Enterprise Desktop are supported.
It is recommended to check your boot loader configuration after having installed another kernel to set the default boot entry of your choice. See Book “Administration Guide”, Chapter 14 “The Boot Loader GRUB 2”, Section 14.3 “Configuring the Boot Loader with YaST” for more information.
Installing multiple versions of a software package (multiversion support) is enabled by default from SUSE Linux Enterprise Server 12. To verify this setting, proceed as follows:
Open /etc/zypp/zypp.conf
with the editor of your
choice as root
.
Search for the string multiversion
. If multiversion is
enabled for all kernel packages capable of this feature, the following
line appears uncommented:
multiversion = provides:multiversion(kernel)
To restrict multiversion support to certain kernel flavors, add the
package names as a comma-separated list to the
multiversion
option in
/etc/zypp/zypp.conf
—for example
multiversion = kernel-default,kernel-default-base,kernel-source
Save your changes.
Make sure that required vendor provided kernel modules (Kernel Module Packages) are also installed for the new updated kernel. The kernel update process will not warn about eventually missing kernel modules because package requirements are still fulfilled by the old kernel that is kept on the system.
When frequently testing new kernels with multiversion support enabled, the
boot menu quickly becomes confusing. Since a /boot
partition usually has limited space you also might run into trouble with
/boot
overflowing. While you can delete unused kernel
versions manually with YaST or Zypper (as described below), you can also
configure libzypp
to automatically
delete kernels no longer used. By default no kernels are deleted.
Open /etc/zypp/zypp.conf
with the editor of your
choice as root
.
Search for the string multiversion.kernels
and
activate this option by uncommenting the line. This option takes a
comma-separated list of the following values:
4.4.126-48
:
keep the kernel with the specified version number
latest
:
keep the kernel with the highest version number
latest-N
:
keep the kernel with the Nth highest version number
running
:
keep the running kernel
oldest
:
keep the kernel with the lowest version number (the one that was
originally shipped with SUSE Linux Enterprise Desktop)
oldest+N
.
keep the kernel with the Nth lowest version number
Here are some examples
multiversion.kernels = latest,running
Keep the latest kernel and the one currently running. This is similar to not enabling the multiversion feature, except that the old kernel is removed after the next reboot and not immediately after the installation.
multiversion.kernels = latest,latest-1,running
Keep the last two kernels and the one currently running.
multiversion.kernels = latest,running,4.4.126-48
Keep the latest kernel, the one currently running, and 4.4.126-48.
Unless you are using a special setup, always keep the
kernel marked running
.
If you do not keep the running kernel, it will be deleted when updating the kernel. In turn, this means that all of the running kernel's modules are also deleted and cannot be loaded anymore.
If you decide not to keep the running kernel, always reboot immediately after a kernel upgrade to avoid issues with modules.
You want to make sure that an old kernel will only be deleted after the system has rebooted successfully with the new kernel.
Change the following line in /etc/zypp/zypp.conf
:
multiversion.kernels = latest,running
The previous parameters tell the system to keep the latest kernel and the running one only if they differ.
You want to keep one or more kernel versions to have one or more “spare” kernels.
This can be useful if you need kernels for testing. If something goes wrong (for example, your machine does not boot), you still can use one or more kernel versions which are known to be good.
Change the following line in /etc/zypp/zypp.conf
:
multiversion.kernels = latest,latest-1,latest-2,running
When you reboot your system after the installation of a new kernel, the
system will keep three kernels: the current kernel (configured as
latest,running
) and its two immediate predecessors
(configured as latest-1
and latest-2
).
You make regular system updates and install new kernel versions. However, you are also compiling your own kernel version and want to make sure that the system will keep them.
Change the following line in /etc/zypp/zypp.conf
:
multiversion.kernels = latest,3.12.28-4.20,running
When you reboot your system after the installation of a new kernel, the
system will keep two kernels: the new and running kernel (configured as
latest,running
) and your self-compiled kernel
(configured as 3.12.28-4.20
).
You can install or remove multiple kernels with YaST:
Start YaST and open the software manager via
› .List all packages capable of providing multiple versions by choosing
› › .Select a package and open its
tab in the bottom pane on the left.To install a package, click the check box next to it. A green check mark indicates it is selected for installation.
To remove an already installed package (marked with a white check mark),
click the check box next to it until a red X
indicates it is
selected for removal.
Click
to start the installation.
You can install or remove multiple kernels with zypper
:
Use the command zypper se -s 'kernel*'
to display a
list of all kernel packages available:
S | Name | Type | Version | Arch | Repository --+----------------+------------+-----------------+--------+------------------- v | kernel-default | package | 2.6.32.10-0.4.1 | x86_64 | Alternative Kernel i | kernel-default | package | 2.6.32.9-0.5.1 | x86_64 | (System Packages) | kernel-default | srcpackage | 2.6.32.10-0.4.1 | noarch | Alternative Kernel i | kernel-default | package | 2.6.32.9-0.5.1 | x86_64 | (System Packages) ...
Specify the exact version when installing:
tux >
sudo
zypper in kernel-default-2.6.32.10-0.4.1
When uninstalling a kernel, use the commands zypper se -si
'kernel*'
to list all kernels installed and zypper
rm
PACKAGENAME-VERSION to remove the
package.
During installation, you could have created a local user for your system. With the YaST module
you can add users or edit existing ones. It also lets you configure your system to authenticate users with a network server.
To administer users or groups, start YaST and click sudo
yast2 users &
from a command line.
Every user is assigned a system-wide user ID (UID). Apart from the users which can log in to your machine, there are also several system users for internal use only. Each user is assigned to one or more groups. Similar to system users, there are also system groups for internal use.
Depending on the set of users you choose to view and modify with, the dialog (local users, network users, system users), the main window shows several tabs. These allow you to execute the following tasks:
From the Section 19.2, “Managing User Accounts”. Learn about advanced options like enforcing password policies, using encrypted home directories, or managing disk quotas in Section 19.3, “Additional Options for User Accounts”.
tab create, modify, delete or temporarily disable user accounts as described inLocal users accounts are created according to the settings defined on the Section 19.4, “Changing Default Settings for Local Users”.
tab. Learn how to change the default group assignment, or the default path and access permissions for home directories inLearn how to change the group assignment for individual users in Section 19.5, “Assigning Users to Groups”.
From the Section 19.6, “Managing Groups” for information on how to do this.
tab, you can add, modify or delete existing groups. Refer toWhen your machine is connected to a network that provides user authentication methods like NIS or LDAP, you can choose between several authentication methods on the Section 19.7, “Changing the User Authentication Method”.
tab. For more information, refer toFor user and group management, the dialog provides similar functionality. You can easily switch between the user and group administration view by choosing the appropriate tab at the top of the dialog.
Filter options allow you to define the set of users or groups you want to modify: On the
or tab, click to view and edit users or groups. They are listed according to certain categories, such as or , if applicable. With › you can also set up and use a custom filter.Depending on the filter you choose, not all of the following options and functions will be available from the dialog.
YaST offers to create, modify, delete or temporarily disable user accounts. Do not modify user accounts unless you are an experienced user or administrator.
File ownership is bound to the user ID, not to the user name. After a user ID change, the files in the user's home directory are automatically adjusted to reflect this change. However, after an ID change, the user no longer owns the files they created elsewhere in the file system unless the file ownership for those files are manually modified.
In the following, learn how to set up default user accounts. For further options, refer to Section 19.3, “Additional Options for User Accounts”.
Open the YaST
dialog and click the tab.With
define the set of users you want to manage. The dialog lists users in the system and the groups the users belong to.To modify options for an existing user, select an entry and click
.To create a new user account, click
.Enter the appropriate user data on the first tab, such as
(which is used for login) and . This data is sufficient to create a new user. If you click now, the system will automatically assign a user ID and set all other values according to the default.
Activate root
and the user can read the system mail without
having to first log in as root
.
The mails sent by system services are stored in the local mailbox
/var/spool/mail/
USERNAME,
where USERNAME is the login name of the
selected user. To read e-mails, you can use the mail
command.
To adjust further details such as the user ID or the path to the user's home directory, do so on the
tab.If you need to relocate the home directory of an existing user, enter the path to the new home directory there and move the contents of the current home directory with
. Otherwise, a new home directory is created without any of the existing data.To force users to regularly change their password or set other password options, switch to Section 19.3.2, “Enforcing Password Policies”.
and adjust the options. For more details, refer toIf all options are set according to your wishes, click
.Click
to close the administration dialog and to save the changes. A newly added user can now log in to the system using the login name and password you created.Alternatively, to save all changes without exiting the
dialog, click › .It is useful to match the (local) user ID to the ID in the network. For example, a new (local) user on a laptop should be integrated into a network environment with the same user ID. This ensures that the file ownership of the files the user creates “offline” is the same as if they had created them directly on the network.
Open the YaST
dialog and click the tab.To temporarily disable a user account without deleting it, select the user from the list and click
. Activate . The user cannot log in to your machine until you enable the account again.To delete a user account, select the user from the list and click
. Choose if you also want to delete the user's home directory or to retain the data.In addition to the settings for a default user account, SUSE® Linux Enterprise Desktop offers further options. For example, options to enforce password policies, use encrypted home directories or define disk quotas for users and groups.
If you use the GNOME desktop environment you can configure Auto Login for a certain user and Passwordless Login for all users. Auto login causes a user to become automatically logged in to the desktop environment on boot. This functionality can only be activated for one user at a time. Login without password allows all users to log in to the system after they have entered their user name in the login manager.
Enabling Auto Login or Passwordless Login on a machine that can be accessed by more than one person is a security risk. Without the need to authenticate, any user can gain access to your system and your data. If your system contains confidential data, do not use this functionality.
to activate auto login or login without password, access these functions in the YaST
with › .On any system with multiple users, it is a good idea to enforce at least basic password security policies. Users should change their passwords regularly and use strong passwords that cannot easily be exploited. For local users, proceed as follows:
Open the YaST
dialog and select the tab.Select the user for which to change the password options and click
.Switch to the
tab. The user's last password change is displayed on the tab.To make the user change their password at next login, activate
.To enforce password rotation, set a
and a .To remind the user to change their password before it expires, set the number of
.To restrict the period of time the user can log in after their password has expired, change the value in
.You can also specify a certain expiration date for the complete account. Enter the
in YYYY-MM-DD format. Note that this setting is not password-related but rather applies to the account itself.For more information about the options and about the default values, click
.Apply your changes with
.To prevent system capacities from being exhausted without notification, system administrators can set up quotas for users or groups. Quotas can be defined for one or more file systems and restrict the amount of disk space that can be used and the number of inodes (index nodes) that can be created there. Inodes are data structures on a file system that store basic information about a regular file, directory, or other file system object. They store all attributes of a file system object (like user and group ownership, read, write, or execute permissions), except file name and contents.
SUSE Linux Enterprise Desktop allows usage of soft
and
hard
quotas. Additionally, grace intervals can be
defined that allow users or groups to temporarily violate their quotas by
certain amounts.
Defines a warning level at which users are informed that they are nearing their limit. Administrators will urge the users to clean up and reduce their data on the partition. The soft quota limit is usually lower than the hard quota limit.
Defines the limit at which write requests are denied. When the hard quota is reached, no more data can be stored and applications may crash.
Defines the time between the overflow of the soft quota and a warning being issued. Usually set to a rather low value of one or several hours.
To configure quotas for certain users and groups, you need to enable quota support for the respective partition in the YaST Expert Partitioner first.
In YaST, select
› and click to proceed.In the
, select the partition for which to enable quotas and click .
Click quota
package is not
already installed, it will be installed when you confirm the respective
message with .
Confirm your changes and leave the
.
Make sure the service quotaon
is
running by entering the following command:
tux >
sudo
systemctl status quotaon
It should be marked as being active
. If this is not
the case, start it with the command systemctl start
quotaon
.
Now you can define soft or hard quotas for specific users or groups and set time periods as grace intervals.
In the YaST
, select the user or the group you want to set the quotas for and click .On the
tab, select the entry and click to open the dialog.From
, select the partition to which the quota should apply.Below
, restrict the amount of disk space. Enter the number of 1 KB blocks the user or group may have on this partition. Specify a and a value.Additionally, you can restrict the number of inodes the user or group may have on the partition. Below
, enter a and .You can only define grace intervals if the user or group has already exceeded the soft limit specified for size or inodes. Otherwise, the time-related text boxes are not activated. Specify the time period for which the user or group is allowed to exceed the limits set above.
Confirm your settings with
.Click
to close the administration dialog and save the changes.Alternatively, to save all changes without exiting the
dialog, click › .
SUSE Linux Enterprise Desktop also ships command line tools like
repquota
or warnquota
. System
administrators can use these tools to control the disk usage or send e-mail
notifications to users exceeding their quota. Using
quota_nld
, administrators can also forward kernel
messages about exceeded quotas to D-BUS. For more information, refer to the
repquota
, the warnquota
and the quota_nld
man page.
When creating new local users, several default settings are used by YaST. These include, for example, the primary group and the secondary groups the user belongs to, or the access permissions of the user's home directory. You can change these default settings to meet your requirements:
Open the YaST
dialog and select the tab.To change the primary group the new users should automatically belong to, select another group from
.To modify the secondary groups for new users, add or change groups in
. The group names must be separated by commas.
If you do not want to use
/home/USERNAME
as default
path for new users' home directories, modify the .
To change the default permission modes for newly created home directories,
adjust the umask value in Book “Security and Hardening Guide”, Chapter 19 “Access Control Lists in Linux”
and to the umask
man page.
For information about the individual options, click
.Apply your changes with
.Local users are assigned to several groups according to the default settings which you can access from the Section 19.4, “Changing Default Settings for Local Users”.
dialog on the tab. In the following, learn how to modify an individual user's group assignment. If you need to change the default group assignments for new users, refer toOpen the YaST
dialog and click the tab. It lists users and the groups the users belong to.Click
and switch to the tab.To change the primary group the user belongs to, click
and select the group from the list.To assign the user additional secondary groups, activate the corresponding check boxes in the
list.Click
to apply your changes.Click
to close the administration dialog and save the changes.Alternatively, to save all changes without exiting the
dialog, click › .With YaST you can also easily add, modify or delete groups.
Open the YaST
dialog and click the tab.With
define the set of groups you want to manage. The dialog lists groups in the system.To create a new group, click
.To modify an existing group, select the group and click
.In the following dialog, enter or change the data. The list on the right shows an overview of all available users and system users which can be members of the group.
To add existing users to a new group select them from the list of possible
by checking the corresponding box. To remove them from the group deactivate the box.Click
to apply your changes.Click
to close the administration dialog and save the changes.Alternatively, to save all changes without exiting the
dialog, click › .To delete a group, it must not contain any group members. To delete a group, select it from the list and click
. Click to close the administration dialog and save the changes. Alternatively, to save all changes without exiting the dialog, click › .When your machine is connected to a network, you can change the authentication method. The following options are available:
Users are administered centrally on a NIS server for all systems in the network. For details, see Book “Security and Hardening Guide”, Chapter 4 “Using NIS”.
The System Security Services Daemon (SSSD) can locally cache user data and then allow users to use the data, even if the real directory service is (temporarily) unreachable. For details, see Book “Security and Hardening Guide”, Chapter 5 “Setting Up Authentication Clients Using YaST”, Section 5.2 “SSSD”.
SMB authentication is often used in mixed Linux and Windows networks. For details, see Book “Administration Guide”, Chapter 33 “Samba” and Book “Security and Hardening Guide”, Chapter 8 “Active Directory Support”.
To change the authentication method, proceed as follows:
Open the
dialog in YaST.Click the
tab to show an overview of the available authentication methods and the current settings.To change the authentication method, click
and select the authentication method you want to modify. This takes you directly to the client configuration modules in YaST. For information about the configuration of the appropriate client, refer to the following sections:NIS: Book “Security and Hardening Guide”, Chapter 4 “Using NIS”, Section 4.2 “Configuring NIS Clients”
LDAP: Book “Security and Hardening Guide”, Chapter 5 “Setting Up Authentication Clients Using YaST”, Section 5.1 “Configuring an Authentication Client with YaST”
Samba: Book “Administration Guide”, Chapter 33 “Samba”, Section 33.3.1 “Configuring a Samba Client with YaST”
SSSD: Book “Security and Hardening Guide”, Chapter 5 “Setting Up Authentication Clients Using YaST”, Section 5.2 “SSSD”
After accepting the configuration, return to the
overview.Click
to close the administration dialog.By default, SUSE Linux Enterprise Desktop creates user names which cannot be deleted. These users are typically defined in the Linux Standard Base. The following list provides the common user names and their purpose:
bin
, daemon
Legacy user, included for compatibility with legacy applications. New applications should no longer use this user name.
gdm
Used by GNOME Display Manager (GDM) to provide graphical logins and manage local and remote displays.
lp
Used by the Printer daemon for Common Unix Printing System (CUPS).
mail
User reserved for mailer programs like sendmail
or postfix
.
man
Used by man to access man pages.
messagebus
Used to access D-Bus (desktop bus), a software bus for inter-process
communication. Daemon is dbus-daemon
.
nobody
User that owns no files and is in no privileged groups. Nowadays, its use is limited as it is recommended by Linux Standard Base to provide a separate user account for each daemon.
nscd
Used by the Name Service Caching Daemon. This daemon is a lookup
service to improve performance with NIS and LDAP.
Daemon is nscd
.
polkitd
Used by the PolicyKit Authorization Framework which defines and
handles authorization requests for unprivileged processes.
Daemon is polkitd
.
postfix
Used by the Postfix mailer.
pulse
Used by the Pulseaudio sound server.
root
Used by the system administrator, providing all appropriate privileges.
rpc
Used by the rpcbind
command, an RPC
port mapper.
rtkit
Used by the rtkit package providing a D-Bus system service for real time scheduling mode.
salt
User for parallel remote execution provided by Salt. Daemon
is named salt-master
.
scard
User for communication with smart cards and readers. Daemon is named
pcscd
.
srvGeoClue
Used by the GeoClue D-Bus service to provide location information.
sshd
Used by the Secure Shell daemon (SSH) to ensure secured and encrypted communication over an insecure network.
statd
Used by the Network Status Monitor protocol (NSM), implemented in the
rpc.statd
daemon, to listen
for reboot notifications.
systemd-coredump
Used by the /usr/lib/systemd/systemd-coredump
command
to acquire, save and process core dumps.
systemd-timesync
Used by the /usr/lib/systemd/systemd-timesyncd
command
to synchronize the local system clock with a remote Network Time
Protocol (NTP) server.
This chapter explains how to configure language and country settings. You can change the language globally for the whole system, individually for certain users or desktops, or temporarily for single applications. Additionally, you can configure secondary languages and adjust the date and country settings.
Working in different countries or having to work in a multilingual
environment requires your computer to be set up to support this.
SUSE® Linux Enterprise Desktop can handle different locales
in parallel.
A locale is a set of parameters that defines the language and country
settings reflected in the user interface.
The main system language was selected during installation and keyboard and time zone settings were adjusted. However, you can install additional languages on your system and determine which of the installed languages should be the default.
For those tasks, use the YaST language module as described in Section 20.1, “Changing the System Language”. Install secondary languages to get optional localization if you need to start applications or desktops in languages other than the primary one.
Apart from that, the YaST timezone module allows you to adjust your country and timezone settings accordingly. It also lets you synchronize your system clock against a time server. For details, refer to Section 20.2, “Changing the Country and Time Settings”.
Depending on how you use your desktop and whether you want to switch the entire system to another language or only the desktop environment itself, there are several ways to do this:
Proceed as described in Section 20.1.1, “Modifying System Languages with YaST” and Section 20.1.2, “Switching the Default System Language” to install additional localized packages with YaST and to set the default language. Changes are effective after the next login. To ensure that the entire system reflects the change, reboot the system or close and restart all running services, applications, and programs.
Provided you have previously installed the desired language packages for your desktop environment with YaST as described below, you can switch the language of your desktop using the desktop's control center. Refer to Book “GNOME User Guide”, Chapter 3 “Customizing Your Settings”, Section 3.2 “Configuring Language Settings” for details. After the X server has been restarted, your entire desktop reflects your new choice of language. Applications not belonging to your desktop framework are not affected by this change and may still appear in the language that was set in YaST.
You can also run a single application in another language (that has already been installed with YaST). To do so, start it from the command line by specifying the language code as described in Section 20.1.3, “Switching Languages for Standard X and GNOME Applications”.
YaST knows two different language categories:
The primary language set in YaST applies to the entire system, including YaST and the desktop environment. This language is used whenever available unless you manually specify another language.
Install secondary languages to make your system multilingual. Languages installed as secondary languages can be selected manually for a specific situation. For example, use a secondary language to start an application in a certain language to do word processing in this language.
Before installing additional languages, determine which of them should be the default system language (primary language).
To access the YaST language module, start YaST and click sudo yast2 language &
from a command line.
When installing additional languages, YaST also allows you to
set different locale settings for the user root
, see Step 4. The option
determines how
the locale variables (LC_*
) in the file
/etc/sysconfig/language
are set for
root
. You can set them to the same locale as for normal
users. Alternatively, you can keep it unaffected by any language
changes, or only set the variable RC_LC_CTYPE
to
the same values as for the normal users. The
RC_LC_CTYPE
variable sets the localization for
language-specific function calls.
To add languages in the YaST language module, select the
you want to install.To make a language the default language, set it as
.Additionally, adapt the keyboard to the new primary language and adjust the time zone, if appropriate.
For advanced keyboard or time zone settings, select Section 15.1, “Setting Up Your System Keyboard Layout” and Section 20.2, “Changing the Country and Time Settings”.
› or › in YaST to start the respective dialogs. For more information, refer to
To change language settings specific to the user root
, click
.
Set
to the desired value. For more information, click .
Decide if you want to root
or not.
If your locale was not included in the list of primary languages available, try specifying it with
. However, some localization may be incomplete.Confirm your changes in the dialogs with
. If you have selected secondary languages, YaST installs the localized software packages for the additional languages.The system is now multilingual. However, to start an application in a language other than the primary one, you need to set the desired language explicitly as explained in Section 20.1.3, “Switching Languages for Standard X and GNOME Applications”.
To globally change the default language of a system, use the following procedure:
Start the YaST language module.
Select the desired new system language as
.If you switch to a different primary language, the localized software packages for the former primary language will be removed from the system. To switch the default system language but keep the former primary language as additional language, add it as
by enabling the respective check box.Adjust the keyboard and time zone options as desired.
Confirm your changes with
.After YaST has applied the changes, restart current X sessions (for example, by logging out and logging in again) to make YaST and the desktop applications reflect your new language settings.
After you have installed the respective language with YaST, you can run a single application in another language.
Start the application from the command line by using the following command:
LANG=LANGUAGE application
For example, to start f-spot in German, run
LANG=de_DE f-spot
. For other languages, use the
appropriate language code. Get a list of all language codes available with
the locale
-av
command.
Using the YaST date and time module, adjust your system date, clock and
time zone information to the area you are working in. To access the YaST
module, start YaST and click sudo yast2 timezone &
from a command line.
First, select a general region, such as
. Choose an appropriate country that matches the one you are working in, for example, .Depending on which operating systems run on your workstation, adjust the hardware clock settings accordingly:
If you run another operating system on your machine, such as Microsoft Windows*, it is likely your system does not use UTC, but local time. In this case, deactivate
.If you only run Linux on your machine, set the hardware clock to UTC and have the switch from standard time to daylight saving time performed automatically.
The switch from standard time to daylight saving time (and vice versa) can only be performed automatically when the hardware clock (CMOS clock) is set to UTC. This also applies if you use automatic time synchronization with NTP, because automatic synchronization will only be performed if the time difference between the hardware and system clock is less than 15 minutes.
Since a wrong system time can cause serious problems (missed backups, dropped mail messages, mount failures on remote file systems, etc.) it is strongly recommended to always set the hardware clock to UTC.
You can change the date and time manually or opt for synchronizing your machine against an NTP server, either permanently or only for adjusting your hardware clock.
In the YaST timezone module, click
to set date and time.Select
and enter date and time values.Confirm your changes.
Click
to set date and time.Select
.Enter the address of an NTP server, if not already populated.
Click
to get your system time set correctly.To use NTP permanently, enable
.With the Book “Administration Guide”, Chapter 31 “Time Synchronization with NTP”, Section 31.1 “Configuring an NTP Client with YaST”.
button, you can open the advanced NTP configuration. For details, seeConfirm your changes.
To adapt the operating system better to your deployment, you can create custom media for use as an appliance or live system with KIWI. KIWI can be used either on a local machine or online in SUSE Studio Express (OBS).
With KIWI, you can create Live CDs, Live DVDs, flash disks to use on Linux-supported hardware platforms and virtual disks for virtualization and cloud systems (like Xen, KVM, VMware, EC2 and more). Images created by KIWI can also be used in a PXE environment to boot from the network.
This guide does not cover topics related to KIWI in depth, as there is separate documentation available:
For more information, see the KIWI documentation at https://doc.suse.com/kiwi/ (also available in the package kiwi-doc).
SUSE Studio Express on Open Build Service can be used to create OS images online. It supports creating virtual appliances and live systems, based on either openSUSE or SUSE Linux Enterprise. For more information and documentation, see https://studioexpress.opensuse.org/.
This appendix contains the GNU Free Documentation License version 1.2.
Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or non-commercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.