Leap 15.0 was released at around 1200 UTC today, which is around 7am at my local time (Chicago time).
There appears to have been a problem with the bit torrent seeding. I hope that was fixed. For my own download, I used aria2c, which uses the meta4 link.
Today, I downloaded the DVD installer. And I then did a final test install. This went perfectly. I also downloaded the live KDE media, and booted that as a virtual DVD on a KVM virtual machine. That booted up nicely. However, the live download page has updated since my download.
My laptop is already running 15.0. And 15.0 is already installed on my main desktop, but in a different partition. I’m continuing to run 42.3 for another day or two before I switch over. My main desktop is also a file server for the home network, so I have to do the changeover at a time when it won’t disrupt anything.
A good launch
It looks as if Leap 15.0 has had a good launch. I am hearing very few problems reported at the openSUSE forums. Actually, a number of users started running 15.0 during the testing phase.
I’m expecting this to be a very good release.
OpenSUSE Leap 15.0 is expected to be released on Friday May 25th. That’s just a few days away. I have already posted two guides to different aspects of installing:
So here’s one more post before the release. I will fill in some of the gaps left by the other guides.
Some quick notes
First some notes. If you have already been testing pre-release versions of openSUSE 15.0, then now would be a good time to run
from a root command line. This should bring your system to the final release version. After that, you should update the usual way with “zypper up” or with the desktop update applet, or with Yast online update.
It is expected that Leap 15.0 will be released by the end of this month (May 2018). At present, I have Build 241.1 installed for testing. It is considered to be a release candidate.
The biggest installer change from earlier openSUSE releases is with the partitioner. So that’s what I’ll be discussing in this post.
I’ll note that the new partitioner is also being used if you install Tumbleweed. And, after installing Leap 15.0, you will also be able to access the partitioner via Yast, for making changes to your disks.
And one additional note about the installer. Before now, I have been reporting a problem with installing into an existing encrypted LVM. The problem was that the installer failed to create “/etc/crypttab”. That has now been corrected. So installing into an existing encrypted LVM should be relatively straightforward.
Starting the install
My previous post was on booting the installer. And there, I showed the possible boot screens for legacy booting or UEFI booting. Now let’s look at what we will see after booting the installer.
OpenSUSE Leap 15 is getting closer to release. The last two builds have been release candidates. Or, at least, the last two builds no longer say “Beta”, so I take them to be release candidates.
This post will be about booting the installer. And perhaps that’s no big deal. However, some folk are unsure on whether they have booted the installer in UEFI mode or in Legacy boot mode. So I am including some screen shots to help explain the difference between the boot screens. These screen shots are from when booting the install media (Build224.1) in a KVM virtual machine. Using a virtual machine is what makes it possible to take a screen shot while booting.
I’ve been testing Leap 15.0 for some time. I have not always posted about that. As long as it is working, a post would not be very interesting. However, it is time to sum up the current status.
We now have a release date for the finalized Leap 15.0. The plan is to release on May 25, at 12:00 UTC. See the announcement for more details:
I’m expecting further test releases before that date. They will mostly be release candidates. My own plans are to update my current installs for each release candidate. I probably won’t do another full install on a real machine, but I will install some of the release candidates on a KVM virtual machine.
My current usage
At present I am still using Leap 42.3 on my main desktop. Sometime within the next week or so, I plan to switch to full time use of Leap 15.0, and mostly retire 42.3.
Since my last post on Leap 15.0, Build 139.1 was released. It was time for a new install, so I downloaded the iso. And then I installed to a virtual machine.
I ran into some interesting bugs.
It told me that my EFI partition (at 33M) was too small. Well, I agree that’s small. But it is what an earlier build of 15.0 had created. It looks as if they have adjusted to a more reasonable size.
I told the installer to go ahead, in spite of the small EFI partition size. And I then ran into an additional bug. The installer said that some devices (the ones to which I was installing) did not exist. See bug 1082143 for details.
The installer allowed me to continue in spite of those errors. And the install was successful. So the errors were bogus.
A Tumbleweed install
Back to Tumbleweed. Actually, that Leap 15.0 is part of the background. I decided to try installing Tumbleweed into the same virtual machine where I had just installed Leap 15.0. However, this time I would allow it to delete everything on disk and make a fresh start.
I notice, on Thursday Jan 4th, that Build 84.1 was available at the download site. So I download, and did some testing.
As is my usual practice, I used “aria2c” to download the iso, and I used “wget” to download the checksum file. I then verified the “gpg” signature on the checksum file, after which I used the checksum to verify the downloaded iso file.
My first test was to update an existing 15.0 system. For that, I wrote the iso to a USB flash drive. I then configured that flash drive as a repo. And, following that, I used “zypper dup” to bring the existing 15.0 system up to date. When I do this, I can see that most of the updated software comes from the local USB that I configured as a repo. Some updated software comes from the online repos. The “zypper” command seems to recognize that the repo on the local USB is to be preferred to the online repo, when the software is available in both places.
There have been several Tumbleweed snapshots over the last few days. But today we saw the first with a 2018 snapshot date. So I decided to do a test install.
As usual, I used “aria2c” to download the iso (“openSUSE-Tumbleweed-DVD-x86_64-Snapshot20180101-Media.iso”). I also downloaded the sha256 checksum file. I then verified the gpg signature on the checksum file. Then I verified the checksum on the iso, to make sure that I had a good download.
A quick reminder that Leap 15.0 is still at the alpha pre-release stage.
Today, I decided to experiment with upgrading. I have openSUSE Leap 42.3 installed in a virtual machine under KVM. So I cloned that virtual machine, using the “virt-clone” command (as root). I then proceeded to upgrade it to Leap 15.0.
This is intended to be a throw-away. I’ll delete that upgraded virtual machine after a few days of testing. I may repeat the entire procedure when 15.0 is closer to final release.
I first booted the clone VM, to make sure that it could boot into Leap 42.3.
Next, I shutdown that VM. Then on the “hardware details” screen of the viewer, I configured the virtual DVD device to use the DVD installer iso for Leap 15.0. I also checked the box to enable the boot menu (under “boot options”).
The next Leap version, 15.0, is still showing as an alpha release. Still, I was happy to see the install iso for Build 79.1 show up at the download site last Wednesday. At around the same time, there was an update message on the factory mailing list, reporting the current status of Leap 15.0.
According to that update message, the current aim is for a final release in May of 2018. That seems more realistic than the earlier (Feb/March) suggestion.
When I noticed that the iso was available, I of course downloaded it. I followed my usual practice for this:
wget http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256 aria2c -V -R http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso gpg --verify openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256 sha256sum -c openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256
In turn, those commands download the sha256 checksum and the iso itself. Then they verify the gpg signature on the checksum file, and the checksum of the downloaded iso file.