Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise Server 11 SP4

6 Installation with YaST

After your hardware has been prepared for the installation of SUSE® Linux Enterprise Server as described in Part I, “Architecture Specific Installation Considerations” and after the connection with the installation system has been established, you are presented with the interface of SUSE Linux Enterprise Server's system assistant YaST. YaST guides you through the entire installation and configuration procedure.

6.1 Choosing the Installation Method

After having selected the installation medium, determine the suitable installation method and boot option that best matches your needs:

Installing from the SUSE Linux Enterprise Server Media (DVD, CD, USB)

Choose this option if you want to perform a stand-alone installation and do not want to rely on a network to provide the installation data or the boot infrastructure. The installation proceeds exactly as outlined in Section 6.2, “The Installation Workflow”.

Installing from a Network Server

Choose this option if you have an installation server available in your network or want to use an external server as the source of your installation data. This setup can be configured to boot from physical media (Floppy, CD/DVD, or hard disk) or configured to boot via network using PXE/BOOTP. Refer to Section 6.1.1, “Installing from a Network Server Using SLP”, Section 6.1.2, “Installing from a Network Source without SLP”, or Chapter 14, Remote Installation for details.

SUSE Linux Enterprise Server supports several different boot options from which you can choose, depending on the hardware available and on the installation scenario you prefer. Booting from the SUSE Linux Enterprise Server media is the most straightforward option, but special requirements might call for special setups:

Table 6.1: Boot Options

Boot Option

Description

DVD

This is the easiest boot option. This option can be used if the system has a local DVD-ROM drive that is supported by Linux.

USB Mass Storage Device

In case your machine is not equipped with an optical drive, you can boot the installation image from a USB mass storage device such as a USB stick. To create a bootable USB storage device, you need to copy either the DVD or the Mini CD iso image to the device using the dd command (the USB device must not be mounted, all data on the device will be erased):

dd if=PATH_TO_ISO_IMAGE of=USB_STORAGE_DEVICE bs=4M

dd is available on Linux and MacOS by default. A Microsoft Windows* version can be downloaded from http://www.chrysocome.net/dd.

Important
Important: Compatibility

Please note that booting from a USB Mass Storage Device is not supported on UEFI machines (this includes the complete ia64 architecture) and on the ppc64 architecture.

PXE or BOOTP

Booting over the network must be supported by the system's BIOS or firmware, and a boot server must be available in the network. This task can also be handled by another SUSE Linux Enterprise Server system. Refer to Chapter 14, Remote Installation for more information.

Hard Disk

SUSE Linux Enterprise Server installation can also be booted from the hard disk. To do this, copy the kernel (linux) and the installation system (initrd) from the directory /boot/architecture/ on the installation media to the hard disk and add an appropriate entry to the existing boot loader of a previous SUSE Linux Enterprise Server installation.

Tip
Tip: Booting from DVD on UEFI machines

amd64, em64t DVD1 can be used as a boot medium for machines equipped with UEFI (Unified Extensible Firmware Interface). Refer to your vendor's documentation for specific information. If booting fails, try to enable CSM (Compatibility Support Module) in your firmware.

6.1.1 Installing from a Network Server Using SLP

If your network setup supports OpenSLP and your network installation source has been configured to announce itself via SLP (described in Section 14.2, “Setting Up the Server Holding the Installation Sources”), boot the system, press F4 in the boot screen and select SLP from the menu.

The installation program configures the network connection with DHCP and retrieves the location of the network installation source from the OpenSLP server. If the automatic DHCP network configuration fails, you are prompted to enter the appropriate parameters manually. The installation then proceeds as described below with the exception of the network configuration step that is needed prior to adding additional repositories. This step is not needed as the network is already configured and active at this point.

6.1.2 Installing from a Network Source without SLP

If your network setup does not support OpenSLP for the retrieval of network installation sources, boot the system and press F4 in the boot screen to select the desired network protocol (NFS, HTTP, FTP, or SMB/CIFS). Provide the server's address and the path to the installation media.

The installation program automatically configures the network connection with DHCP. If this configuration fails, you are prompted to enter the appropriate parameters manually. The installation retrieves the installation data from the source specified. The installation then proceeds as described below with the exception of the network configuration step needed prior to adding additional repositories. This step is not needed as the network is already configured and active at this point.

6.2 The Installation Workflow

The SUSE Linux Enterprise Server installation is split into three main parts: preparation, installation, and configuration. During the preparation phase you configure some basic parameters such as language, time, hard disk setup and installation scope. In the non-interactive installation phase the software is installed and the system is prepared for the first boot. Upon finishing the installation the machine reboots into the newly installed system and starts the final system configuration. In this stage, network and Internet access, as well as hardware components such as printers, are set up.

6.3 IBM POWER: System Start-Up for Network Installation

For IBM POWER platforms, the system is booted (IPL, Initial Program Load) as described in Section 3.2, “Preparation”. For a network installation, SUSE Linux Enterprise Server does not show a splash screen or a boot loader command line on these systems. During the installation load the kernel manually. YaST starts with its installation screen as soon as a connection has been established to the installation system via VNC, X, or SSH. Because there is no splash screen or boot loader command line, kernel or boot parameters cannot be entered on the screen, but must be included in the kernel image using the mkzimage_cmdline utility.

Tip
Tip: IBM POWER: The Next Steps

To install, follow the description of the installation procedure with YaST starting from Section 6.8, “Welcome”.

6.4 IBM System z: System Start-Up for Installation

For IBM System z platforms, the system is booted (IPL, Initial Program Load) as described in Section 4.2.4, “IPLing the SUSE Linux Enterprise Server Installation System”. SUSE Linux Enterprise Server does not show a splash screen on these systems. During the installation, load the kernel, initrd, and parmfile manually. YaST starts with its installation screen as soon as a connection has been established to the installation system via VNC, X, or SSH. Because there is no splash screen, kernel or boot parameters cannot be entered on screen, but must be specified in a parmfile (see Section 4.4, “The parmfile—Automating the System Configuration”).

