I did another install of 42.3 on Thursday. I guess I’m a tad slow reporting that. This install was for Build 0283. I installed it on my main desktop. At the moment, I am still running 42.2 on that computer. I installed 42.3 on a separate area of the disk.
I do plan to soon switch to running 42.3 full time. That’s the best way of testing this beta release. The final release is due in about one month.
Downloading and installing
I followed my usual procedure. I used “aria2c” to download the iso for the DVD installer. I used “wget” to download the sha256 checksum file. Then I verified the gpg signature on the checksum file, and verified that the checksum matched the downloaded iso.
The next step was to write the iso file to a USB flash drive. I used “dd_rescue” for that. Then I booted the USB, and installed 42.3
Installation itself went well. Everything worked about as expected. Following the install, I booted into 42.3, and did a little final tweaking. And I also added additional software that is not on the install media but is in the repos.
I’m no longer doing monthly installs of Tumbleweed. But I do installs when there is a reason.
In this case it was another computer. And what use is a computer without some form of linux?
My wife purchased a new laptop for use with Windows 10. So I got the previous laptop as a hand-me-down. I already have a laptop with Windows 7, and also dual-booting to openSUSE. So I did not need another Windows 7 system. So this became my linux laptop.
Around two months ago, another computer died. That was an older desktop — the one with an nVidia graphics card. That older desktop is now in computer heaven (otherwise known as the electronics recycling center). With the arrival of this hand-me-down, I’m now back to my former number of computers. But this one has Intel graphics, so I no longer have anything with nVidia graphics.
I wanted to use an encrypted LVM for this install. And I find it more convenient to prepare the disk ahead of time.
It has been a few months since I last tried installing Tumbleweed. I wanted to install on my laptop, to test the latest version of NetworkManager.
The install went pretty well. The most obvious problem was a black screen on the first boot of the newly installed system. But that was not as bad as it sounds. I’ll give more details below. The install was for snapshot 20170314.
As is my usual practice, I used “aria2c” to download the iso, and I used “wget” to download the sha256 checksum file. Both were the 64-bit versions.
I downloaded both the DVD installer and the live rescue CD.
After downloading, I used
gpg --verify filename.sha256
to verify the gpg signature on the checksum file (where “filename” depends on whether this was for the live CD or the DVD installer.
I then used
sha256sum -c filename.sha256
to verify the checksum of the downloaded iso file.
After download, I wrote both isos to USB devices. My typical command for this is
dd_rescue filename.iso /dev/sdd
where “/dev/sdd” is the device where the USB shows up. I used a 4G USB device for the live rescue CD, and an 8G USB for the DVD installer.
I then booted the live rescue CD on two systems. It booted up without any difficulty. On the first boot, a hybrid partition was created, where any changes made can be saved to disk. Read More…
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’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.
It’s early June, and I still have not reported a couple of “installs” that I did in May. So better late than never.
I used scare quotes around “install” because I did not actually install Tumbleweed in May, though I did do some install tests. There’s not a lot to report, so this will be a short post.
I didn’t have a good reason for a full Tumbleweed install. But I decided to at least test the NET installer. It’s been a year or more since I last tried that. On my previous attempt, the NET installer was broken for use with WiFi.
I downloaded the NET installer for snapshot 20160529, and wrote that to a USB. I then disconnected the ethernet cable from my laptop and booted the NET installer.
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.
I’ve been doing an install each month, mostly to test for problems with the installer. For this month, I download snapshot 20160412. There have been more snapshots since then, but this was the one that I installed yesterday.
The live rescue CD
I also downloaded the live rescue CD at the same time. I must have started the download too soon after publication. This was the slowest download that I have done. Normally, the iso for a rescue CD downloads in a few minutes. For this download, “aria2c” was giving me an estimated download time of around 58 hours and worse. The download site was obviously busy and no mirrors were yet available.
The slow download continued for a while. Then it gave me an error indicating that the download had failed.
This month’s install was interesting.
My original plan was to install from the KDE live iso. So I downloaded “openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20160307-Media.iso” and wrote that to a USB. It booted up nicely, and ran well. Among other things, that suggests that the problems with persistent storage on the usb device have been fixed. It created a hybrid partition that was mounted as “ext4” instead of the “btrfs” that had been giving problems with the persistent hybrid partition.
On Saturday, I noticed that snapshot 20160205 had been released. So I downloaded that for this month’s install.
The install itself went quite smoothly. I installed the KDE (i.e. Plasma 5) desktop. Additionally, I installed networkmanager-gnome, so that I could test that with KDE.
My install was into the same external drive that I have previously used. It was connected to my laptop. My install was into an encrypted LVM. I imported the mount points during the partitioning section of the install.
I noticed two problems. The first was a repeat of the problem that I had n noted for my January install. Namely, the entry added to “/etc/crypttab” was bad. I had to go into rescue mode to repair that. But this was expected. That bug report is still open. So the problem was not a surprise and I knew how to deal with it. On this occasion, I used the UUID of the LUKS partition in “/etc/crypttab”.