I still have a lot to test following that Tumbleweed update. I did encounter some issues. I’ll comment on those here.
Crash during update
On one system, the update completed. But I could not logout from the desktop. So I used CTRL-ALT-BACKSPACE to crash the desktop, then rebooted on the sddm login screen.
On another system, where I was using “gdm” as login manager, the desktop seemed to crash in the middle of the update, leaving a blank screen. I logged in remotely (using “ssh”) to see what was happening. The desktop session appeared to have disappeared (I checked processes that I owned, and none were running except those from the ssh login).
I haven’t posted for a while, for various reasons. A major reason was health issues. I had an unanticipated hospitalization. This was due to complications following an appendectomy.
Everything seems to be turning out okay. I’m well on the path to recovery.
The beta1 release was announced on Thursday. So I downloaded and installed.
The downloading went smoothly. I used “aria2c” to download “openSUSE-Leap-42.1-DVD-x86_64-Build0186-Media.iso” (the DVD installer iso for beta1). Then I used “wget” to download the sha256 checksum file “openSUSE-Leap-42.1-DVD-x86_64-Build0186-Media.iso.sha256”. Then I used “gpg” to verify the signature of that checksum file. Finally, I used the “sha256sum” command to computer the checksum of the downloaded iso, and compare that to the checksum in the “.sha256” file.
A bit more detail. On the download page for the development version, I checked the box for “Pick Mirror” and clicked “download”. That gave me a list of mirrors and it gave me the url for the meta4 download link. I copied that link, and used it as an argument for “aria2c” on a command line to download the iso. Then I replaced the final “.meta4” with “.sha256” in that link, and used that with “wget” to download the sha256 checksum file. Read More…
My previous post was on setting up an NFS server. In this one, I will describe how I setup an NFS client.
My first decision was to use “autofs” (the automounter). With “autofs”, the NFS network share is not mounted until there is an attempt to access it.
Without autofs, you can get into a situation where you cannot boot the client computer unless the NFS server is running. So I prefer auto-mounting to avoid that kind of difficulty. Read More…
Last week I posted about sharing updates via NFS. In this post, I’ll describe how to setup an NFS server with opensuse. I’ll later add a post about setting up an NFS client. Both are relatively simple.
To setup the NFS server, I needed to install “nfs-kernel-server” and “yast2-nfs-server”. Both are on the install DVD and both are in the standard repos. When I first did this, I install “nfs-kernel-server” during my original install of the system. Then when I tried to configure, I noticed that “yast2-nfs-server” was missing, so I installed that.
For this month, I decided to install the 20150903 Tumbleweed snapshot. I planned to install on an external drive, and to install only KDE (i.e. Plasma 5).
This install turned out to be a disaster. But that’s why I do these monthly installs. I have reported the problems as bug 944662.
The downloading went well. I used “aria2c” to download “openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150903-Media.iso”. And I used “wget” to download the checksum file “openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150903-Media.iso.sha256”. I then used “gpg” to verify the signature on the checksum file. And I used “sha256sum” to compare the checksum of the downloaded iso with that in the checksum file. All went well.
Milestone 2 for Leap 42.1 was announced on Friday. So, naturally, I downloaded the install DVD iso, and attempted an install.
Both the download and the install went quite well. As usual, I wrote the iso to a USB flash drive, and used that for installing. I installed Leap on its own (unencrypted) partition, but with swap and home coming from an existing encrypted LVM. I mounted the home volume from the LVM as “/xhome”, so that “/home” is actually part of the root partition. The idea was that users could symlink back to files in “/xhome” to make their usual files/directories available. But desktop configuration would be kept separate to avoid conflicts between different desktop versions.
Trouble began with the first boot. I was prompted for the encryption key, but the system was not reading the keyboard and this prevented entering the key.
I have opensuse on my main desktop, on my laptop and on a test machine.
When there’s an update, the update has to be downloaded for each machine. That raises the question of whether they can be downloaded just once, and then used on multiple systems.
There was a discussion of this question on the opensuse mailing list last May (beginning May 21, 2015). I liked the suggestion offered by Carlos. So I decided to give it a try. I didn’t do it exactly as Carlos suggested, so this post will describe what I actually did.
I saw a Distrowatch announcement of a new release of KaOS, so decided to give it a try. From there, I followed the link to the release announcement.
My previous experience with KaOS was in April, where it failed to install. This time, I had a better experience.
KaOS is a rolling KDE based distro. It is using plasma 5. The new version came with a beta release of plasma 5, so gives me an early look of what I can soon expect to see in opensuse Tumbleweed. The downloaded system uses a release-candidate for Plasma 5.4.
I check the torrent link, but that seemed to be for an earlier release. My understanding is that torrent downloads are provided by users, and I probably looked before they had set it up for the new release.
I’ve been doing an install of the month, in order to test Tumbleweed installation. For August, I installed in an alternate partition on my main desktop system.
The Tumbleweed install media have been broken for the last two weeks. If used from a USB flash drive, the installer cannot be booted in UEFI mode. Apparently it can still be booted with UEFI if it is actually burned to a DVD. However, I prefer to install with a USB, so I decided to give it a try in spite of the problems. I had actually wanted to test whether a UEFI install can be done when the install media is not UEFI bootable. So this was a good time to test that.
I downloaded the install DVD iso for the 20150802 snapshot. As usual, I used “aria2c” to download. That went well. I also used “wget” to download the file containing the sha256 checksum. I verified the gpg signature on that checksum file. Then I compared the checksum in that file with the checksum that I could compute from the downloaded iso. And all was fine.