Tip
Tip: IBM System z: The Next Steps

To install, follow the description of the installation procedure with YaST starting from Section 6.8, “Welcome”.

6.5 System Start-Up for Installation

You can install SUSE Linux Enterprise Server from local installation sources, such as the SUSE Linux Enterprise Server CDs or DVD, or from network source of an FTP, HTTP, NFS, or SMB server. Any of these approaches requires physical access to the system to install as well as user interaction during the installation. The installation procedure is basically the same regardless of the installation source. Any exceptions are sufficiently highlighted in the following workflow description. For a description on how to perform non-interactive, automated installations, refer to Part IV, “Automated Installations”.

6.6 The Boot Screen on Machines Equipped with Traditional BIOS

The boot screen displays a number of options for the installation procedure. Boot from Hard Disk 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 press Enter to boot it. The relevant options are:

Installation

The normal installation mode. All modern hardware functions are enabled. In case the installation fails, see F5Kernel for boot options that disable potentially problematic functions.

Repair Installed System

Boots into the graphical repair system. More information on repairing an installed system is available in Section 36.6.4, “Recovering a Corrupted System”.

Rescue System

Starts a minimal Linux system without a graphical user interface. For more information, see Section 36.6.4.2, “Using the Rescue System”.

Check Installation Media

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.

Firmware Test

Starts a BIOS checker that validates ACPI and other parts of your BIOS.

Memory Test

Tests your system RAM using repeated read and write cycles. Terminate the test by rebooting. For more information, see Section 36.2.5, “Fails to Boot”.

The Boot Screen on Machines with a Traditional BIOS
Figure 6.1: The Boot Screen on Machines with a Traditional BIOS

Use the function keys indicated in the bar at the bottom of the screen to change the language, screen resolution, installation source or to add an additional driver from your hardware vendor:

F1Help

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.

F2Language

Select the display language and a corresponding keyboard layout for the installation. The default language is English (US).

F3Video Mode

Select various graphical display modes for the installation. Select Text Mode if the graphical installation causes problems.

F4Source

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 SLP in Chapter 23, SLP Services in the Network.

F5Kernel

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 No ACPI to install without ACPI support. No local APIC disables support for APIC (Advanced Programmable Interrupt Controllers) which may cause problems with some hardware. Safe Settings 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: Installation—ACPI Disabled or Installation—Safe Settings. Experts can also use the command line (Boot Options) to enter or change kernel parameters.

F6Driver

Press this key to notify the system that you have an optional driver update for SUSE Linux Enterprise Server. With File or URL, load drivers directly before the installation starts. If you select Yes, you are prompted to insert the update disk at the appropriate point in the installation process.

Tip
Tip: Getting Driver Update Disks

Driver updates for SUSE Linux Enterprise are provided at http://drivers.suse.com/. These drivers have been created via the Partner Linux Driver Program.

Tip
Tip: Using IPv6 during the Installation

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 bootprompt: ipv6=1 (accept IPv4 and IPv6) or ipv6only=1 (accept IPv6 only).

After starting the installation, SUSE Linux Enterprise Server loads and configures a minimal Linux system to run the installation procedure. To view the boot messages and copyright notices during this process, press Esc. On completion of this process, the YaST installation program starts and displays the graphical installer.

Tip
Tip: Installation without a Mouse

If the installer does not detect your mouse correctly, use Tab for navigation, arrow keys to scroll, and Enter to confirm a selection. Various buttons or selection fields contain a letter with an underscore. Use AltLetter to select a button or a selection directly instead of navigating there with the Tab button.

6.6.1 Providing Data to Access an SMT Server

By default, updates for SUSE Linux Enterprise Server are delivered by the Novell Customer Center. If your network provides a so called SMT 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. This information can either be entered at the boot prompt (as described here) or during the registration process as described in Section 6.16.1.4.1, “Local Registration Server”.

regurl

URL of the SMT server. This URL has a fixed format https://FQN/center/regsvc/ FQN has to be a fully qualified hostname of the SMT server. Example:

regurl=https://smt.example.com/center/regsvc/
regcert

Location of the SMT server's certificate. Specify one of the following locations:

URL

Remote location (http, https or ftp) from which the certificate can be downloaded. Example:

regcert=http://smt.example.com/smt-ca.crt
Floppy

Specifies a location on a floppy. The floppy has to be inserted at boot time, as you will not be prompted to insert it if it is missing. The value has to start with the string floppy followed by the path to the certificate. Example:

regcert=floppy/smt/smt-ca.crt
local path

Absolute path to the certificate on the local machine. Example:

regcert=/data/inst/smt/smt-ca.cert
Interactive

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
Deactivate certificate installation

Use done if either the certificate will be installed by an add-on product, or if you are using a certificate issued by an official certificate authority. Example:

regcert=done
Warning
Warning: Beware of typing errors

Make sure the values you enter are correct. If regurl has not been specified correctly, the registration of the update source will fail. If a wrong value for regcert has been entered, you will be prompted for a local path to the certificate.

In case regcert is not specified, it will default to http://FQN/smt.crt with FQN being the name of the SMT server.

6.6.2 Configuring an Alternative Data Server for supportconfig

The data that supportconfig (see Chapter 2, Gathering System Information for Support for more information) gathers is sent to the Novell 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 has to be entered at the boot prompt.

supporturl

URL of the server. The URL has the format http://FQN/Path/ FQN has to be full qualified hostname of the server, Path has to be replaced with the location on the server. Example:

supporturl=http://support.example.com/supportconfig/data/

6.7 The Boot Screen on Machines Equipped with UEFI

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, that prevents booting malicious code by only allowing signed boot loaders to be executed. See Chapter 12, UEFI (Unified Extensible Firmware Interface) for more information.

The boot manager GRUB, used to boot machines with a traditional BIOS, does not support UEFI, therefore GRUB is replaced with ELILO. If Secure Boot is enabled, a GRUB2 UEFI module is used via an ELILO compatibility layer. From an administrative and user perspective, both boot manager implementations behave the same and are referred to as ELILO in the following.

Tip
Tip: UEFI and Secure Boot are Supported by Default

The installation routine of SUSE Linux Enterprise automatically detects if the machine is equipped with UEFI. All installation sources also support Secure Boot. If an EFI system partition already exists on dual boot machines (from a Microsoft Windows 8 installation, for example), it will automatically be detected and used. Partition tables will be written as GPT on UEFI systems.

Warning
Warning: Using Non-Inbox Drivers with Secure Boot

There is no support for adding non-inbox drivers (that is, drivers that do not come with SLE) during installation with Secure Boot enabled. The signing key used for SolidDriver/PLDP is not trusted by default.

To solve this problem, it is necessary to either add the needed keys to the firmware database via firmware/system management tools before the installation or to use a bootable ISO that will enroll the needed keys in the MOK list at first boot. For more information, see Section 12.1, “Secure Boot”.

The boot screen displays a number of options for the installation procedure. Change the selected option with the arrow keys and press Enter to boot it. The relevant options are:

Installation

The normal installation mode.

Rescue System

Starts a minimal Linux system without a graphical user interface. For more information, see Section 36.6.4.2, “Using the Rescue System”.

Check Installation Media

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.

The Boot Screen on Machines with UEFI
Figure 6.2: The Boot Screen on Machines with UEFI

ELILO on SUSE Linux Enterprise Server does not support a graphical boot screen or a boot prompt. In order to add additional 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 at this time). The Installation entry will look similar to the following:

setparams 'Installation'

  set gfxpayload=keep
  echo 'Loading kernel ...'
  linuxefi /boot/x86_64/loader/linux
  echo 'Loading initial ramdisk ...'
  initrdefi /boot/x86_64/loader/initrd

Add space separated parameters to the end of the line starting with linuxefi. A list of parameters is available at https://en.opensuse.org/Linuxrc. In the following example the installation language is set to German:

linuxefi /boot/x86_64/loader/linux Language=de_DE

To boot the edited entry, press F10. If you access the machine via serial console, press Esc0.

6.8 Welcome

Start the installation of SUSE Linux Enterprise Server by choosing your language. Changing the language will automatically preselect a corresponding keyboard layout. Override this proposal by selecting a different keyboard layout from the drop-down menu. The language selected here is also used to assume a time zone for the system clock. This setting—along with the selection of secondary languages to install on your system—can be modified later in the Installation Summary, described in Section 6.14, “Installation Settings”. For information about language settings in the installed system, see Chapter 13, Changing Language and Country Settings with YaST.

Read the license agreement that is displayed beneath the language and keyboard selection thoroughly. Use License Translations... to access translations. If you agree to the terms, check I Agree to the License Terms and click Next to proceed with the installation. If you do not agree to the license agreement, you cannot install SUSE Linux Enterprise Server; click Abort to terminate the installation.

Welcome
Figure 6.3: Welcome

6.9 IBM System z: Hard Disk Configuration

When installing on IBM System z platforms, the language selection dialog is followed by a dialog to configure the attached hard disks. Select DASD, Fibre Channel Attached SCSI Disks (zFCP), or iSCSI for installation of SUSE Linux Enterprise Server. The DASD and zFCP configuration buttons are only available if the corresponding devices are attached. For instructions on how to configure iSCSI disks, refer to Section 14.1, “Installing iSCSI Target and Initiator”.

Tip
Tip: Adding DASD or zFCP Disks at a Later Stage

Adding DASD or zFCP disks is not only possible during the installation workflow, but also when the installation proposal is shown. To add disks at that stage, click Expert and scroll down. The DASD and zFCP entries are shown at the very bottom.

After adding the disks, reread the partition table. Return to the installation proposal screen and choose Partitioning then select Reread Partition Table. This updates the new partition table.

6.9.1 Configuring DASD Disks

After selecting Configure DASD Disks, an overview lists all available DASDs. To get a clearer picture of the available devices, use the entry field located above the list to specify a range of channels to display. To filter the list according to such a range, select Filter.

IBM System z: Selecting a DASD
Figure 6.4: IBM System z: Selecting a DASD

Specify the DASDs to use for the installation by selecting the corresponding entries in the list. Click Select or Deselect. Activate and make the DASDs available for the installation by selecting Perform Action › Activate. To format the DASDs, select Perform Action › Format right away or use the YaST partitioner later as described in Section 15.1, “Using the YaST Partitioner”.

6.9.2 Configuring zFCP Disks

To use zFCP disks for the SUSE Linux Enterprise Server installation, select Configure zFCP Disks in the selection dialog. This opens a dialog with a list of the zFCP disks available on the system. In this dialog, select Add to open another dialog in which to enter zFCP parameters.

To make a zFCP disk available for the SUSE Linux Enterprise Server installation, choose an available Channel Number from the drop-down list. Get WWPNs (World Wide Port Number) and Get LUNs (Logical Unit Number) return lists with available WWPNs and FCP-LUNs, respectively, to choose from. When completed, exit the zFCP dialog with Next and the general hard disk configuration dialog with Finish to continue with the rest of the configuration.

6.10 Media Check

The media check dialog only appears if you install from media created from downloaded ISOs. If you install from the original media kit, the dialog is skipped.

The media check examines the integrity of a medium. To start it, select the drive that contains the installation medium and click Start Check. The check can take some time.

To test multiple media, wait until a result message appears in the dialog before changing the medium. If the last medium checked is not the one you started the installation with, YaST prompts for the appropriate medium before continuing with the installation.

If using ISO images (for example, for installing add-on products), click Check ISO File and choose the image via the file dialog.

Warning
Warning: Failure of Media Check

If the media check fails, your medium is damaged. Do not continue the installation because installation may fail or you may loose your data. Replace the broken medium and restart the installation process.

If the media check turns out positive, click Next to continue the installation.

6.11 Installation Mode

After a system analysis (where YaST probes for storage devices and tries to find other installed systems on your machine) the available installation modes are displayed.

New installation

Select this option to start a new installation from scratch.

Update

Select this option to update an existing installation to a newer version. For more information about system update, see Chapter 7, Updating SUSE Linux Enterprise.

Repair Installed System

Choose this option to repair a damaged system that is already installed. More information is available in Section 36.6.4, “Recovering a Corrupted System”.

Installation Mode
Figure 6.5: Installation Mode

Check Include Add-On Products from Separate Media to include add-on products during the installation. An add-on product can include extensions, third-party products and drivers or additional software for your system.

Tip
Tip: Installing Product Patches from an SMT Server on Installation

In case your organization provides the update channel for SUSE Linux Enterprise Server via an SMT server, it is possible to specify this channel as an Add-On product by entering its HTTP address. As a consequence, the system will be installed with the most current packages without having to apply the updates at the end of the installation.

Click Next to proceed. If you selected to include an add-on product, proceed with Section 6.11.1, “Add-On Products”, otherwise skip the next section and advance to Section 6.12, “Clock and Time Zone”.

6.11.1 Add-On Products

Add-on products can be installed either from a local source (CD, DVD, or directory) or from a network source (HTTP, FTP, NFS, CIFS,...). When installing from a network source, you need to configure the network first (unless you are performing a network installation—in this case the existing network configuration is used). Choose Yes, Run the Network Setup and proceed as described in Section 6.11.1.1, “Network Setup”. If the add-on product is available locally, select No, Skip the Network Setup.

Click Next and specify the product source. Source types available are CD, DVD, Hard Disk, USB Mass Storage, a Local Directory or a Local ISO Image (if no network was configured). If the add-on product is available on removable media, the system automatically mounts the media and reads its contents. If the add-on product is available on hard disk, choose Hard Disk to install from an unmounted hard drive, or Local Directory/Local ISO Image to install from the local file system. Add-on products may be delivered as a repository or as a set of RPM files. In the latter case, check Plain RPM Directory. Whenever a network is available, you can choose from additional remote sources such as HTTP, SLP, FTP, etc. It is also possible to specify a URL directly.

Check Download Repository Description Files to download the files describing the repository now. If unchecked, they will be downloaded once the installation starts. Proceed with Next and insert a CD or DVD if required. Depending on the product's content it may be necessary to accept additional license agreements.

It is also possible to configure add-on products later. Using add-on products on the installed system is described in Chapter 10, Installing Add-On Products.

Tip
Tip: Driver Updates

You can also add driver update repositories via the Add-On Products dialog. Driver updates for SUSE Linux Enterprise are provided at http://drivers.suse.com/. These drivers have been created via the Partner Linux Driver Program.

6.11.1.1 Network Setup

When invoking the network setup, YaST scans for available network cards. If more than one network card is found, you must choose the card to configure from the list.

If an ethernet network adapter is not already connected, a warning will open. Make sure the network cable is plugged in and choose Yes, Use It. If your network is equipped with a DHCP server, choose Automatic Address Setup (via DHCP). To manually set up the network choose Static Address Setup and specify IP Address, Netmask, Default Gateway IP, and the DNS Server IP.

Some networks require the use of a proxy server to access the Internet. Tick the check box Use Proxy for Accessing the Internet and enter the appropriate specifications. Click Accept to perform the network setup. The installation procedure will continue with the add-on products or repositories setup as described in Section 6.11.1, “Add-On Products”.

6.12 Clock and Time Zone

In this dialog, select your region and time zone. Both are preselected according to the selected installation language. To change the preselected values, either use the map or the drop down lists for Region and Time Zone. 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.

Clock and Time Zone
Figure 6.6: Clock and Time Zone

To set up the clock, choose whether the Hardware Clock is Set to UTC. If you run another operating system on your machine, such as Microsoft Windows, it is likely your system uses local time instead. 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.

Important
Important: Set the Hardware Clock to UTC

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 syncing 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 severe 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 Change to either alter the NTP settings or to Manually set the time. See Chapter 24, Time Synchronization with NTP for more information on configuring the NTP service. When finished, click Accept to continue the installation.

Note
Note: Time Cannot be Changed on IBM System z

Since the operating system is not allowed to change time and date directly, the Change option is not available on IBM System z.

6.13 Server Base Scenario

In SUSE Linux Enterprise Server, you can choose from three base scenarios. The selected scenario affects the package selection.

Physical Machine

Choose this scenario when installing on a real machine or a fully virtualized guest.

Virtual Machine

Choose this scenario when installing a paravirtualized guest.

XEN Virtualization Host

Choose this scenario when installing on a machine that should serve as a XEN host.

Server Base Scenario
Figure 6.7: Server Base Scenario

6.14 Installation Settings

On the last step before the real installation takes place, you can alter installation settings suggested by YaST and also review the settings you made so far. Basic settings can be changed in the Overview tab, advanced options are available on the Experts tab. To modify the suggestions, either click Change and select the category to change or click on one of the headlines. After configuring any of the items presented in these dialogs, you are always returned to the Installation Settings window, which is updated accordingly.

Installation Settings
Figure 6.8: Installation Settings
Tip
Tip: Restoring the Default Settings

You can reset all changes to the defaults by clicking Change › Reset to Defaults. YaST then shows the original proposal again.

6.14.1 Partitioning (Overview)

Review and, if necessary, change the partition setup proposed by the system. Changing the partition setup either lets you partition a specific disk or, when choosing Custom Partitioning, apply your own partitioning scheme. Modifying the partition setup opens the Expert Partitioner described in Section 15.1, “Using the YaST Partitioner”.

Tip
Tip: Btrfs as a default file system

The default partitioning scheme is based on Ext3 file system. To use Btrfs as a default file system instead, click Partitioning in the Overview tab and check Use Btrfs as Default Filesystem

Note
Note: Using Minidisks in z/VM

