diff --git a/images/src/png/autoyast2-maindialog_kde.png b/images/src/png/autoyast2-maindialog_kde.png index 743a56cbd7..12917f9256 100644 Binary files a/images/src/png/autoyast2-maindialog_kde.png and b/images/src/png/autoyast2-maindialog_kde.png differ diff --git a/images/src/png/cms-class-definitions_kde.png b/images/src/png/cms-class-definitions_kde.png index c4e77753dc..174176f506 100644 Binary files a/images/src/png/cms-class-definitions_kde.png and b/images/src/png/cms-class-definitions_kde.png differ diff --git a/images/src/png/yast2_hypervisors_kde.png b/images/src/png/yast2_hypervisors_kde.png index 8cf02c4a95..3eda9f0568 100644 Binary files a/images/src/png/yast2_hypervisors_kde.png and b/images/src/png/yast2_hypervisors_kde.png differ diff --git a/images/src/png/yast2_inst_nfsserver1_kde.png b/images/src/png/yast2_inst_nfsserver1_kde.png index eb25bacc4f..4774774fcf 100644 Binary files a/images/src/png/yast2_inst_nfsserver1_kde.png and b/images/src/png/yast2_inst_nfsserver1_kde.png differ diff --git a/images/src/png/yast2_inst_nisserver2_kde.png b/images/src/png/yast2_inst_nisserver2_kde.png index 2ac50bc971..e6fdfcd7e9 100644 Binary files a/images/src/png/yast2_inst_nisserver2_kde.png and b/images/src/png/yast2_inst_nisserver2_kde.png differ diff --git a/images/src/png/yast2_nis1_no_nis_installed_kde.png b/images/src/png/yast2_nis1_no_nis_installed_kde.png index bafb2af34e..3fefad5862 100644 Binary files a/images/src/png/yast2_nis1_no_nis_installed_kde.png and b/images/src/png/yast2_nis1_no_nis_installed_kde.png differ diff --git a/images/src/png/yast2_nis_hosts_kde.png b/images/src/png/yast2_nis_hosts_kde.png index febbb80245..b38f95b9aa 100644 Binary files a/images/src/png/yast2_nis_hosts_kde.png and b/images/src/png/yast2_nis_hosts_kde.png differ diff --git a/images/src/png/yast2_nis_maps_kde.png b/images/src/png/yast2_nis_maps_kde.png index c17df953ad..6ea8dda5ed 100644 Binary files a/images/src/png/yast2_nis_maps_kde.png and b/images/src/png/yast2_nis_maps_kde.png differ diff --git a/images/src/png/yast2_nis_master_kde.png b/images/src/png/yast2_nis_master_kde.png index 31413707fa..3253f8b47d 100644 Binary files a/images/src/png/yast2_nis_master_kde.png and b/images/src/png/yast2_nis_master_kde.png differ diff --git a/xml/art_amd-sev.xml b/xml/art_amd-sev.xml index 0b80a3e2dc..b5631d8c21 100644 --- a/xml/art_amd-sev.xml +++ b/xml/art_amd-sev.xml @@ -398,7 +398,7 @@ - The following example starts a network installation of a SLES15 SP4 + The following example starts a network installation of a &slsa; 15 SP4 virtual machine protected with SEV-ES. diff --git a/xml/audit_components.xml b/xml/audit_components.xml index 5af4055231..d2257b712b 100644 --- a/xml/audit_components.xml +++ b/xml/audit_components.xml @@ -48,7 +48,7 @@ - yes + yes @@ -209,11 +209,12 @@ audispd merged into auditd - In &sles; 15 SP4 the code for - audispd has - been merged into auditd. - All audispd configurations - are now in /etc/audit/auditd.conf and + In &sles; 15 SP4&leap; 15.4 the code for audispd has been merged into auditd. All audispd configurations are now in + /etc/audit/auditd.conf and /etc/audit/plugins.d. diff --git a/xml/ay_erb_templates.xml b/xml/ay_erb_templates.xml index dd7ffcb008..697af21c8a 100644 --- a/xml/ay_erb_templates.xml +++ b/xml/ay_erb_templates.xml @@ -479,9 +479,8 @@ Distribution name (for example, - SLES or openSUSE - TumbleweedSLE - Micro) + &slsa; or &opensuse; + Tumbleweed&slem;) @@ -508,7 +507,7 @@ You might use this information to decide which product to install, using - pretty much the same profile for all of them (SLE or openSUSE + pretty much the same profile for all of them (&slea; or &opensuse; distributions). diff --git a/xml/ay_firewall.xml b/xml/ay_firewall.xml index 90877fa83c..ab1e612b2a 100644 --- a/xml/ay_firewall.xml +++ b/xml/ay_firewall.xml @@ -359,30 +359,32 @@ Installation stages when the &firewalld; profile is applied - Starting with &productname; 15 SP3, the &firewalld; profile is - usually applied at the end of the first stage of the installation. (To learn - about the installation stages, see .) - However, there are circumstances where the profile is applied in the second - stage. The following list specifies the conditions under which the - &firewalld; profile is applied in the first or second stage: + Starting with &productname; 15 SP3.3, the + &firewalld; profile is usually applied at the end of the first stage of the + installation. (To learn about the installation stages, see .) However, there are circumstances where the + profile is applied in the second stage. The following list specifies the + conditions under which the &firewalld; profile is applied in the first or + second stage: - You are running &ay; with a &firewalld; section, and not installing &slea; + You are running &ay; with a &firewalld; section, and not installing &productname; over SSH or VNC. The firewall is configured in the first stage. - You are running &ay; with a &firewalld; section, installing &slea; over + You are running &ay; with a &firewalld; section, installing &productname; over SSH or VNC, and no second stage is required. The firewall is configured in the first stage. - You are running &ay; with a &firewalld; section, installing &slea; over + You are running &ay; with a &firewalld; section, installing &productname; over SSH or VNC, and the second stage is required. The firewall is configured in the second stage. diff --git a/xml/ay_partitioning.xml b/xml/ay_partitioning.xml index b75eacfd73..c712be874d 100644 --- a/xml/ay_partitioning.xml +++ b/xml/ay_partitioning.xml @@ -1846,7 +1846,7 @@ The accepted values for each RAID depend on the RAID level (eg. raid5) - and the number of devices in the RAID. Given that RAID0 or RAID1 do not provide + and the number of devices in the RAID. Given that RAID0 or RAID1 do not provide any parity, do not specify this option for such devices. <parity_algorithm>left_asymmetric</parity_algorithm> @@ -2135,7 +2135,8 @@ size=40G features='0' hwhandler='0' wp=rw RAID implementations. For example, you can dynamically migrate a multi-device Btrfs volume from one RAID level to another, RAID levels can be set on a per-file basis, and more. However, not all of these features are - fully supported yet in &productname; &product-ga; SP&product-sp;. + fully supported yet in &productname; &product-ga; SP.&product-sp;. With &ay;, a multi-device Btrfs can be configured by specifying a drive with diff --git a/xml/ay_security_settings.xml b/xml/ay_security_settings.xml index c280c09372..106c79803e 100644 --- a/xml/ay_security_settings.xml +++ b/xml/ay_security_settings.xml @@ -131,7 +131,8 @@ Linux Security Module (LSM) settings - In &sle; 15.4 and up, the installation control file has a new + In &sle; 15 SP4&leap; 15.4 and up, the installation control file has a new option, <lsm_select> for configuring which major Linux Security Module (LSM) will be activated by default after installation: &aa;, &selnx;, or none. @@ -157,7 +158,7 @@ - + Using &openscap; security policies @@ -193,7 +194,7 @@ <suse_register> section (see ). - If you install without an internet connection, add the + If you install without an internet connection, add the Basesystem module from the QU2 medium to the <add_on_products> section: diff --git a/xml/book_security.xml b/xml/book_security.xml index ce9a072f65..a67cce4351 100644 --- a/xml/book_security.xml +++ b/xml/book_security.xml @@ -78,7 +78,7 @@ - + Regulations and Compliance diff --git a/xml/book_tuning.xml b/xml/book_tuning.xml index d272e06953..37e42fb761 100644 --- a/xml/book_tuning.xml +++ b/xml/book_tuning.xml @@ -84,7 +84,7 @@ - + diff --git a/xml/deployment_selfinstall_procedure.xml b/xml/deployment_selfinstall_procedure.xml index 10193f5ae9..6d437f1dd8 100644 --- a/xml/deployment_selfinstall_procedure.xml +++ b/xml/deployment_selfinstall_procedure.xml @@ -98,7 +98,7 @@ - Select Install SLE Micro to start the installation + Select Install &slem; to start the installation process. @@ -116,7 +116,7 @@ - Start the configuration process by selecting SLE Micro. + Start the configuration process by selecting &slem;. &slema; is either configured according to the instructions provided on the configuration device, or jeos-firstboot is started. diff --git a/xml/deployment_yast_installer.xml b/xml/deployment_yast_installer.xml index ca1b7d7a54..0ef090440a 100644 --- a/xml/deployment_yast_installer.xml +++ b/xml/deployment_yast_installer.xml @@ -2460,7 +2460,7 @@ sle-live-patching 8c541494 from the beginning of the installation process, boot the system with the boot parameter YAST_SECURITY_POLICY=POLICY. - To check for compliance with the &disaa; &stiga;, use + To check for compliance with the &disaa; &stiga;, use YAST_SECURITY_POLICY=stig. For more information about boot parameters, refer to . @@ -2494,7 +2494,7 @@ sle-live-patching 8c541494 Network Settings module. For details, see . - + Support for &nm; &suse; only supports &nm; for desktop workloads with &sleda; or the Workstation extension. diff --git a/xml/file_management.xml b/xml/file_management.xml index 9a831ae796..1d69b9c06b 100644 --- a/xml/file_management.xml +++ b/xml/file_management.xml @@ -74,14 +74,15 @@ - You are advised to review . It is - important to understand the need to separate the partitions that could - impact a running system (for example, log files filling up - /var/log are a good reason to separate - /var from the / partition). - Another thing to keep in mind is that you need to use LVM - or another volume manager or at the least the extended partition type - to work around the limit of four primary partitions on PC class systems. + You are advised to review . It is important to understand the + need to separate the partitions that could impact a running system (for + example, log files filling up /var/log are a good + reason to separate /var from the + / partition). Another thing to keep in mind is that + you need to use LVM or another volume manager or at the least the extended + partition type to work around the limit of four primary partitions on PC + class systems. @@ -103,7 +104,7 @@ - &sle; provides the permissions package to easily apply + &productname; provides the permissions package to easily apply file permissions. The package comes with three pre-defined system profiles: diff --git a/xml/gpu_passthru.xml b/xml/gpu_passthru.xml index ec579e60ac..1a7a03bfa7 100644 --- a/xml/gpu_passthru.xml +++ b/xml/gpu_passthru.xml @@ -31,9 +31,9 @@ GPU pass-through is supported on the &x86-64; architecture only. - + - The host operating system needs to be SLES 12 SP3 or newer. + The host operating system needs to be &slsa; 12 SP3 or newer. @@ -63,9 +63,9 @@ Verify the host environment - + - Verify that the host operating system is SLES 12 SP3 or newer: + Verify that the host operating system is &slsa; 12 SP3 or newer: &prompt.user;cat /etc/issue diff --git a/xml/hardware_nvdimm.xml b/xml/hardware_nvdimm.xml index e30378b1b1..17a1ff32ab 100644 --- a/xml/hardware_nvdimm.xml +++ b/xml/hardware_nvdimm.xml @@ -11,7 +11,7 @@ - This chapter contains additional information about using &sle; with + This chapter contains additional information about using &productname; with non-volatile main memory, also known as Persistent Memory, comprising one or more NVDIMMs. @@ -31,10 +31,10 @@ - &suse; currently supports the use of persistent memory with &sls; on machines + &suse; currently supports the use of persistent memory with &productname; on machines with the &x86-64; and &power; architectures. - + Like conventional RAM, persistent memory is installed directly into mainboard memory slots. As such, it is supplied in the same physical form @@ -44,7 +44,7 @@ Unlike RAM, though, persistent memory is also similar to flash-based SSDs in - several ways. Both are based on forms of solid-state memory circuitry, but + several ways. Both are based on forms of solid-state memory circuitry, but despite this, both provide non-volatile storage: Their contents are retained when the system is powered off or restarted. For both forms of medium, writing data is slower than reading it, and both support a limited number of @@ -65,15 +65,15 @@ development, different vendors' hardware may impose different limitations. Thus, the following statements are generalizations. - + Persistent memory is up to ten times slower than DRAM, but around a thousand times faster than flash storage. It can be rewritten on a byte-by-byte basis - rather than flash memory's whole-sector erase-and-rewrite process. Finally, + rather than flash memory's whole-sector erase-and-rewrite process. Finally, while rewrite cycles are limited, most forms of persistent memory can handle millions of rewrites, compared to the thousands of cycles of flash storage. - + This has two important consequences: @@ -118,8 +118,8 @@ fast persistent storage, an alternative to SSDs and NVMe devices. Data in this mode is kept when the system is powered off. - - App Direct Mode has been supported since SLE 12 SP4. + + App Direct Mode has been supported since &slsa; 12 SP4. @@ -133,8 +133,8 @@ advantage of this mode, memory performance may decrease. Data in this mode is lost when the system is powered off. - - Memory Mode has been supported since SLE 15 SP1. + + Memory Mode has been supported since &slsa; 15 SP1. @@ -142,8 +142,8 @@ In Mixed Mode, the Intel Optane memory is partitioned, so it can serve in both modes simultaneously. - - Mixed Mode has been supported since SLE 15 SP1. + + Mixed Mode has been supported since &slsa; 15 SP1. @@ -290,7 +290,7 @@ medium. If a sector cannot be completely written (that is, if the write operation fails for some reason), then the whole sector will be rolled back to its previous state. Thus a given sector cannot be - partially written. + partially written. Additionally, access to BTT namespaces is cached by the kernel. @@ -397,7 +397,7 @@ This is useful when you want to use the persistent memory on a set of NVDIMMs as a disk-like pool of fast storage. For example, placing - the file system journal on PMEM with BTT increases the reliability + the file system journal on PMEM with BTT increases the reliability of file system recovery after a power failure or other sudden interruption (see ). @@ -410,7 +410,7 @@ The advantage of BTT is that sector write atomicity is guaranteed, so even sophisticated applications that depend on data integrity will keep working. Media error reporting works through standard error-reporting - channels. + channels. @@ -424,12 +424,12 @@ libndctl package, which provides a set of user space libraries to configure NVDIMMs. - + These tools work via the libnvdimm library, which supports three types of NVDIMM: - + @@ -748,7 +748,7 @@ destroyed 1 namespace Creating a PMEM namespace with BTT BTT provides sector write atomicity, which makes it a good choice - when you need data protection, for example for Ext4 and XFS journals. + when you need data protection, for example for Ext4 and XFS journals. If there is a power failure, the journals are protected and should be recoverable. The following examples show how to create a PMEM namespace with BTT in sector mode, and how @@ -774,7 +774,7 @@ I/O size (minimum/optimal): 4096 bytes / 4096 bytes Like the DAX-capable PMEM namespace we previously configured, this BTT-capable PMEM namespace consumes all the available storage on the NVDIMMs. - + The trailing s in the device name @@ -804,19 +804,19 @@ I/O size (minimum/optimal): 4096 bytes / 4096 bytes will use the page cache. - + Placing the file system journal on PMEM/BTT When you place the file system journal on a separate device, it - must use the same file system block size as the file system. Most - likely this is 4096, and you can find the block size with this + must use the same file system block size as the file system. Most + likely this is 4096, and you can find the block size with this command: &prompt.root;blockdev --getbsz /dev/sda3 - The following example creates a new Ext4 journal on a separate - NVDIMM device, creates the file system on a SATA device, then + The following example creates a new Ext4 journal on a separate + NVDIMM device, creates the file system on a SATA device, then attaches the new file system to the journal: @@ -827,7 +827,7 @@ I/O size (minimum/optimal): 4096 bytes / 4096 bytes The following example creates a new XFS file system on a SATA drive, and creates the journal on a separate NVDIMM device: -&prompt.root;mkfs.xfs -l logdev=/dev/pmem3s /dev/sda3 +&prompt.root;mkfs.xfs -l logdev=/dev/pmem3s /dev/sda3 See man 8 mkfs.ext4 and man 8 mkfs.ext4 for detailed information about options. diff --git a/xml/libvirt_configuration_virsh.xml b/xml/libvirt_configuration_virsh.xml index 41d137bd1c..c28993b180 100644 --- a/xml/libvirt_configuration_virsh.xml +++ b/xml/libvirt_configuration_virsh.xml @@ -771,7 +771,7 @@ Used memory: 8388608 KiB &slsa;11 SP4 &kvm; guests - On a newer &qemu; machine type (pc-i440fx-2.0 or higher) with &slsa;11 + On a newer &qemu; machine type (pc-i440fx-2.0 or higher) with &slsa; 11 SP4 &kvm; guests, the acpiphp module is not loaded by default in the guest. This module must be loaded to enable hotplugging of disk and network devices. To load the diff --git a/xml/libvirt_guest_installation.xml b/xml/libvirt_guest_installation.xml index 65616f3855..82c2fc56e3 100644 --- a/xml/libvirt_guest_installation.xml +++ b/xml/libvirt_guest_installation.xml @@ -577,12 +577,10 @@ network=vnet_nated method, but it needs to be supported by the guest as well. - While openSUSE and SLE-based guests support memory ballooning, Windows - guests need the - Virtual - Machine Driver Pack (VMDP) to provide ballooning. To set the - maximum memory greater than the initial memory configured for Windows - guests, follow these steps: + While &opensuse; and &slea;-based guests support memory ballooning, Windows guests need the + Virtual Machine Driver Pack + (VMDP) to provide ballooning. To set the maximum memory greater than the initial + memory configured for Windows guests, follow these steps: diff --git a/xml/libvirt_managing.xml b/xml/libvirt_managing.xml index 0996742fd1..094b4ab1a2 100644 --- a/xml/libvirt_managing.xml +++ b/xml/libvirt_managing.xml @@ -246,7 +246,7 @@ - &slsa; 12 and up/&opensuse; + &slsa; 12, 15 and &opensuse; Launch the &yast; Boot Loader module and switch to the diff --git a/xml/net_samba.xml b/xml/net_samba.xml index 4fe1aed0dd..27224f7271 100644 --- a/xml/net_samba.xml +++ b/xml/net_samba.xml @@ -30,10 +30,10 @@ will be able to access their home directories when hosted on CIFS. - SMB1 will be disabled + SMB1 is unsupported Starting with Samba version 4.17, the SMB1 protocol has been disabled in - &slea; and is no longer supported. + &productname; and is no longer supported. diff --git a/xml/networkmanager.xml b/xml/networkmanager.xml index 1d6afa9719..e12211e05d 100644 --- a/xml/networkmanager.xml +++ b/xml/networkmanager.xml @@ -20,7 +20,7 @@ interfaces and switching between networks when you are moving. - + &nm; is only supported by &suse; for desktop workloads with &sleda; or the diff --git a/xml/nm.xml b/xml/nm.xml index 5d47d429ed..61ef54bc96 100644 --- a/xml/nm.xml +++ b/xml/nm.xml @@ -34,7 +34,7 @@ http://www.heise.de/netze/artikel/WLAN-und-LAN-sichern-mit-IEEE-802-1X-und-Radiu remain connected via a wireless connection. - + &nm; is only supported by &suse; for desktop workloads with &sleda; or the diff --git a/xml/pv2fv.xml b/xml/pv2fv.xml index 8fca3aadac..38d5dce860 100644 --- a/xml/pv2fv.xml +++ b/xml/pv2fv.xml @@ -66,7 +66,7 @@ - /etc/default/grub (&slsa; 12 and 15 only) + /etc/default/grub (&slsa; 12, 15, &opensuse;) @@ -118,7 +118,7 @@ ln -sf /dev/xvda1 /dev/hda1 - On &slsa; 12 and 15, open or create + On &slsa; 12, 15, and &opensuse; open or create /etc/dracut.conf.d/10-virt.conf and add the modules with force_drivers by adding a line as in the example below (mind the leading whitespace): diff --git a/xml/security_ad_support.xml b/xml/security_ad_support.xml index 8c3de731b5..4b7706563b 100644 --- a/xml/security_ad_support.xml +++ b/xml/security_ad_support.xml @@ -11,7 +11,7 @@ - yes + yes @@ -1310,7 +1310,7 @@ Certificate auto-enrollment enables network devices to automatically enroll certificates from Active Directory Certificate Services, including - &sles; devices, with no user intervention. This is managed by &ad;'s + &productname; devices, with no user intervention. This is managed by &ad;'s Group Policy, using Samba's samba-gpupdate command. diff --git a/xml/security_freeradius.xml b/xml/security_freeradius.xml index d4be385740..5bba0d5177 100644 --- a/xml/security_freeradius.xml +++ b/xml/security_freeradius.xml @@ -14,63 +14,63 @@ - yes + yes - The RADIUS (Remote Authentication Dial-In User Service) protocol has - long been a standard service for manage network access. It provides - authentication, authorization and accounting (AAA) for - large businesses such as Internet service providers and cellular - network providers, and is also popular for small networks. It + The RADIUS (Remote Authentication Dial-In User Service) protocol has + long been a standard service for manage network access. It provides + authentication, authorization and accounting (AAA) for + large businesses such as Internet service providers and cellular + network providers, and is also popular for small networks. It authenticates users and devices, authorizes those users and devices for certain network services, and tracks use of services for - billing and auditing. You do not have to use all three of the AAA - protocols, but only the ones you need. For example, you may not need + billing and auditing. You do not have to use all three of the AAA + protocols, but only the ones you need. For example, you may not need accounting but only client authentication, or perhaps all you want is accounting, and client authorization is managed by something else. - It is efficient and manages thousands of requests on modest - hardware. It works for all network protocols and not just + It is efficient and manages thousands of requests on modest + hardware. It works for all network protocols and not just dial-up, but the name remains the same. - RADIUS operates in a distributed architecture, sitting separately - from the Network Access Server (NAS). User access data is stored on a - central RADIUS server that is available to multiple NAS. The NAS - provide the physical access to the network, such as a managed + RADIUS operates in a distributed architecture, sitting separately + from the Network Access Server (NAS). User access data is stored on a + central RADIUS server that is available to multiple NAS. The NAS + provide the physical access to the network, such as a managed Ethernet switch, or wireless access point. - FreeRADIUS is the open source RADIUS implementation, and is the most - widely used RADIUS server. In this chapter you learn how to - install and test a FreeRADIUS server. Because of the numerous - use cases, after your initial setup is working correctly, + FreeRADIUS is the open source RADIUS implementation, and is the most + widely used RADIUS server. In this chapter you learn how to + install and test a FreeRADIUS server. Because of the numerous + use cases, after your initial setup is working correctly, your next stop is the official documentation, which is detailed and thorough (see ). - Installation and testing on &sle; + Installation and testing on &productname; - The following steps set up a simple test system. When you have - verified that the server is operating correctly and you are ready to - create a production configuration, you have several undo steps + The following steps set up a simple test system. When you have + verified that the server is operating correctly and you are ready to + create a production configuration, you have several undo steps to perform before starting your production configuration. - First install the freeradius-server and - freeradius-server-utils - packages. Then enter /etc/raddb/certs and run - the bootstrap script to create a set of test + First install the freeradius-server and + freeradius-server-utils + packages. Then enter /etc/raddb/certs and run + the bootstrap script to create a set of test certificates: &prompt.root;zypper in freeradius-server freeradius-server-utils &prompt.root;cd /etc/raddb/certs &prompt.root;./bootstrap - The README in the certs directory contains a - great deal of useful information. When the + The README in the certs directory contains a + great deal of useful information. When the bootstrap script has completed, start the server in debugging mode: @@ -87,23 +87,23 @@ Ready to process requests - When you see the Listening and Ready to process requests lines, - your server has started correctly. If it does not start, read the - output carefully because it tells you what went wrong. You may direct + When you see the Listening and Ready to process requests lines, + your server has started correctly. If it does not start, read the + output carefully because it tells you what went wrong. You may direct the output to a text file with tee: &prompt.user;radiusd -X | tee radiusd.text The next step is to test authentication with a test client and user. - The client is a client of the RADIUS server, such as a wireless + The client is a client of the RADIUS server, such as a wireless access point or switch. Clients are configured in - /etc/raddb/client.conf. Human users are - configured in + /etc/raddb/client.conf. Human users are + configured in /etc/raddb/mods-config/files/authorize. Open - /etc/raddb/mods-config/files/authorize and + /etc/raddb/mods-config/files/authorize and uncomment the following lines: bob Cleartext-Password := "hello" @@ -112,7 +112,7 @@ Reply-Message := "Hello, %{User-Name}" A test client, client localhost, is provided in /etc/raddb/client.conf, with a secret of testing123. Open a second terminal, and as an - unprivileged user use the radtest command to log + unprivileged user use the radtest command to log in as bob: &prompt.user;radtest bob hello 127.0.0.1 0 testing123 @@ -140,9 +140,9 @@ Waking up in 4.9 seconds. (3) Cleaning up request packet ID 241 with timestamp +889 - Now run one more login test from a different computer on your - network. Create a client configuration on your server by uncommenting - and modifying the following entry in + Now run one more login test from a different computer on your + network. Create a client configuration on your server by uncommenting + and modifying the following entry in clients.conf, using the IP address of your test machine: @@ -153,25 +153,25 @@ Waking up in 4.9 seconds. - On the client machine, install - freeradius-server-utils. Try logging in from the client as bob, using the radtest command. It - is better to use the IP address of the RADIUS server rather than the + On the client machine, install + freeradius-server-utils. Try logging in from the client as bob, using the radtest command. It + is better to use the IP address of the RADIUS server rather than the hostname because it is faster: &prompt.user;radtest bob hello &wsIip; 0 testing123-1 - If your test logins fail, review all the output to learn what went - wrong. There are several test users and test clients provided. The - configuration files are full of useful information, and we recommend - studying them. When you are satisfied with your testing and ready to - create a production configuration, remove all the test certificates - in /etc/raddb/certs and replace them with your - own certificates, comment out all the test users and clients, and + If your test logins fail, review all the output to learn what went + wrong. There are several test users and test clients provided. The + configuration files are full of useful information, and we recommend + studying them. When you are satisfied with your testing and ready to + create a production configuration, remove all the test certificates + in /etc/raddb/certs and replace them with your + own certificates, comment out all the test users and clients, and stop radiusd by pressing C. Manage - the radiusd.service with + the radiusd.service with systemctl, just like any other service. diff --git a/xml/security_ldap_firewall.xml b/xml/security_ldap_firewall.xml index 42c79e9f31..a06f42c531 100644 --- a/xml/security_ldap_firewall.xml +++ b/xml/security_ldap_firewall.xml @@ -20,7 +20,7 @@ connections, and STARTTLS. 636 is for encrypted connections over TLS. - &firewalld; is the default firewall manager for &sle;. The following rules + &firewalld; is the default firewall manager for &productname;. The following rules activate the ldap and ldaps firewall services: diff --git a/xml/security_ldap_sssd.xml b/xml/security_ldap_sssd.xml index b5f42bb549..120cbeefb5 100644 --- a/xml/security_ldap_sssd.xml +++ b/xml/security_ldap_sssd.xml @@ -146,7 +146,7 @@ shadow: compat sss Edit the PAM configuration on the SSSD server, modifying common-account-pc, common-auth-pc, common-password-pc, and -common-session-pc. &sle; provides a command to +common-session-pc. &productname; provides a command to modify all of these files at once, pam-config: &prompt.sudo;pam-config -a --sss diff --git a/xml/security_ssh.xml b/xml/security_ssh.xml index fe59650a80..ef27b3915b 100644 --- a/xml/security_ssh.xml +++ b/xml/security_ssh.xml @@ -16,7 +16,7 @@ - OpenSSH is the SSH (secure shell) implementation that ships with &sls;, + OpenSSH is the SSH (secure shell) implementation that ships with &productname;, for securing network operations such as remote administration, file transfers, and tunneling insecure protocols. SSH encrypts all traffic between two hosts, including authentication, to protect against @@ -1409,10 +1409,9 @@ Have a lot of fun... X11 forwarding does not work on Wayland - X11 forwarding requires the X Windows System, which is the default on - &slea;, and not the Wayland display server protocol. The X Windows - System has built-in networking, while Wayland does not. Wayland is not - supported on &slea;. + X11 forwarding requires the X Window System running on the remote host. The X Window System + has built-in networking, while Wayland does not. Therefore Wayland does not support X11 + forwarding. Use the following command to learn if your system runs X or Wayland: @@ -1790,13 +1789,13 @@ cd path Change remote directory to 'path' /usr/share/doc/packages/openssh-common/README.SUSE - + /usr/share/doc/packages/openssh-common/README.FIPS &suse; package specific documentation; changes in defaults with - respect to upstream, notes on FIPS mode etc. + respect to upstream, notes on FIPS mode etc. diff --git a/xml/selinux.xml b/xml/selinux.xml index 006d28ef1a..f114fd8c38 100644 --- a/xml/selinux.xml +++ b/xml/selinux.xml @@ -308,12 +308,12 @@ system_u:object_r:var_t var For testing purposes you can obtain policies from . This provides - repositories for &slea; with several additional packages, including policies. + repositories for &productname; with several additional packages, including policies. - Copy the repository link that matches your &slea; version, and add it with Zypper: + Copy the repository link that matches your &productname; version, and add it with Zypper: &prompt.sudo;zypper ar -f \ https://download.opensuse.org/repositories/security:/SELinux_legacy/&productnumber-leaprepo;/ \ diff --git a/xml/sle_update_finish.xml b/xml/sle_update_finish.xml index 5eb3e6cdde..24ad0b4828 100644 --- a/xml/sle_update_finish.xml +++ b/xml/sle_update_finish.xml @@ -111,7 +111,7 @@ &prompt.sudo;mkfs.xfs -m crc=0 DEVICE - The format was used in SLE 11 and older releases, and it currently creates + The format was used in &slea; 11 and older releases, and it currently creates a warning message by dmesg: Deprecated V4 format (crc=0) will not be supported after September 2030 diff --git a/xml/sle_update_preparation.xml b/xml/sle_update_preparation.xml index b440ddd78b..3c8fdc0abd 100644 --- a/xml/sle_update_preparation.xml +++ b/xml/sle_update_preparation.xml @@ -22,7 +22,7 @@ yes - jufa 2021-02-09: suggestion to give this chapter a facelift: + jufa 2021-02-09: suggestion to give this chapter a facelift: Chapter 3: Preparing the upgrade - Intro - Procedure w check system version, release notes, back-up, listing packages, create proposal @@ -31,7 +31,7 @@ Currently you cannot skip a release when performing upgrade of &slema;. You can upgrade your system only to the subsequent release, for example from 5.0 to 5.1 and then to 5.2. - + Make sure the system is up-to-date @@ -296,19 +296,18 @@ Number of packages increases with an update to a new major release - A system upgraded to a new major version - (SLE X+1) may contain more packages than - the initial system (SLE X). It will also - contain more packages than a fresh installation of - SLE X+1 with the same pattern selection. - Reasons for this are: + A system upgraded to a new major version (&slea; X+1) may + contain more packages than the initial system (&slea; X). It + will also contain more packages than a fresh installation of + &slea; X+1 with the same pattern selection. Reasons for this + are: Packages were split to allow a more fine-grained package selection. For - example, 37 texlive packages on SLE 11 were split - into over 3000 packages on SLE 15. + example, 37 texlive packages on &slea; 11 were split + into over 3000 packages on &slea; 15. @@ -316,13 +315,13 @@ When a package has been split, all new packages are installed in the upgrade case to retain the same functionality as the previous version. However, the new default for a fresh installation of - SLE X+1 may be to not install all + &slea; X+1 may be to not install all packages. - Legacy packages from SLE X may be kept + Legacy packages from &slea; X may be kept for compatibility reasons. @@ -1026,7 +1025,7 @@ GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sda1 splash=silent quiet showopts" Get the UUID for /dev/sda1: -&prompt.sudo;blkid /dev/vda1 +&prompt.sudo;blkid /dev/vda1 /dev/vda1: UUID="a1d1f2e0-b0ee-4be2-83d5-78a98c585827" TYPE="swap" PARTUUID="000134b5-01" The UUID for /dev/sda1 is @@ -1040,7 +1039,7 @@ GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/sda1 splash=silent quiet showopts" UUID=a1d1f2e0-b0ee-4be2-83d5-78a98c585827. The result will look like this: -GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=a1d1f2e0-b0ee-4be2-83d5-78a98c585827 splash=silent quiet showopts" +GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=a1d1f2e0-b0ee-4be2-83d5-78a98c585827 splash=silent quiet showopts" diff --git a/xml/slemicro_pcp.xml b/xml/slemicro_pcp.xml index 81b2469f0a..49f4ccfb2c 100644 --- a/xml/slemicro_pcp.xml +++ b/xml/slemicro_pcp.xml @@ -47,7 +47,7 @@ To get the container image using Cockpit, go to Podman containers, click Get new image, and search for pcp. Then select the image from the - registry.suse.com for SLE 15 SP4 and download it. + registry.suse.com for &slea; 15 SP4 and download it.
@@ -497,12 +497,12 @@ $version=1.1 # Value is days before compressing archives, 0 is immediate compression, # "never" or "forever" suppresses compression. # -#$PCP_COMPRESSAFTER=0 +#$PCP_COMPRESSAFTER=0 #$PCP_COMPRESSAFTER=3 #$PCP_COMPRESSAFTER=never - + # === LOGGER CONTROL SPECIFICATIONS === -# +# #Host P? S? directory args # local primary logger @@ -525,7 +525,7 @@ LOCALHOSTNAME y n PCP_ARCHIVE_DIR/LOCALHOSTNAME -r -T24h10m -c config.de slemicro_1 y n PCP_ARCHIVE_DIR/slemicro_1 -r -T24h10m -c config.default -v 100Mb
- - + Btrfs (v4.3) - + Ext4 (v4.3) - + XFS (v5.3) -As of &productname; 15 SP3, any of the named file systems can be used. +As of &productname; 15 SP3.3, any of the named file systems can be used. @@ -390,7 +390,7 @@ To properly account writeback I/O, it is necessary to have equal I/O and memory controller cgroup hierarchies, and to use the cgroup v2 I/O controller. Together, this means that one has to use the unified cgroup hierarchy. This has to be requested -explicitly in SLES by passing a kernel command line option, +explicitly in &productname; by passing a kernel command line option, . @@ -419,7 +419,7 @@ Switch the scheduler to BFQ: You must specify the disk device (not a partition). The optimal way to set this attribute is a udev rule specific to the device -(note that &slsa; ships udev rules that already enable BFQ for rotational +(note that &productname; ships udev rules that already enable BFQ for rotational disk drives). diff --git a/xml/tuning_kexec.xml b/xml/tuning_kexec.xml index 6075f6c3f0..9e2769e33e 100644 --- a/xml/tuning_kexec.xml +++ b/xml/tuning_kexec.xml @@ -888,7 +888,7 @@ cio_ignore=all,!da5d,!f500-f502 SFTP is the preferred method for transmitting files over SSH. The - target host must enable the SFTP subsystem (&slea; default). Example: + target host must enable the SFTP subsystem (&productname; default). Example: KDUMP_SAVEDIR=sftp://TARGET_HOST/path/to/dumps diff --git a/xml/tuning_storagescheduler.xml b/xml/tuning_storagescheduler.xml index 4182ae7a26..a2970ec8d0 100644 --- a/xml/tuning_storagescheduler.xml +++ b/xml/tuning_storagescheduler.xml @@ -5,16 +5,16 @@ %entities; ]> - - + Tuning I/O performance - yes + yes @@ -29,7 +29,7 @@ network storage systems, for example, each require different tuning strategies. - + Switching I/O scheduling @@ -80,7 +80,7 @@ <literal>elevator</literal> boot parameter removed - The elevator boot parameter has been removed. The blk-mq I/O path replaces cfq, and does not include the + The elevator boot parameter has been removed. The blk-mq I/O path replaces cfq, and does not include the elevator boot parameter. @@ -140,54 +140,54 @@ - - File - Description - + + File + Description + - - writes_starved - Controls how many times reads are preferred - over writes. A value of 3 means that - three read operations can be done before writes and reads - are dispatched on the same selection criteria. - Default is 3. - - - - read_expire - Sets the deadline (current time plus the - read_expire value) for read operations in milliseconds. - Default is 500. - - - - write_expire - Sets the deadline (current time plus the - write_expire value) for write operations in - milliseconds. - Default is 5000. - - - - front_merges - Enables (1) or disables (0) attempts to front - merge requests. - Default is 1. - - - fifo_batch - Sets the maximum number of requests per batch - (deadline expiration is only checked for batches). This - parameter allows to balance between latency and - throughput. When set to 1 (that is, one - request per batch), it results in "first come, first served" - behavior and usually lowest latency. Higher values usually - increase throughput. - Default is 16. - - + + writes_starved + Controls how many times reads are preferred + over writes. A value of 3 means that + three read operations can be done before writes and reads + are dispatched on the same selection criteria. + Default is 3. + + + + read_expire + Sets the deadline (current time plus the + read_expire value) for read operations in milliseconds. + Default is 500. + + + + write_expire + Sets the deadline (current time plus the + write_expire value) for write operations in + milliseconds. + Default is 5000. + + + + front_merges + Enables (1) or disables (0) attempts to front + merge requests. + Default is 1. + + + fifo_batch + Sets the maximum number of requests per batch + (deadline expiration is only checked for batches). This + parameter allows to balance between latency and + throughput. When set to 1 (that is, one + request per batch), it results in "first come, first served" + behavior and usually lowest latency. Higher values usually + increase throughput. + Default is 16. + + @@ -240,88 +240,88 @@ - - File - Description - + + File + Description + - - slice_idle - Value in milliseconds specifies how long to - idle, waiting for next request on an empty queue. - Default is 8. - - - - slice_idle_us - Same as slice_idle but in - microseconds. - Default is 8000. - - - - low_latency - Enables (1) or disables (0) BFQ's low latency mode. This - mode prioritizes certain applications (for example, if interactive) - such that they observe lower latency. - Default is 1. - - - - back_seek_max - Maximum value (in Kbytes) for backward seeking. - Default is 16384. - - - - back_seek_penalty - Used to compute the cost of backward seeking. - Default is 2. - - - - fifo_expire_async - Value (in milliseconds) is used to set the - timeout of asynchronous requests. - Default is 250. - - - - fifo_expire_sync - Value in milliseconds specifies the - timeout of synchronous requests. - Default is 125. - - - - timeout_sync - Maximum time in milliseconds that a task - (queue) is serviced after it has been selected. - Default is 124. - - - - max_budget - Limit for number of sectors that are served - at maximum within timeout_sync. If set to - 0 BFQ internally calculates a - value based on timeout_sync and an - estimated peak rate. - Default is 0 - (set to auto-tuning). - - - strict_guarantees - Enables (1) or disables (0) BFQ specific queue handling - required to give stricter bandwidth sharing guarantees - under certain conditions. - Default is 0. - - + + slice_idle + Value in milliseconds specifies how long to + idle, waiting for next request on an empty queue. + Default is 8. + + + + slice_idle_us + Same as slice_idle but in + microseconds. + Default is 8000. + + + + low_latency + Enables (1) or disables (0) BFQ's low latency mode. This + mode prioritizes certain applications (for example, if interactive) + such that they observe lower latency. + Default is 1. + + + + back_seek_max + Maximum value (in Kbytes) for backward seeking. + Default is 16384. + + + + back_seek_penalty + Used to compute the cost of backward seeking. + Default is 2. + + + + fifo_expire_async + Value (in milliseconds) is used to set the + timeout of asynchronous requests. + Default is 250. + + + + fifo_expire_sync + Value in milliseconds specifies the + timeout of synchronous requests. + Default is 125. + + + + timeout_sync + Maximum time in milliseconds that a task + (queue) is serviced after it has been selected. + Default is 124. + + + + max_budget + Limit for number of sectors that are served + at maximum within timeout_sync. If set to + 0 BFQ internally calculates a + value based on timeout_sync and an + estimated peak rate. + Default is 0 + (set to auto-tuning). + + + strict_guarantees + Enables (1) or disables (0) BFQ specific queue handling + required to give stricter bandwidth sharing guarantees + under certain conditions. + Default is 0. + + @@ -341,33 +341,33 @@ - - File - Description - + + File + Description + - - read_lat_nsec - Sets the target latency for read operations in - nanoseconds. - Default is 2000000. - - - - write_lat_nsec - Sets the target latency for write operations in - nanoseconds. - Default is 10000000. - - + + read_lat_nsec + Sets the target latency for read operations in + nanoseconds. + Default is 2000000. + + + + write_lat_nsec + Sets the target latency for write operations in + nanoseconds. + Default is 10000000. + + - + I/O barrier tuning @@ -383,11 +383,13 @@ <option>nobarrier</option> is deprecated in XFS - Note that the option has been completely deprecated - for XFS, and it is not a valid mount option in &sle; 15 SP2 and upward. Any - XFS mount command that explicitly specifies the flag will fail to mount the - file system. To prevent this from happening, make sure that no scripts or - fstab entries contain the option. + Note that the option has been completely + deprecated for XFS, and it is not a valid mount option in &sle; 15 SP2&leap; + 15.2 and upward. Any XFS mount command that explicitly specifies the + flag will fail to mount the file system. To prevent this from happening, make + sure that no scripts or fstab entries contain the + option. diff --git a/xml/uefi.xml b/xml/uefi.xml index 32677cf2ef..6159e901ab 100644 --- a/xml/uefi.xml +++ b/xml/uefi.xml @@ -183,9 +183,7 @@ even pursue both in parallel. --> legal issues, and simplifies the certification and signing step considerably. The shim loader’s job is to load a boot loader such as &grub; and verify it; this boot loader in - turn will load kernels signed by a SUSE key only. SUSE provides this - functionality since SLE11 SP3 on fresh installations with UEFI Secure Boot - enabled. + turn will load kernels signed by a SUSE key only. There are two types of trusted users: @@ -586,7 +584,9 @@ MOK - Since &sles; 15 SP3, Kexec and Kdump are supported in + Since &sles; 15 SP3&leap; 15.3, Kexec and Kdump are supported in Secure Boot mode. diff --git a/xml/virt_logs.xml b/xml/virt_logs.xml index dbb8d6dcb5..3227920953 100644 --- a/xml/virt_logs.xml +++ b/xml/virt_logs.xml @@ -12,16 +12,16 @@ yes - + When a virtualization host encounters a problem, it is often necessary to collect a detailed system report, which can be done with the help of the supportconfig tool. See - + for more information about supportconfig. - In certain cases, the information gathered by - supportconfig is insufficient, and logs generated from a + In certain cases, the information gathered by + supportconfig is insufficient, and logs generated from a custom logging or debugging configuration may be required to determine the cause of a problem. diff --git a/xml/virt_support.xml b/xml/virt_support.xml index 1a0ef01e09..daffd54cad 100644 --- a/xml/virt_support.xml +++ b/xml/virt_support.xml @@ -131,12 +131,9 @@ are not supported. - + For the maximum total virtual CPUs per host, see - recommendations - in the Virtualization Best Practices Guide regarding over-commitment of - physical CPUs. The total number of virtual CPUs should be + . The total number of virtual CPUs should be proportional to the number of available physical CPUs. @@ -189,7 +186,7 @@ - + &kvm; host limits are identical to &sls; (see the corresponding section of release notes), except for: @@ -200,7 +197,7 @@ Maximum virtual CPUs per VM: see recommendations in the Virtualization Best Practices Guide regarding over-commitment of physical CPUs at - . + . The total virtual CPUs should be proportional to the available physical CPUs. @@ -272,11 +269,11 @@ - See recommendations in the Virtualization Best Practices + See recommendations in the Virtualization Best Practices Guide regarding over-commitment of physical CPUs in - . + . The total virtual CPUs should be proportional to the - available physical CPUs + available physical CPUs. @@ -499,7 +496,7 @@ The following guest operating systems are supported as a technology preview (L2, fixes if reasonable): - SLED 15 SP3 + &sleda; 15 SP3 @@ -669,11 +666,10 @@ Offline migration scenarios - &suse; supports offline migration, powering off a guest VM, then moving - it to a host running a different SLE product, from SLE 12 to SLE 15 - SPX. The following host operating system - combinations are fully supported (L3) for migrating guests from one - host to another: + &suse; supports offline migration, powering off a guest VM, then moving it to a host + running a different &slea; product, from &slea; 12 to &slea; 15 + SPX. The following host operating system combinations are fully + supported (L3) for migrating guests from one host to another: Supported offline migration guests @@ -690,7 +686,7 @@ - Target SLES host + Target &slsa; host 12 SP3 @@ -719,7 +715,7 @@ - Source SLES host + Source &slsa; host @@ -906,12 +902,11 @@ Live migration scenarios This section lists support status of live migration scenarios when - running virtualized on top of SLES. Also, refer to the supported - live - migration requirements. The following host operating system - combinations are fully supported (L3 according to the respective - product life - cycle). + running virtualized on top of &slsa;. Also, refer to the supported + . The + following host operating system combinations are fully supported (L3 + according to the respective product life cycle). Live migration @@ -919,8 +914,8 @@ &suse; always supports live migration of virtual machines between - hosts running SLES with successive service pack numbers. For - example, from SLES 15 SP2 to 15 SP3. + hosts running &slsa; with successive service pack numbers. For + example, from &slsa; 15 SP2 to 15 SP3. @@ -928,8 +923,8 @@ &suse; strives to support live migration of virtual machines from a host running a service pack under LTSS to a host running a newer service pack, within the same major version of &sls;. For - example, virtual machine migration from a SLES 12 SP2 host to a - SLES 12 SP5 host. &suse; only performs minimal testing of + example, virtual machine migration from a &slsa; 12 SP2 host to a + &slsa; 12 SP5 host. &suse; only performs minimal testing of LTSS-to-newer migration scenarios and recommends thorough on-site testing before attempting to migrate critical virtual machines. @@ -939,8 +934,8 @@ &xen; live migration - Live migration between SLE 11 and SLE 12 is not supported because of - the different tool stack, see the + Live migration between &slea; 11 and &slea; 12 is not supported because of the different + tool stack, see the Release notes for more details. @@ -959,7 +954,7 @@ - Target SLES host + Target &slsa; host 12 SP4 @@ -985,7 +980,7 @@ - Source SLES host + Source &slsa; host @@ -1496,7 +1491,7 @@ See - + diff --git a/xml/vt_guestfs.xml b/xml/vt_guestfs.xml index de31a5e1b2..1c067c43ff 100644 --- a/xml/vt_guestfs.xml +++ b/xml/vt_guestfs.xml @@ -572,7 +572,7 @@ tmpfs /run tmpfs noauto 0 0 &prompt.user;kiwi --build /tmp/p2v.kiwi \ -d /tmp/build \ --ignore-repos \ - --add-repo http://URL/TO/SLE/REPOSITORIES \ + --add-repo http://URL_TO_REPOSITORIES \ --type iso diff --git a/xml/vt_installation.xml b/xml/vt_installation.xml index 63bd27c5d3..88276576b9 100644 --- a/xml/vt_installation.xml +++ b/xml/vt_installation.xml @@ -174,7 +174,7 @@ If everything works as expected, change the default boot kernel with &yast; and make the &xen;-enabled kernel the default. For more information about changing the default kernel, see - . + . diff --git a/xml/xen2kvm.xml b/xml/xen2kvm.xml index bdbf890dd1..0bfe5e2932 100644 --- a/xml/xen2kvm.xml +++ b/xml/xen2kvm.xml @@ -121,24 +121,6 @@ - - Preparing the virtual machine - - Conditions for skipping this step - - If running virt-v2v on &slsa; 12 SP1 or earlier, - this step can be safely skipped. This step can also be ignored if the - virtual machine is fully virtualized or if it runs on &slsa; 12 SP2 - or later. - - - - The &xen; virtual machine must have the default kernel installed. To - ensure this, run zypper in kernel-default on the - virtual machine. - - - Converting virtual machines to run under &kvm; managed by &libvirt; @@ -454,7 +436,7 @@ Passwordless SSH access - Starting with &slsa; 12 SP2, virt-v2v requires a + virt-v2v requires a passwordless SSH connection to the remote host. This means a connection using an SSH key added to the ssh-agent. See man ssh-keygen and man @@ -597,7 +579,7 @@ Id Name State ---------------------------------- 0 Domain-0 running - 1 SLES11SP3 running + 1 SLES15SP3 running [...] @@ -675,7 +657,7 @@ Id Name State INITRD_MODULES="virtio_blk virtio_pci virtio_net virtio_balloon" - For &slsa; 12, search for xenblk xennet in + For &slsa; 12, 15, and &opensuse; search for xenblk xennet in /etc/dracut.conf.d/*.conf and replace them with virtio_blk virtio_pci virtio_net virtio_balloon @@ -1168,10 +1150,5 @@ getty@xvc1.service -> /usr/lib/systemd/system/getty@xvc1.service . - - For more information on virtualization with &xen; and &kvm;, see the - &productname; documentation at - . - diff --git a/xml/xen_administrating.xml b/xml/xen_administrating.xml index d49b2a2e4d..11b1085f56 100644 --- a/xml/xen_administrating.xml +++ b/xml/xen_administrating.xml @@ -292,12 +292,11 @@ cpuid = [ - + &libvirt; also supports calculating a baseline CPU for migration. For more details, refer to - . + . diff --git a/xml/zypper.xml b/xml/zypper.xml index cfb7fe503a..fc2e3d1411 100644 --- a/xml/zypper.xml +++ b/xml/zypper.xml @@ -466,7 +466,7 @@ Zypper subcommands available from elsewhere on your $PATH Installing all needed patches - Patching &sle; is the most reliable way to install + Patching &productname; is the most reliable way to install new versions of installed packages. It guarantees that all required packages with correct versions are installed and ensures that package versions considered as conflicting are omitted. @@ -615,25 +615,25 @@ Reading installed packages... &prompt.user;zypper list-patches --cve=CVE-2016-2315,CVE-2016-2324 - + List retracted patches - In the &sle; 15 codestream, some patches are automatically - retracted. Maintenance updates are carefully tested, because there + In the &sle; 15 codestream, some patches are automatically + retracted. Maintenance updates are carefully tested, because there is a risk that an update contains a new bug. If an update proves to - contain a bug, a new update (with a higher version number) is - issued to revert the buggy update, and the buggy update is blocked + contain a bug, a new update (with a higher version number) is + issued to revert the buggy update, and the buggy update is blocked from being installed again. You can list retracted patches with zypper: &prompt.user;zypper lp --all |grep retracted -SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-1965 - | recommended | important | --- | retracted | Recommended update for multipath-tools -SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-2689 +SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-1965 + | recommended | important | --- | retracted | Recommended update for multipath-tools +SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-2689 | security | important | --- | retracted | Security update for cpio -SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-3655 - | security | important | reboot | retracted | Security update for the Linux Kernel +SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-3655 + | security | important | reboot | retracted | Security update for the Linux Kernel See complete information on a retracted (or any) patch: @@ -654,16 +654,16 @@ Severity : important Created On : Mon 16 Aug 2021 03:44:00 AM PDT Interactive : --- Summary : Security update for cpio -Description : +Description : This update for cpio fixes the following issues: - It was possible to trigger Remote code execution due to a integer overflow + It was possible to trigger Remote code execution due to a integer overflow (CVE-2021-38185, bsc#1189206) UPDATE: - This update was buggy and could lead to hangs, so it has been retracted. + This update was buggy and could lead to hangs, so it has been retracted. There will be a follow up update. - [...] + [...] @@ -737,7 +737,7 @@ cve | CVE-2019-3566 | SUSE-SLE-SERVER.. | recommended | moderate | not needed zypper update ignores problematic packages. - For example, if a package is locked, zypper update + For example, if a package is locked, zypper update omits the package, even if a higher version of it is available. Conversely, zypper patch reports a conflict if the package is considered vulnerable.