Linux from suse to suse

openSUSE Leap 15.3

A brand new way of building openSUSE and a new type of a hybrid Linux distribution

Leap uses source from SUSE Linux Enterprise (SLE), which gives Leap a level of stability unmatched by other Linux distributions, and combines that with community developments to give users, developers and sysadmins the best stable Linux experience available.

Intel or AMD 64-bit desktops, laptops, and servers (x86_64)

Offline Image (4.4 GiB)

Network Image (146.0 MiB)

UEFI Arm 64-bit servers, desktops, laptops and boards (aarch64)

Offline Image (4.1 GiB)

Network Image (167.2 MiB)

PowerPC servers, not big-endian (ppc64le)

Offline Image (4.1 GiB)

Network Image (133.9 MiB)

IBM Z and LinuxONE (s390x)

Offline Image (1.7 GiB)

Network Image (104.6 MiB)

Intel or AMD 64-bit desktops, laptops, and servers (x86_64)

KVM and XEN (228.8 MiB)

MS HyperV (141.4 MiB)

VMware (142.4 MiB)

OpenStack-Cloud (217.3 MiB)

Intel or AMD 64-bit desktops, laptops, and servers (x86_64)

GNOME LiveCD (857.4 MiB)

KDE LiveCD (927.7 MiB)

Xfce LiveCD (906.9 MiB)

Rescue LiveCD (617.1 MiB)

UEFI Arm 64-bit servers, desktops, laptops and boards (aarch64)

GNOME LiveCD (826.2 MiB)

KDE LiveCD (897.1 MiB)

Xfce LiveCD (878.2 MiB)

Rescue LiveCD (597.1 MiB)

Choosing Which Media to Download

The Offline Image is typically recommended as it contains most of the packages available in the distribution and does not require a network connection during the installation.

The Network Image is recommended for users who have limited bandwidth on their internet connections, as it will only download the packages they choose to install, which is likely to be significantly less than 4.7GB.

Easy Ways to Switch to openSUSE Leap

If you’re already running openSUSE you can upgrade by booting from the DVD/USB and choosing upgrade, or carry out an ‘Online Upgrade’ in a few commands. Online Upgrade Instructions.

From an older version or other Linux distro	From Windows	From OS X
How to burn a DVD on Linux.	How to burn a DVD on Windows.	How to burn a DVD on OS X.
How to create a bootable USB stick on Linux.	How to create a Bootable USB stick on Windows.	How to create a bootable USB stick on OS X.

Documentation

System Requirements

• 2 Ghz dual core processor or better
• 2GB physical RAM + additional memory for your workload
• Over 40GB of free hard drive space
• Either a DVD drive or USB port for the installation media
• Internet access is helpful, and required for the Network Installer

Verify Your Download Before Use

Many applications can verify the checksum of a download. To verify your download can be important as it verifies you really have got the ISO file you wanted to download and not some broken version.

For each ISO, we offer a checksum file with the corresponding SHA256 sum.

For extra security, you can use GPG to verify who signed those .sha256 files.

For more help verifying your download please read Checksums Help

Источник

openSUSE Leap 15.3

A brand new way of building openSUSE and a new type of a hybrid Linux distribution

Leap uses source from SUSE Linux Enterprise (SLE), which gives Leap a level of stability unmatched by other Linux distributions, and combines that with community developments to give users, developers and sysadmins the best stable Linux experience available.

Intel or AMD 64-bit desktops, laptops, and servers (x86_64)

Образ без сети (4.4 GiB)

Образ для установки по сети (146.0 MiB)

UEFI Arm 64-bit servers, desktops, laptops and boards (aarch64)

Образ без сети (4.1 GiB)

Образ для установки по сети (167.2 MiB)

PowerPC servers, not big-endian (ppc64le)

Образ без сети (4.1 GiB)

Образ для установки по сети (133.9 MiB)

IBM Z and LinuxONE (s390x)

Образ без сети (1.7 GiB)

Образ для установки по сети (104.6 MiB)

Intel or AMD 64-bit desktops, laptops, and servers (x86_64)

KVM и XEN (228.8 MiB)

MS HyperV (141.4 MiB)

VMware (142.4 MiB)

OpenStack-Cloud (217.3 MiB)

Live-образ

Intel or AMD 64-bit desktops, laptops, and servers (x86_64)

LiveCD GNOME (857.4 MiB)

LiveCD KDE (927.7 MiB)

LiveCD Xfce (906.9 MiB)

LiveCD восстановления (617.1 MiB)

UEFI Arm 64-bit servers, desktops, laptops and boards (aarch64)

LiveCD GNOME (826.2 MiB)