If SUSE Linux Enterprise Server is installed on minidisks in z/VM, which reside on the same physical disk, the access path of the minidisks (/dev/disk/by-id/) is not unique but rather the ID of the physical disk. So if two or more minidisks are on the same physical disk, they all have the same ID.

To avoid problems when mounting the minidisks, always mount them either "by path" or "by UUID".

6.14.2 Booting (Expert)

IBM Z This module cannot be used to configure the boot loader (zipl) on the IBM System z platforms.

YaST 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 Server will be booted by default. Normally, you can leave these settings unchanged. If you need a custom setup, modify the proposal for your system. For information, see Section 11.2, “Configuring the Boot Loader with YaST”.

6.14.3 Software (Overview)

SUSE Linux Enterprise Server contains a number of software patterns for various application purposes. Click Software to start the pattern selection and modify the installation scope according to your needs. Select your pattern from the list and see a pattern description in the right part of the window. Each pattern contains a number of software packages needed for specific functions (e.g. Web and LAMP server or a print server). For a more detailed selection based on software packages to install, select Details 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 9, Installing or Removing Software.

Software Selection and System Tasks
Figure 6.9: Software Selection and System Tasks
Note
Note: Default Desktop

The default desktop of SUSE Linux Enterprise Server is GNOME. To install KDE, click Software and select KDE Desktop Environment from Graphical Environment.

6.14.4 Language (Overview)

Here you can change the system Language you defined in the first step of the installation. It is also possible to add additional languages. To adjust the system language settings, select Language. Select a language from the list. The primary language is used as the system language. You can also adapt keyboard layout and time zone to the primary language if the current settings differ. Details lets you modify language settings for the user root, set UTF-8 support, or further specify the language (e.g. select South African English).

Choose secondary languages to be able to switch to one of these languages at any time without having to install additional packages. For more information, see Chapter 13, Changing Language and Country Settings with YaST.

6.14.5 Add-On Products (Expert)

If you added a source for an add-on media earlier, it appears here. Add, remove, or modify add-on products here, if needed.This is the same configuration dialog as discussed earlier in Section 6.11.1, “Add-On Products”.

6.14.6 Keyboard Layout (Expert)

To change the keyboard layout, select Keyboard Layout. By default, the layout corresponds to the language chosen for installation. Select the keyboard layout from the list. Use the Test field at the bottom of the dialog to check if you can enter special characters of that layout correctly. Options to fine-tune various settings are available under Expert Mode. When finished, click Accept to return to the installation summary.

6.14.7 Time Zone (Expert)

Adjust time zone and clock settings here. Provided a network is configured, you can also set up a Network Time Protocol (NTP) client that automatically synchronizes your computer with a time server. This is the same configuration as shown earlier in Section 6.12, “Clock and Time Zone”.

6.14.8 Default Runlevel (Expert)

SUSE Linux Enterprise Server can boot to different runlevels. Normally, there should be no need to change anything here, but if necessary set the default runlevel with this dialog. Refer to Section 10.2.3, “Configuring System Services (Runlevel) with YaST” for more information about runlevel configuration.

6.14.9 System (Expert)

This dialog presents all the hardware information YaST could obtain about your computer. When called, the hardware detection routine is started. Depending on your system, this may take some time. Select any item in the list and click Details to see detailed information about the selected item. Use Save to File to save a detailed list to either the local file system or a floppy. Advanced users can also change the PCI ID setup and Kernel Settings by choosing Kernel Settings.

6.14.10 Kdump (Expert)

Using kdump, you can save a dump of the kernel (in case of a crash) to analyze what went wrong. Use this dialog to enable and configure kdump. Find detailed information at Chapter 18, kexec and kdump.

6.15 Performing the Installation

After configuring all installation settings, click Install 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 Accept to install the software package. When not agreeing to the license, click I Disagree and the software package will not be installed. In the dialog that follows, confirm with Install 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.

After the software installation has completed, the basic system is set up. Among others, Finishing the Basic Installation includes installing the boot manager, initializing fonts and more. Next YaST boots into the new Linux system to start the system configuration.

Tip
Tip: Existing SSH Host Keys

If you install SUSE Linux Enterprise Server on a machine with existing Linux installations, the installation routine automatically imports the SSH host key with the most recent access time from an existing installation.

6.15.1 IBM System z: IPLing the Installed System

In most cases, YaST automatically reboots into the installed system on the IBM System z platform. Known exceptions to this are installations wherein the boot loader resides on an FCP device in environments with LPAR on a machine older than z9 or with z/VM older than release 5.3. The boot loader gets written to the device that holds the /boot directory. If /boot is not on a separate partition, it is on the same partition as the root file system /.

In cases where an automatic reboot is not possible, YaST will show a dialog box containing information about from which device to do an IPL. Accept the shutdown option and perform an IPL after the shutdown. The procedure varies according to the type of installation:

LPAR Installation

In the IBM System z HMC, select Load, select Clear, then enter the loading address (the device address of the device holding the /boot directory with the boot loader). If using a ZFCP disk as the boot device, choose Load from SCSI and specify the load address of your FCP adapter as well as WWPN and LUN of the boot device. Now start the loading process.

z/VM Installation

Log in to the VM guest (see Example 4.5, “Configuration of a z/VM Directory” for the configuration) as LINUX1 and proceed to IPL the installed system:

IPL 151 CLEAR

151 is an example address of the DASD boot device, replace this value with the correct address.

If using a ZFCP disk as the boot device, specify both the ZFCP WWPN and LUN of the boot device before initiating the IPL. The parameter length is limited to eight characters. Longer numbers must be separated by spaces:

SET LOADDEV PORT 50050763 00C590A9 LUN 50010000 00000000

Finally, initiate the IPL:

IPL FC00

FC00 is an example address of the ZFCP adapter, replace this value with the correct address.

6.15.2 IBM System z: Connecting to the Installed System

After IPLing the installed system, establish a connection with it to complete the installation. The steps involved in this vary depending on the type of connection used at the outset.

