Testing Jump 15.2

Yesterday, I took a look at the Jump 15.2 download site.

Well, more accurately, I looked to see if I could find a download site.  And it was there, with an iso ready for test.

For future reference,  follow this link to the DOWNLOAD SITE

So what is Jump 15.2?  It is really Leap 15.2, but being rebuilt in a different way.  It is a test for how 15.3 will be built.

The Jump project

With the Leap series thus far, openSUSE is using some software sources from SLE and some that came from Tumbleweed.  Those sources are then builts at OBS (the Open Build System) to produce the software release.

With the Jump project, the idea is to reduce some of the redundant operations.  So the Jump release is supposed to use rpm binary packages that were built for SLE where available, and separately build the binary packages where the source does not come directly from SLE.

Jump 15.2 is a trial run of this idea.  If it all works out, they will move to Jump 15.3, except that it might be named “Leap 15.3”.  I’m not sure whether naming decisions have been finalized.

Downloading

I downloaded “openSUSE-Jump-15.2-DVD-x86_64-Build39.13-Media.iso”.  I also downloaded the corresponding “.sha256” and the “.sha256.asc” files.  Note that some other architectures are also available at the download site.

As is my usual practice, I used “aria2c” to download the iso, and I used “wget” to download the sha256 checksum and its gpg signature.

Downloading took around 4 minutes.  Fortunately, I have a fast fiber connection.  I still remember an earlier era where downloading the DVD iso took about 1 hour.  And I even recall a still earlier time where I would start the download before going to bed, and hope it would be completed by morning.

After downloading, I used “gpg” to verify the gpg signature on the .sha256″ file.  And then I used “sha256sum” to verify that the checksum of the downloaded DVD iso was correct.

Installing

My plan was to only install this in a KVM virtual machine.  So I configured a new machine, set to install from the iso.  That is to say, the downloaded iso is used as a virtual DVD drive.  I configured it for 50G of disk space.  And I configured it to use UEFI booting.

The install itself proceeded very much like earlier installs of Leap 15.2.  I went with the defaults for partitioning.  This gave me a 500M EFI partition, a 2G swap partition and the rest of the disk space as the root partition using “btrfs”.  I did modify the “btrfs” subvolume settings.  I removed the subvolume for “/boot/grub2/i386-pc”.  I would not be needing that, since this was a UEFI install.  And I removed the subvolume for “/tmp” because I intended to configure that for mounting as “tmpfs”.

For software, I chose to install the KDE desktop.  I did check to be sure that “tcsh” would be installed.  Beyond that, this was mostly a default install.

Early in the install, it asked if I want to use online software sources.  I did not choose that.  My assumption was that the online repos would be the standard Leap 15.2 repos, and that the packages from SLE would only be available on the DVD itself.  That turned out to be a correct assumption.

On reboot, I intervened and rebooted from the rescue system (on the DVD iso), so that I could do some final tweaking.  I wanted to set it up so that “/tmp” would be mounted as “tmpfs”.  I did that by making “/etc/systemd/system/tmp.mount” a symbolic link to “/usr/share/systemd/tmp.mount”.

I then rebooted into the newly installed system.

Looking around

Jump 15.2 behaves very much like Leap 15.2.  This was not surprising.

I used Yast Software Repositories to look at the configured repos.  As expected, these were the standard Leap 15.2 repos and the DVD used for installing.  The DVD repo was disabled.

I enabled that repo, and I set it to priority 98.  This makes if favored over the standard repos.  The DVD repo has a configured repo name of “openSUSE-Jump-15.2-1”.  I should probably give the main update repo a priority of 98, if I ever intend updating this system.

I checked the package “xterm”, because that is likely to come from SLE.

# zypper se -si xterm
Loading repository data...
Reading installed packages...

S | Name      | Type    | Version    | Arch   | Repository
--+-----------+---------+------------+--------+---------------------
i | xterm     | package | 330-9.1    | x86_64 | openSUSE-Jump-15.2-1
i | xterm-bin | package | 330-9.1    | x86_64 | openSUSE-Jump-15.2-1
i | xtermset  | package | 0.5.2-1.27 | x86_64 | openSUSE-Jump-15.2-1

You can compare this to what you get on a Leap 15.2 system, to see the difference.  I also looked at that package in Yast Software Management.  The “Version” tab showed:

330-9.1-x86_64 from vendor SUSE LLC <https://www.suse.com/> (installed)

Many other packages, and probably all of the KDE desktop packages, showed the vendor as “openSUSE”.

Updating

If I normally update this from the repos, that will probably give me standard Leap 15.2 with the DVD repo disabled.  And it might not update at all with the DVD repo enabled at the priority that I used.

My tentative plan is to skip normal updates.  Instead, I will download a new DVD iso from time to time, if one becomes available.  And I will either do a new install, or I will configure the downloaded ISO as a repo (to replace the original install iso), and update from that.

Tags: ,

About Neil Rickert

Retired mathematician and computer scientist who dabbles in cognitive science.

Trackbacks / Pingbacks

  1. An update on the Jump project. | Thoughts on computing - 2020/09/23
%d bloggers like this: