It has been a while since I last installed Tumbleweed. I decided that it was time to again check the installer.
The Tumbleweed system that I already have installed had desktops KDE, Gnome, XFCE and LXDE. But for recent intstalls (as with Leap 42.2), I have been going with KDE, Gnome, XFCE, LXQt, FVWM and MATE. So it seemed reasonable for the new Tumbleweed install to follow the same path. I also added Enlightenment for experimenting.
As usual, I downloaded via the command line. The install was for snapshot 20161128. I chose to download both the DVD iso and the rescue iso.
For the rescue iso, the commands that I used were:
wget http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso.sha256 gpg --verify openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso.sha256 aria2c -V -R http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso sha256sum -c openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso.sha256
And, for the DVD iso, I similarly used:
wget http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso.sha256 gpg --verify openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso.sha256 aria2c -V -R http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso sha256sum -c openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso.sha256
I downloaded the DVD installer, using “aria2c”. I then “burned” that to a USB. I then booted that USB to install on my main desktop.
This was a clean install. I kept the previous 42.1 on a separate disk area. That way I can boot either.
After installing, I was switching between 42.1 and 42.2. I needed to tweak the new install to suit my needs. And booting to 42.1 allowed me to get my work done. By Thursday, I had completed the switch, and I am now running 42.2.
For my other computers, I updated the already installed RC2 (release candidate 2) to the final version. For that, I plugged in the USB, and made sure that it was enabled as a repo. I then did
# zypper refresh # zypper dup
We should see 42.2 released less than two days from now. So here are a few last minute notes.
Install or update
I am planning to do a full install on my main desktop, where I have not installed the release candidates. Also, I want to see how the full install goes.
On other systems, I will simply update RC2. I checked this morning on my laptop, using
# zypper lu
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.
Beta3 was announced yesterday. So, naturally, I prepared to download and install. We are getting close to final release time for 42.2. The biggest change for Beta3, is that Plasma 5 (or KDE) is now at release 5.8.
Download and install
As with prior development releases of 42.2, the download and installation went smoothly. I followed my normal practice of “burning” the DVD image to a USB flash drive. I then booted that flash drive to start the installer.
I have done three installs. Two of those were yesterday, and the third was this morning.
As with my previous installs, I have been installing to an encrypted LVM (two installs), and to an unencrypted partition but using the home file system from an encrypted LVM on the other install.
Download and install
I saw the announcement on Thursday morning. I immediately started a download. As is my practice, I used “wget” to download the sha256 checksum file, and “aria2c” to dowload the DVD installer iso. Once downloaded, I verified the gpg signature on the sha256 checksum file, and then used that file to verify the downloaded iso. That’s probably redundant, because “aria2c” does verification checks during the download.
Next, I wrote the downloaded iso to a USB flash drive. I used an 8G flash drive, and wrote with “dd_rescue”.
Rebooting the system, I hit F12 during boot. For that computer, it brings up a BIOS boot menu which allowed me to select booting from the USB flash drive.
I used the torrent from the announcement for download (with “ktorrent” as the client). The download went well. I then checked the sha256 checksum from the announcement. and that looked good. So I “burned” the installer image to an USB flash drive with
# dd_rescue Solus-220.127.116.11.iso /dev/sdd
We are getting nearer to the release date (November) for Leap 42.2. And the first beta release was announced on Wednesday. It was time for me to get busy and do some testing.
I used “aria2c” to download the iso, and “wget” to download the sha256 checksum file. I verified the “gpg” signature on the checksum file. And then I checked the sha256 hash of the downloaded iso against the checksum file. Everything checked out.
Next, I “burned” the iso to a usb flash drive, with:
dd_rescue openSUSE-Leap-42.2-DVD-x86_64-Build0164-Media.iso /dev/sdd
(“/dev/sdd” happens to be the device name for the first USB drive on this system).
I then booted from that USB to install beta1. My first install was on Wednesday. That was to a UEFI box, with secure-boot enabled. My second install was yesterday (Thursday), to an older computer with legacy booting. Both installs went smoothly.
The quick “tl;dr” version — updates don’t work, but updating is still possible.
I installed kubuntu-16.04 in April. Although I don’t use it much, I occasionally boot into it to check a few things. Whenever I booted into Kubuntu, I looked to see if the update applet was notifying me of updates. I left the system running for an hour or more, to give it plenty of time to find out.
It never showed any updates.
So I clicked on the applet (hidden tray icon) and asked it to check for updates. It told me that my system was up to date.