6.15.2.1 Using VNC to Connect

A message in the 3270 terminal asks you to connect to the Linux system using a VNC client. This message is easily missed, however, because it is mixed with kernel messages and the terminal process might quit before you become aware of the message. If nothing happens for five minutes, try to initiate a connection to the Linux system using a VNC viewer.

If you connect using a Java-capable browser, enter the complete URL, consisting of the IP address of the installed system along with the port number, in the following fashion:

 http://<IP of installed system>:5801/

6.15.2.2 Using X to Connect

When IPLing the installed system, make sure that the X server used for the first phase of the installation is up and still available before booting from the DASD. YaST opens on this X server to finish the installation. Complications may arise if the system is booted up but unable to connect to the X server in a timely fashion.

6.15.2.3 Using SSH to Connect

Important
Important: IBM System z: Connecting from a Linux or UNIX System

Start SSH in an xterm. Other terminal emulators lack complete support for the text-based interface of YaST.

A message in the 3270 terminal asks you to connect to the Linux system with an SSH client. This message is easily missed, however, because it is mixed with kernel messages and the terminal process might quit before you become aware of the message.

Once the message appears, use SSH to log in to the Linux system as root. If the connection is denied or times out, wait for the login timeout to expire, then try again (this time may vary depending on server settings).

When the connection is established, execute the command /usr/lib/YaST2/startup/YaST2.ssh. Just executing the command yast does not suffice in this case.

YaST then begins completing the installation of the remaining packages and creating an initial system configuration.

6.16 Configuration of the Installed System

The system is now installed, but not yet configured for use. The hardware, the network and other services are not yet set up.

6.16.1 System Configuration

Having rebooted, the system starts the manual configuration. If the configuration fails at one of the steps of this stage, it restarts and continues from the last successful step.

6.16.1.1 Password for the System Administrator root

root is the name of the superuser, the administrator of the system. Unlike regular users, who may or may not have permission to execute administrative commands on the system, root has unlimited command capacity, for instance changing the system configuration, installing programs, and setting 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 the irretrievable loss of system files.

For verification purposes, the password for root must be entered twice. Do not forget the root password. Once entered, this password cannot be retrieved.

When typing passwords, the characters are replaced by dots, so you do not see the string you are typing. If you are unsure whether you have typed the correct string, use the Test Keyboard Layout field for testing purposes.

SUSE Linux Enterprise Server can use the DES, MD5, or Blowfish encryption algorithms for passwords. The default encryption type is Blowfish. To change the encryption type, click Expert Options › Encryption Type and select the new type.

The root can be changed any time later in the installed system. To do so run YaST and start Security and Users › User and Group Management.

6.16.1.2 Hostname and Domain Name

The hostname is the computer's name in the network. The domain name is the name of the network. A hostname and domain are proposed by default. If your system is part of a network, the hostname has to be unique in this network, whereas the domain name has to be common to all hosts on the network.

In many networks, the system receives its name over DHCP. In this case it is not necessary to modify the proposed hostname and domain name. Select Change Hostname via DHCP instead. To be able to access your system using this hostname, even when it is not connected to the network, select Assign Hostname to Loopback IP. Do not enable this option when your machine provides network services. If you often change networks without restarting the desktop environment (e.g. when switching between different WLANs), do not enable this option either, because the desktop system may get confused when the hostname in /etc/hosts changes.

To change hostname settings at any time after installation, use YaST Network Devices › Network Settings. For more information, see Section 22.4.1, “Configuring the Network Card with YaST”.

6.16.1.3 Network Configuration

Tip
Tip: IBM System z: Network Configuration

For the IBM System z platforms, a working network connection is needed at installation time to connect to the target system, the installation source, and the YaST terminal controlling the process. The steps to set up the network are discussed in Section 4.2.5, “Network Configuration”. The IBM System z platforms only support the types of network interfaces mentioned there (OSA Ethernet, OSA Gigabit Ethernet, OSA Express Fast Ethernet, Escon, and IUCV). The YaST dialog simply displays the interface with its settings as already configured. Just confirm this dialog to continue.

By default, Traditional Method without NetworkManager Applet is enabled. If desired, you can also use NetworkManager to manage all your network devices. However, the traditional method is the preferred option for server solutions. Find detailed information about NetworkManager in Chapter 27, Using NetworkManager.

The network can also be configured after the system installation has been completed. If you skip it now, your system is left offline unable to retrieve any available updates. To configure your network connection later, select Skip Configuration and click Next.

The following network settings can be configured in this step:

General Network Settings

Enable or disable the use of NetworkManager as described above. Also change the IPv6 support here. By default the IPv6 support is enabled. To disable it, click Disable IPv6. For more information about IPv6, see Section 22.2, “IPv6—The Next Generation Internet”.

Firewall

By default SuSEFirewall2 is enabled on all configured network interfaces. To globally disable the firewall for this computer, click on Disable. If the firewall is enabled, you may Open the SSH port in order to allow remote connections via secure shell. To open the detailed firewall configuration dialog, click on Firewall. See Section 15.4.1, “Configuring the Firewall with YaST” for detailed information.

Network Interfaces

All network cards detected by YaST are listed here. If you have already set up a network connection during the installation (as described in Section 6.11.1.1, “Network Setup”) the card used for this connection is listed as Configured. A click on Network Interfaces opens the Network Settings dialog, where you can change existing configurations, set up networks cards not configured yet, or add and configure additional cards.

DSL Connections, ISDN Adapters, and Modems

If your computer is equipped with an internal DSL modem, an internal ADSL Fritz Card, an ISDN card or a modem, clicking on the respective headline opens the configuration dialog. Refer to Chapter 11, Accessing the Internet for further information.

VNC Remote Administration

To enable remote administration of your machine via VNC, click VNC Remote Administration. Choose Allow Remote Administration in the following dialog and adjust your firewall settings accordingly.

Proxy

