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.
Ubuntu-18.04 was announced yesterday. I had been waiting for this. So I soon started a download. I used torrent for the download. I also downloaded the checksum file and its gpg signature. After the download completed, I verified the gpg signature for the checksum file, and then I verified the checksum for the install iso.
My earlier install of 16.04 was intended as a trial run for 18.04. As in that case, my plan was to install in an existing encrypted LVM. I expected this to be easy. But it wasn’t.
The install went smoothly enough. But the installed system would not boot. I was never prompted for the encryption key.
I eventually got it working. Having found out where I went wrong, I did another install, this time to a KVM virtual machine. And that install worked out very well. So that’s what I will describe.
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.
In recent tests with openSUSE Leap 15.0 and with Tumbleweed, I have been testing out pam_kwallet. It seems to work pretty well. So I have since converted another Tumbleweed system to using pam_kwallet. However, I am not using pam_kwallet with Leap 42.3, on the grand principle that if it ain’t broke, don’t fix it.
Leap 15.0 should be released some time in May. So pam_kwallet is something you might want to think about when you install it.
What is pam_kwallet?
First things first, so I should first explain “kwallet”, sometimes called “kdewallet”. It is a protected place for storing passwords that are used by KDE applications. Typically, it is used for the WiFi passphrase, for web password and email passwords. This, of course, depends on what applications you are using for web browing and for email.
Yes, Ubuntu 16.04 is old hat. This was a recent re-release, but who cares with 18.04 just around the corner. But I decided to install anyway, and I’ll shortly explain why.
The problem with installing Ubuntu into an existing encrypted LVM, is that it doesn’t boot. You have to go into repair mode to fix it. The reason for this is that the file “/etc/crypttab” is not created by the install. And the system won’t boot unless that is created and the “initrd” file is generated so as to contain a copy of that file. That’s needed to handle the crypto early in the boot process.
What has changed?
I’ve done this before, and blogged about it. So what’s new?
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.
Since my last post on 15.0, there have been several new beta releases. We have seen Build115.1, Build 124.1, Build 127.1, Build 128.1 and Build 129.1.
With that many builds, I have not been downloading them all. I have been updating my 15.0 systems. I am updating them in the same way that I update openSUSE Tumbleweed. That is, I am using
to update from the repos. My most recent install attempts have been with Build127.1, though most of my systems are now updated to the latest version.
Things are mostly going well with 15.0. The final release is still planned for May. But if you want to take a look at pre-release versions, then now is a good time to try.
What I have tested is mainly working well. There are still a few bugs in the partitioner, as used for install. Some of those bugs have already been fixed in the latest updates.
Build 109.3 of Leap 15.0 was announced on Friday. So I download and installed. With build 109.3, it is now announcing itself as a Beta release. Previous releases that I tested have indicated that they were Alpha releases.
I followed my usual practice of downloading with “aria2c”. I am using the download site download.opensuse.org/distribution/leap/15.0/iso/. I first used “wget” to download “openSUSE-Leap-15.0-DVD-x86_64-Build109.3-Media.iso.sha256” (the checksum file). I then verified its gpg signature. Next, I downloaded the iso itself. And I used “sha256sum” to verify the sha256 checksum. And, following that, I wrote the iso to an 8G USB flash drive. Read More…