In my previous post, I reviewed the GeckoLinux version of openSUSE 15.2. Since then, the GeckoLinux project has release their rolling distribution, based on openSUSE Tumbleweed. For the announcement check HERE.
So I downloaded the iso, and verified the sha1 checksum. Then I proceeded to do an install.
As previously, I installed only in a virtual machine. I setup the virtual machine to use UEFI booting. The downloaded iso was configured as a virtual CDROM drive. Booting from that, the live Gecko rolling release came up.
I’m normally a user of KDE/Plasma. But this time, I instead downloaded the live media for the MATE desktop. I rarely use MATE — I think the last time was with openSUSE 13.2. So this was a good time to try it on Tumbleweed.
Running the live media, there was an Install icon on the desktop. Double click on that brought up the Calamares installer. I told the installer to erase the disk and start over with a clean installation.
The release of Leap 15.2 is expected in early July. As previously posted, I have been using 15.2 on my main desktop for around 6 weeks. I update it as new releases become available. It has been at the RC level (release candidate) for a little over two weeks now.
My advice on installing is based on the release candidate. I’ll include a small set of images (printscreen images) to illustrate how the installation goes.
Preparing screen images
First a note on how I prepared these images. I downloaded the latest DVD installer. And I booted to that (as a virtual DVD drive), on a KVM virtual machine. I actually used two different virtual machines — one for legacy booting and another for UEFI booting.
I have been testing and blogging about the Alpha release for a while. But now 15.2 has reached the Beta phase. This suggests that it is closer to the final release version. As I understand it, once it reaches the beta level there are more restrictions on what software changes will be permitted.
Okay, I’m a few days late reporting this. The announcement was actually on Feb 20th:
At the time of the announcement, the software was still not available. But that showed up a few hours later:
So I have been busy over the last few days. I downloaded the DVD installer iso, and wrote that to an 8G USB drive. I used “dd_rescue” to write to the device. And then it was off to install and do some preliminary testing.
I have installed on 4 machines thus far. Two use traditional BIOS booting, and two use UEFI booting. I have secure-boot enabled on one of the two UEFI machines.
On my last post about Tumbleweed installs, I noted two serious problems:
- installs using the live media do not work correctly;
- a weak password encryption method is used.
I have since done some more installs. And, happily, both problems seem to have been resolved.
I did a new install with Tumbleweed live KDE around 10 days ago. And the install went well. On first boot, the installed system booted without any problems.
After that live install, I checked “/etc/shadow”. There was still a problem there. The encrypted password for the newly defined user was using the weak DES encryption. As before, the root password did use the more secure sha256 hashing method.
When I recently updated my Leap 15.1 systems, the “Beta” disappeared from the version information in “/etc/os-release”. That indicates that we are now seeing release candidates rather than beta versions. The final release is expected to be in late May.
After noticing this, I download the DVD installer iso so that I could try a clean install. As usual, I used “aria2c” for the download. And I also downloaded the sha256 checksum file. The gpg signature on the checksum file validated that download, and then the checksum validated the iso download.
The install itself went well. I mostly took the defaults. I selected the KDE desktop (there isn’t a default choice there). And this install was on a UEFI virtual machine (under KVM).
As indicated, I took the defaults for most choices. And, as a result, the installer used “btrfs”. I have normally avoided “btrfs”, and will probably revert to using “ext4”.
I had been watching for this. I’ve been noticing Solus for a while, and have previously reviewed earlier version. But the future of Solus was in question. Some time last year Ikey Doherty, the founder of Solus, walked away. I’m inclined to say that he abandoned the project. But others in the team picked it up, and managed to get some help from Doherty to set the project on a new footing. If you do a web search for “Ikey Doherty” you will find some of the history of this. But details of that history are beyond the scope of this blog.
So now that Solus 4.0 is out, it looks as if the team has been successful in reestablishing the project. And, naturally, I decided to give it a test run.
To download, I went to the “Download” page (linked from the announcement). There, I used the torrent downloader to retrieve the Budgie Desktop version.
KaOS-2019.02 was released recently, so I decided to test it.
I’ll note that I have tested it only in a KVM virtual machine. I have previously tested earlier KaOS versions on real hardware. But I logged into KaOS so infrequently, that I decided to only use a virtual machine install this time.
What is KaOS
KaOS is a rolling release, featuring the KDE (Plasma 5) desktop. It usually keeps up with new releases from KDE.org. The current release is using Plasma 5.15.2, KDE Frameworks 5.55.0 and QT 5.12.1.
In prior experience with earlier versions of KaOS, it often had the latest KDE release a day or two earlier than openSUSE Tumbleweed.
I downloaded the iso from the source-forge download site. I verified the provided gpg signature to check the download. I already had a copy of the signing key on my keyring, from earlier tests of KaOS.
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.