If you have a proxy server controlling the Internet access in your network, configure the proxy URLs and authentication details in this dialog.

Tip
Tip: Resetting the Network Configuration to the Default Values

Reset the network settings to the original proposed values by clicking Change › Reset to Defaults. This discards any changes made.

6.16.1.3.1 Test Internet Connection

After having configured a network connection, you can test it. For this purpose, YaST establishes a connection to the SUSE Linux Enterprise Server server and downloads the latest release notes. Read them at the end of the installation process. A successful test is also a prerequisite for the automatic addition of the default repositories and for updating online.

If you have multiple network interfaces, verify that the desired card is used to connect to the Internet. If not, click Change Device.

To start the test, select Yes, Test Connection to the Internet and click Next. In the following dialog, view the progress of the test and the results. Detailed information about the test process is available via View Logs. If the test fails, click Back to return to the network configuration to correct your entries.

Proceed with Next. If the test was successful, the official software repositories for SUSE Linux Enterprise Server and the update repository will be configured. Downloading the repository data for the first time may take some time.

If you do not want to test the connection at this point, select No, Skip This Test then Next. This also skips downloading the release notes, configuring the customer center and updating online. These steps can be performed any time after the system has been initially configured.

6.16.1.4 Novell Customer Center Configuration

To get technical support and product updates, you need to register and activate your product with the Novell Customer Center. The Novell Customer Center Configuration provides assistance for doing so. Find detailed information about Novell Customer Center at http://www.novell.com/documentation/ncc/.

If you are offline or want to skip this step, select Configure Later. This also skips SUSE Linux Enterprise Server's online update.

In Include for Convenience, select whether to send unsolicited additional information, such as your Hardware Profile or Optional Information when registering. This simplifies the registration process. Click on Details to get in-depth information about how the data will be collected. In order to obtain information about which data will be sent for your specific product, the Novell server will be connected. Upon this initial connect no data other than the ID of your product will be sent to the Novell servers.

In order to become entitled for support, make sure to check Registration Code. You will be prompted to enter the code when proceeding with Next. Find more information about the technical support at http://www.suse.com/support/programs/.

Note
Note: Data Privacy

No information is passed to anyone outside Novell/SUSE. The data is used for statistical purposes and to enhance your convenience regarding driver support and your Web account. Find a link to the detailed privacy policy by clicking on Details. View the information transmitted in the log file at /root/.suse_register.log.

Apart from activating and registering your product, this module also adds the official update repositories to your configuration. These repositories provide fixes for known bugs or security issues which can be installed via an online update.

To keep your repositories valid, select Regularly Synchronize with Customer Center. This option checks your repositories and adds newly available catalogs or removes obsolete ones. It does not affect manually-added repositories.

Proceed with Next. A connection with the Novell server is established. Follow the on-screen instructions to finish the registration.

Tip
Tip: Re-registering an Installed System with a Different Registration Code

When you register a system in Novell Customer Center, registration data is stored locally and in the Novell Customer Center database. Although it is normally not necessary, there are corner cases which may require you to re-register an already installed machine with a different registration code. To do so, proceed with the following steps on the installed system:

  1. Enter the following command as user root to delete the installation data on the local machine:

    suse_register.pl --erase-local-regdata
  2. Next you need to remove the registered system from the Novell Customer Center database. Go to http://www.suse.com/ in a browser and click Support › Customer Center. Log in and navigate to My Systems › System. Select the system and remove it by clicking on the dash sign in the bottom bar of the table.

  3. Now you can re-register the machine with either suse-register or the YaST module Online Update Configuration.

6.16.1.4.1 Local Registration Server

If your organization provides a local registration server instead of using the Novell Customer Center, you need to specify 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. Open the dialog with Advanced › Local Registration Server

Registration Server

URL of the registration server. The URL has a fixed format https://FQN/center/regsvc/ FQN has to be full qualified hostname of the registration server. Example:

https://smt.example.com/center/regsvc/
Server CA certificate location

Location of the registration server's certificate. Specify one of the following locations:

URL

Remote location (http, https or ftp) from which the certificate can be downloaded. Example:

http://smt.example.com/smt-ca.crt
Floppy

Specifies a location on a floppy. The floppy has to be inserted before proceeding. The value has to start with the string floppy followed by the path to the certificate. Example:

floppy/smt/smt-ca.crt
local path

Absolute path to the certificate on the local machine. Example:

/data/inst/smt/smt-ca.cert
Interactive

Use ask to open a pop-up menu where you can specify the path to the certificate. Do not use this option with AutoYaST. Example

ask
Deactivate certificate installation

Use done if either the certificate will be installed by an add-on product, or if you are using a certificate issued by an official certificate authority. Example:

done

6.16.1.5 Online Update

If an Internet connection has been established, and updates are available, select whether to perform a YaST online update. If there are any patched packages available on the servers, download and install them now to fix known bugs or security issues. For detailed instructions see Chapter 1, YaST Online Update. Directives on how to perform an online update in the installed system are available at Section 9.4, “Keeping the System Up-to-date” or Chapter 1, YaST Online Update. This step is skipped if no updates are available or no Internet connection has been established. Patches fixing security issues and recommended patches applying to your installation are automatically preselected. Click Accept to install them and Next to proceed with the system configuration.

Important
Important: Downloading Software Updates

The download of updates might take quite some time, depending on the bandwidth of the Internet connection and the size of the update files. In case the patch system itself is updated, the online update will restart and download more patches after the restart. If the kernel was updated, the system will reboot before completing the configuration.

6.16.1.6 Services Configuration

After testing the Internet connection and downloading the first updates, a dialog opens in which to enable and configure three network services.

CA Management

The purpose of a CA (certificate authority) is to guarantee a trust relationship among all network services communicating with each other. Without a CA, you can secure server communications with SSL and TLS separately for each individual service. By default, a CA is created and enabled during the installation. Find details about the creation of a CA with YaST in Chapter 17, Managing X.509 Certification.

OpenLDAP Server