LiveCD KDE (897.1 MiB)

LiveCD Xfce (878.2 MiB)

LiveCD восстановления (597.1 MiB)

Выбор носителя для загрузки

The Offline Image is typically recommended as it contains most of the packages available in the distribution and does not require a network connection during the installation.

The Network Image is recommended for users who have limited bandwidth on their internet connections, as it will only download the packages they choose to install, which is likely to be significantly less than 4.7GB.

Как перейти на openSUSE Leap

If you’re already running openSUSE you can upgrade by booting from the DVD/USB and choosing upgrade, or carry out an ‘Online Upgrade’ in a few commands. Online Upgrade Instructions.

С более старой версии или другого дистрибутива Linux	С Windows	С OS X
Как записать DVD в Linux.	Как записать DVD в Windows.	Как записать DVD в OS X.
Как создать загружаемый USB-носитель в Linux.	Как создать загружаемый USB-носитель в Windows.	Как создать загружаемый USB-носитель в OS X.

Документация

Рекомендуемые системные требования

• 2 Ghz dual core processor or better
• 2GB physical RAM + additional memory for your workload
• Over 40GB of free hard drive space
• Either a DVD drive or USB port for the installation media
• Internet access is helpful, and required for the Network Installer

Проверка загруженного образа перед использованием

Many applications can verify the checksum of a download. To verify your download can be important as it verifies you really have got the ISO file you wanted to download and not some broken version.

For each ISO, we offer a checksum file with the corresponding SHA256 sum.

For extra security, you can use GPG to verify who signed those .sha256 files.

For more help verifying your download please read Справка по контрольным суммам

Источник

SDB:System upgrade

Tested on openSUSE

A live upgrade from the prior version is officially supported. This allows to perform a complete operating system upgrade in place, without reloading everything from scratch.

Contents

Summary

This page explains how to run a series of command line steps to live upgrade your system to the latest version of openSUSE.

Doing a live upgrade has advantages as well as disadvantages.

Among the advantages are:

• You only download the packages that need to be upgraded, thus using a lot less bandwidth.
• During the upgrade, you can still use your workstation (even if this is not recommended); the only downtime will be the reboot after the upgrade.
• You do not have to use a DVD, nor do you need a DVD writer. You do not have to use a USB key. This because you boot your existing system, and install everything from the net.

• If, for any reason, the upgrade is interrupted (e.g. power outages, network disconnect) and the process cannot continue, you could be left with a broken system (that depends on where the process stopped of course).
• If you have multiple systems to upgrade, you use bandwidth each time, so it might be better to download an ISO image.
• It does not do all of the cleanup and maintenance that an offline DVD Upgrade does.

Other possibility: Offline upgrade, a.k.a. traditional or DVD upgrade. For more information, read offline upgrade. This upgrade method is safer and more versatile. Unless you have a good reason to do otherwise, use the offline upgrade method.

Supported scenarios

Update from 32-bit openSUSE to Leap is not supported. Leap is 64-bit only. If your hardware has x86_64 support, you can upgrade 13.2 to 64-bit first. See 32-bit to 64-bit upgrade.

On the AArch64 architecture (64-bit ARM), upgrading from Leap 15.0 to Leap 15.1 is not supported. Please do a fresh installation on those systems.

Be aware that, in principle, this upgrade process is considered “best effort” only. This means that due to some third-party packages and the myriad of possible configurations, it is possible for some combinations to cause failure upon upgrade.

Also, remember these important rules:

• All important data must be backed up prior to beginning the upgrade process.
• You must update your system with the latest updates for the release you are currently running before running zypper dup.
• You must only zypper dup to the next release. Hopping over a release, e.g., going from 42.1 -> 15.1, is not supported.

Note: according to factory mail list it has been tested in openQA direct upgrade from openSUSE 12.x to Tumbleweed (till snapshot 1101). Currently (Nov 2017) the process is tested from 13.x and 42.x directly to TW. However, this does not mean that you should do it! You could hit an unknown problem.

Warning: Do not skip a release when upgrading! Example: do not upgrade from 15.1 to 15.3. Instead, from 15.1 upgrade to 15.2, and only then from 15.2 to upgrade to 15.3.

Note: for 15.3 specifically only the upgrade from a fully updated 15.2 is supported. See the Release Notes, chapter 2.1 (Seamless upgrade from openSUSE Leap 15.2).

Migration to SUSE Linux Enterprise

If you’re interested in migration from openSUSE Leap to SUSE Linux Enterprise. Then please follow our guide for migrating to SUSE Linux Enterprise.

Making sure you are up to date

