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”.
Some folk like to have more than one linux version installed on a computer. And, possibly, they also have Windows installed. So that’s a multi-boot situation.
I’m doing that. In this post, I’ll describe how I am doing it.
When I first did multi-boot, I was somewhat haphazard in how I organized things. But by now, based on my experience, I’m a bit more organized.
I’ll describe my laptop, and how I am using that. I have Windows 7 installed (that came on the computer when I purchased it). And I currently have opensuse 13.2, opensuse Leap 42.1 and opensuse Tumbleweed all installed.
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.
For this month, I installed Tumbleweed on my laptop. I had installed Leap 42.1 to overwrite my previous Tumbleweed install on that laptop.
This computer uses legacy booting. I gave Tumbleweed a 40G partition, which I formatted as “ext4”. I also allowed it to use the swap and home file systems from my encrypted LVM on that computer.
I mounted the home file system to “/xhome”. That left “/home” as part of the root file system. So I created symbolic links into “/xhome” for most of my saved files. Doing it this way allows me to avoid conflicting desktop configurations. So the new install has its own “.config” and “.kde4”, but uses the same “$HOME/bin” and document directories as my other installs on that box. Read More…