You can run an LDAP service on your host to have a central facility manage a range of configuration files. Typically, an LDAP server handles user account data, but with SUSE Linux Enterprise Server it can also be used for mail, DHCP, and DNS data. By default, an LDAP server is set up during the installation. If you decide against the use of an LDAP server, the YaST mail server module does not work because it depends on LDAP functionality. However, you can still set up a mail server on your system with the help of the Mail Transfer Agent module. Find details about LDAP and its configuration with YaST in Chapter 4, LDAP—A Directory Service.

Services

The CIM (Common Information Model) Server is started by default. Click Disable to prevent the server automatically stating at boot time. For more information on CIM services refer to Chapter 34, Web Based Enterprise Management Using SFCB.

If preferred, you can skip this configuration proposal for now. After the installation is finished, configure and start the same services with the help of YaST.

Tip
Tip: Resetting the Service Configuration to Defaults

Restore the defaults by clicking Change › Reset to Defaults. This discards any changes made.

6.16.1.7 User Authentication Method

If network access was configured successfully during the previous steps of the installation, you can now choose from several user management options. If a network connection has not been configured, create local user accounts. You may also, if present, import users from a previous installation. Also change the password encryption type in this dialog.

You can also add additional user accounts or change the user authentication method in the installed system. For detailed information about user management, see Chapter 12, Managing Users with YaST.

The default authentication method is Local (/etc/passwd). If a former version of SUSE Linux Enterprise Server or another system using /etc/passwd is detected, you may import local users. To do so, check Read User Data from a Previous Installation and click Choose. In the next dialog, select the users to import and finish with OK.

Manually enter local users by clicking Next. The New Local User dialog opens. After entering the first name and last name, either accept the proposal or specify a new Username that will be used to log in. Finally, enter a password for the user. Reenter it for confirmation (to ensure that you did not type something else by mistake). To provide effective security, a password should be between five and eight characters long. The maximum length for a password is 72 characters. However, if no special security modules are loaded, only the first eight characters are used to discern the password. Passwords are case-sensitive. Special characters (7-bit ASCII) and the digits 0 to 9 are allowed. Other special characters like 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.

Two additional options are available:

Receive System Mail

Checking this box sends messages created by the system services to the user. These are usually only sent to root, the system administrator. This option is useful for the most frequently used account, because it is highly recommended to log in as root only in special cases.

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 after installation, you can use any e-mail client, for example KMail or Evolution.

Automatic Login

This option automatically logs the current user in to the system on start-up. This is mainly useful if the computer is operated by only one user. For automatic login to work, the option must be explicitly enabled.

Warning
Warning: Automatic Login

With automatic login enabled, the system boots straight to your desktop with no authentication at all. If you store sensitive data on your system, you should not enable this option if the computer can also be accessed by others.

Enter more users by calling the User Management module described in Chapter 12, Managing Users with YaST.

When using a network server for user authentication, access to the following services can be configured:

LDAP

Users are administered centrally on an LDAP server for all systems in the network. More information is available in Section 4.4, “Configuring an LDAP Client with YaST”.

NIS

Users are administered centrally on a NIS server for all systems in the network. See Section 3.2, “Configuring NIS Clients” for more information.

Windows Domain

SMB authentication is often used in mixed Linux and Windows networks. Detailed information is available in Section 28.6, “Samba Server in the Network with Active Directory” and Section 5.3, “Configuring a Linux Client for Active Directory”.

Along with user administration via LDAP and NIS, you can use Kerberos authentication. To use it, select Set Up Kerberos Authentication. For more information on Kerberos, refer to Chapter 6, Network Authentication with Kerberos.

6.16.1.8 Release Notes

After completing the user authentication setup, YaST displays the release notes. Reading them is recommended, because they contain important up-to-date information which was not available when the manuals were printed. If you successfully tested the Internet connection, read the most recent version of the release notes, as fetched from SUSE Linux Enterprise Server's servers. Use Miscellaneous › Release Notes in YaST or start the SUSE Help Center to view the release notes after installation.

6.16.1.9 Hardware Configuration

At the end of the installation, YaST opens a dialog for the configuration of Graphics Cards Printer and Sound. Click the individual components to start the hardware configuration. For the most part, YaST detects and configures the devices automatically.

Tip
Tip: IBM System z: Hardware Configuration

On the IBM System z, there is no display that would be supported by XFree. Accordingly, you do not find a Graphics Cards entry on these systems.

You can skip any peripheral devices and configure them later, as described in Chapter 8, Setting Up Hardware Components with YaST. To skip the configuration, select Skip Configuration and click Next.

However, when setting up a desktop system you should configure the graphics card right away. Although the display settings as configured by YaST should be generally acceptable, most users have very strong preferences as far as resolution, color depth, and other graphics features are concerned. To change these settings, select the respective item and set the values as desired.

Tip
Tip: Resetting Hardware Configuration to the Default Values

You can cancel any changes to the hardware configuration by clicking Change › Reset to Defaults. YaST then shows the original proposal again.

6.16.1.10 Installation Completed

After a successful installation, YaST shows the Installation Completed dialog. In this dialog, select whether to clone your newly installed system for AutoYaST. To clone your system, select Clone This System for AutoYaST. The profile of the current system is stored in /root/autoyast.xml. Cloning is selected by default.

AutoYaST is a system for installing one or more SUSE Linux Enterprise Server systems automatically without user intervention. AutoYaST installations are performed using a control file with installation and configuration data.For detailed information, refer to Chapter 21, Automated Installation. Finish the installation of SUSE Linux Enterprise Server with Finish in the final dialog.

6.17 Graphical Login

Tip
Tip: IBM System z: No Graphical Login

The graphical login is not available on IBM System z platforms.

SUSE Linux Enterprise Server is now fully installed and configured. Unless you enabled the automatic login function or customized the default runlevel, you should see the graphical login on your screen in which to enter a username and password to log in to the system. On single user systems with automatic login enabled, the desktop starts automatically.

Print this page