The supported starting point is the last openSUSE release with all current updates applied. This does not include arbitrary openSUSE Build Service repositories you may have added. We recommend that you disable all OBS repositories first, perform the upgrade, then reenable them. The following steps show you how to update your openSUSE distribution to the current packages before upgrading to the next version.

Note: the advice to remove extra repositories may be deprecated.

Find out what version of openSUSE you currently have as follows:

Extra repositories handling

Zypper dup can now better handle extra repositories during upgrade. Removing a repository causes the problem that every package that was installed from it will revert to another repository (if found), or deleted, or left at the old version, depending on the administrator choices. It may be a better method to leave the repository active. A typical example would be Packman.

However, a system upgrade can be the perfect occasion to remove some repositories, as too many repositories complicates maintenance. For example, suppose we have some Xfce or Plasma repository we activated to get newer versions (say we needed a feature or correct a problem that was handled in a newer version): now would be the perfect occasion to revert to the mainline version. It would be the chance to consider removing all HOME repositories that we really do not need.

Each repo we remove will cause zypper to ask what to do with packages installed from them: keep or upgrade with vendor change. The policy would be «keep» if we intend to add back the repository after system upgrade, or «update» otherwise. We could use «—allow-vendor-change» but this may have unintended consequences as zypper will then evaluate if any package would be better to obtain a version from another repo, considering the priorities they have.

Thus, you have to choose what road to take, as the administrator 😉

Graphical tool

Command line

1. Check if the update repository already exists and is enabled and update before upgrading.

Check if http://download.opensuse.org/update/leap/15.0/oss/ (for openSUSE Leap 15 or later, replace 15.0 with your version) exists in one of the URI column values, and Yes in column Enabled, like the example below,

If the Enabled column says No, enable it by issuing the command

If it exists and has been enabled, continue to step 3.

2. Add update-repository

(If your pre-upgrade system is 15.0 and the update repository doesn’t already exist):

The openSUSE Leap 15.3 adds two additional update repositories one for openSUSE Backports and one for SUSE Linux Enterprise, these additional repositories are used during online installation and delivered to Leap 15.3 system via a maintenance update of openSUSE-release with Leap 15.3 GA. This is covered in depth in the Release notes.

3. Move /var/cache to a separate subvolume

/var/cache contains a lot of very volatile data, such as the Zypper cache with RPM packages in different versions for each update. As a result of storing data that is mostly redundant but highly volatile, the amount of disk space a snapshot occupies can increase very fast. For solving this problem move /var/cache to a separate subvolume:

• Find out the device name of the root file system:

• Identify the parent subvolume of all the other subvolumes. For openSUSE 15.1 installations, this is a subvolume named with @:

• If the output of this command is empty, you do not have a subvolume named with @. In that case, you may be able to proceed with subvolume ID 5 which was used in older versions of openSUSE.
• Mount the specific subvolume to a temporary mount point:

• /mnt/var/cache can already exist and could be the same directory as /var/cache. To avoid data loss, move it:

• If there is now a directory /var/cache.old, move it to the new location:

• After moving (optionally) remove /mnt/var/cache.old:

• Unmount the subvolume from the temporary mount point:

• Add an entry to /etc/fstab for the new /var/cache subvolume. Use an existing subvolume as a template to copy from. Make sure to leave the UUID untouched (this is the root file system’s UUID) and change the subvolume name and its mount point consistently to /var/cache.
• Mount the new subvolume as specified in /etc/fstab:

4. Update system to the latest packages

For more information, read Zypper Usage.

Running the Upgrade

The following steps will show you how to upgrade your openSUSE distribution to the following release (eg. 15.2 -> 15.3). If your current version is 15.1 or older, any third party or OBS repositories might cause troubles, so it is prudent to disable or remove some of them before proceeding. If you’re already on 15.2 or newer, this advice is deprecated.

Before you begin

Make sure that you read the list of annoying bugs for the new version you are going to install. Some of them could affect the update process. Usually, some solution or workaround is listed alongside the bug, so make sure that you are prepared for upcoming problems.

Also, read the Release Notes which list changes and glitches in the new release.

Upgrading from the command line

The following steps show how to upgrade to 15.3:

5. Update the repos

6. Refresh with the new repos

7. Execute the full distribution upgrade

Now execute the full distribution upgrade.

With the above command, zypper will download all packages in advance — which is more reliable if your internet connection may fail. To download packages in heaps and install them in heaps, use:

Once the dup is finished, openSUSE sets the releasever variable to the new version.

8. Reboot

After upgrading, a reboot is recommended to start the new kernel and newer versions of everything.

9. Add extra repositories

Executing zypper up may be enough to update your software from these extra repositories.

Источник