I checked the download site for openSUSE 15.0. And I noticed that there was a newer version available. This one is Build 65.1. My previous look at 15.0 had been for Build 48.1.
As you might expect, I downloaded the iso for the DVD installer. I also downloaded the sha256 checksum file. I then verified the gpg signature on the checksum file, and used the checksum file to verify the download of the iso.
The next step was to “burn” the iso to a USB device. I used a 4G USB flash drive for that purpose.
After downloading, I first decided to update the openSUSE 15.0 from my previous install to a KVM virtual machine. I configured the installer USB as a local repo. And I then brought the system up to date with
After updating, and rebooting, the system seemed to run well. Or, so I thought. But after booting again today, I noticed that it had no network. It seems that the update changed the network setup. The ethernet interface is now “eth0”. It was previously “ens3”. So I had to reconfigure for the new interface name before I could make an ethernet connection. I used Yast network settings to reconfigure.
Work on Leap 15 is underway. There was a short discussion on the factory mailing list, beginning HERE.
Two months after my last status update Leap 15 is almost rolling. Following SLE 15 I’d like to aim for a release in April.
It is worth reading that whole message, and perhaps the other emails that follow it. As the message indicates, there is now a download site for isos, in case you want to try Leap 15 for yourself.
I went to the openQA site to look at failures. And they didn’t seem too bad. So I downloaded an iso from there. It was “openSUSE-Leap-15.0-DVD-x86_64-Build48.1-Media.iso”.
Last month, I created a Tumbleweed Virtual Machine (or VM), using KVM. Yesterday’s project was to install into that existing VM. I wanted a clean install, retaining “/home” but reformatting everything else.
Fortunately, that previous install was for UEFI booting. I’m not sure how easy it would have been to do new install into the same BIOS based virtual machine.
I started by downloading the DVD installer for Tumbleweed snapshot 20171007. As usual, I downloaded the sha256 checksum file with “wget”, and I downloaded the iso itself using “aria2c”.
I then verified the gpg signature on the sha256 checksum file, using gpg. Then I used “sha256sum -c” to verify the checksum of the download iso file.
I have previously reported on KaOS, in 2015. I have actually kept it installed since August 2015. When I saw the announcement for 2017.01, I decided that it was time for a re-install. I’ll note that I could have just updated the already installed version, but it seemed like time for a fresh start.
What is KaOS?
KaOS is a rolling distribution, based on KDE.
I am a KDE user, with openSUSE Leap (currently at 42.2). But I also keep openSUSE Tumbleweed installed for looking at what will be coming up. And I’m using KaOS as an alternative view of what is going to be showing up in the future.
I have not used KaOS extensively, except for occasion testing and occasional updating. I’m expecting to continue that practice with the new install.
I downloaded from the download site listed on the announcement. I then checked the md5sum for the download. There did not appear to be a gpg signature that I could check.
Release candidate 2 (or RC2) is now out. It was announced earlier today:
As you might expect, I downloaded the iso for the DVD installer, and “burned” that to a USB flash drive. I then did an install using it.
The install went quite well. I followed the same general method as in my install for RC1.
I noticed one change. Early in the install, I was told about “Mesa-dri-nouveau”. This is a new package, broken out from mesa. The notification asked me whether I wanted to accept this package. If I did not accept, then 3D would be emulated in software.
I accepted the package. I cannot test it otherwise.
Unfortunately, it does not work well enough with my nvidia card.
I’m a tad slow reporting this.
Release candidate 1 (or RC1) for 42.2 was announced on Tuesday. I downloaded the DVD installer, and proceeded to install on three computers.
For the most part, everything went well. I noticed a couple of cosmetic issues. And Plasma 5 still won’t run under “nouveau” (with a Nvidia card). But at least there is a good workaround for that. I’ll discuss these in more detail below.
Gnome shows as version 3.20.2. To find that, I logged into Gnome, right-clicked on the desktop and selected “Settings”. On the window that showed up, I clicked “Details” to find the version.
I’ve simplified my life, so I am no longer doing regular monthly installs. But I still do occasional installs.
In this case, the occasion was a topic at opensuse forums:
A user was not sure how to install without a network. So I decided to do an install, to make sure that this was still possible.
I began by downloading the latest snapshot. I first used
to download the sha256 checksum file. That’s a small file (654 bytes), and I find it easier to use “wget” for small files. I then verified that file, using
gpg --verify openSUSE-Tumbleweed-DVD-x86_64-Snapshot20160813-Media.iso.sha256
The file itself has a gpg signature, so checking that signature is sufficient to verify the download.
Ubuntu 16.04, in several different varieties, came out last week. So I decided to give the kubuntu variant a try. I planned to install in an existing LVM. I knew, from previous experience, that this could be tricky. And, to make it more tricky, I wanted “/boot” to be inside that encrypted LVM.
It didn’t quite work out. I am successfully booting it using the grub2-efi from opensuse. I was unable to get the grub-efi from kubuntu to work.
I planned to install this to replace an experimental Tumbleweed. I had originally set that up a year ago, to test using opensuse with “/boot” part of the encrypted LVM. That test is now well past, and the opensuse bugs have been fixed. So that disk space was free for kubuntu.
For this month, I used an external drive. It’s an old ATA 80G drive that I have mounted in a USB disk enclosure. I connected the external drive to my laptop, so that I could do more testing of WiFi and NetworkManager.
I installed snapshot 20160107. I did that install yesterday. And a few hours later, snapshot 20160108 was announced. Well never mind that. I was testing for install problems.
To install, I downloaded the DVD installer (64-bit), and wrote that to a USB flash drive using the “dd_rescue” command.
I plugged installer USB into my laptop. At this stage, the external drive (the install destination) was not connected. This was deliberate. That drive is bootable. When I tell my system to boot from USB, I am not given a choice of USB. So, to avoid any ambiguity, I made sure that the installer USB was the only one connected. I should add that my laptop uses legacy booting.
I said there would not be a Tumbleweed install this month. But I changed my mind on that. Snapshot 20151017 came out after I had finished my Leap 42.1-RC1 installs, and I had a little free time.
For this install, I used a 1T disk. It had previously been used for Windows. I plugged the disk into a SATA disk docking station, and planned to use the entire disk for the Tumbleweed install. I connected the docking station to a UEFI computer (via a USB cable).
My plan was to try installing to an encrypted LVM. There are some open bug reports indicating problems, so I wanted to see what would happen.