Most of my installs have been with the DVD image. I decided it was time to try out the live KDE image.
I mainly wanted to test out the new NetworkManager applet for KDE, and for a good test I needed to do that on my laptop. I had previously been using factory snapshots on desktop machines rather than laptops, so with an ethernet connection rather than WiFi.
It was easy enough to download the image. I looked in the download directory to see what was there, and then copied the link for the 64-bit KDE live image. I used “aria2c” to download the iso. Then I downloaded the sha256 checksum (I just appended “.sha256″ to the link I had copied). I used the checksum to verify that I had a good download. I would have preferred a gpg signature, but we make do with whatever is available.
Next, I wrote that iso file to a USB. The USB device shows up as “/dev/sdd”, so I used the command:
# dd_rescue openSUSE-Factory-KDE-Live-x86_64-Snapshot20140820-Media.iso /dev/sdd
to create the live USB. Read More…
A few days ago, I decided to install the latest factory snapshot on my older computer — the one with a Nvidia Geforce 6150LE graphics card. Mostly, it was uneventful, except for issues related to the Nvidia graphics. The install itself went smoothly. As we move closer to the release time for opensuse 13.2, the factory installs seem to be going well.
I actually installed factory snapshot 20140813, in spite of what I listed in the title above. This replaced the kubuntu 14.04 that I had previously installed in the spare partition of this computer.
As is my usual practice, I downloaded the iso image for the full DVD installer from the factory download page. I used “aria2c” for the download. I gave “aria2c” the link for the iso, and it managed to find the meta file that it needs. The download was smooth.
I am continuing to use opensuse factory. Today, it updated to the 20140805 snapshot. Factory continues to be mostly working as it should. Here I’ll post a few notes about how it looks.
The Gnome Classic extension was introduced for opensuse 13.1. However, it never quite worked. I was able to get it working by switching to “gdm” as login manager. But I don’t much care for “gdm”, so I soon switched back.
Both “kdm” and “lightdm” have menu selections to login to Gnome. However, they didn’t work. With either of those as login manager, selecting “Gnome Classic” resulted in a login to Gnome. The Classic extension was not activated.
There is a way to manually load Classic once you are in Gnome. I’ve tried that, but I don’t remember the details (it did work).
I’ve been running factory on my desktop for a while now. And, overall, it has been doing well. This updates my experience.
There was a hiatus of around three weeks between the last snapshot in June, and the 20140721 snapshot. The factory repos were not updated during that period. This was apparently due to the errors that were showing up in the openQA testing. In a way, that’s a good sign. It indicates that the opensuse team really is trying to avoid giving you a broken installation.
The 20140721 snapshot
When the 20140721 snapshot was published, there was an admission that there was still some brokenness. I updated my system anyway, running
from a text console. And that worked out pretty well. I did not run into any serious problems. Gnome 3 would now run, which it had not done after the previous update (Intel video problems). There was a minor problem with akregator. When I shutdown akregator, the KDE crash reporter shows up. It looks as if akregator is crashing during the last stages of closing. But it has already saved any volatile data, so the problem is at most minor.
A couple of notes relative to reading and posting blogs.
Double posting – they fixed it
For several months, I have been plagued with double-posting issues. No, posts have not appeared twice. But, when I follow posts via my RSS reader (akregator), many posts have shown up there twice. This has mainly been a problem with wordpress.com hosted blogs. This has been going on for several months.
When I investigated, I could see what seemed to be happening. I’ll illustrate with an example:
Yesterday, I decided to recheck the nvidia site for drivers. And it turns out that they have a new bunch of drivers there. For my card, they now have 304.123. On my last check, around two weeks ago, the latest that they had was 304.121 which did not work with a factory install — factory is mostly a preparatory version leading toward a future 13.2.
I hastily installed a recent factory snapshot on my older Dell box (the one with the nvidia card). I actually installed on an external drive, because this was mostly for testing.
After install, I proceeded to install the nvidia driver the hard way. I then rebooted to test. And it is working very well.
As previously posted, the opensuse team have turned factory into a kind of rolling release. I have it running on a test system, and it does seem reasonably stable apart from a problem with Intel graphics on Gnome.
The way it works, is that new software is first built on OBS (the Open Build Service), and snapshots are periodically taken and tested at OpenQA. Only if the tests are satisfactory, are the newly built packages moved to the factory repo.
To keep my factory install up to date, I periodically run
My current practice is to use CTRL-ALT-F1 to open a terminal (console) session, login there as root, and run the command to update from there. I most recently did that this morning. Read More…
As anticipated Mint 17 “Qiana” was released not too long after the Ubuntu 14.04 on which it is based. I waited a little longer, because I wanted to try the KDE version. When I last tried Mint, it was the Mate version. But that was a while ago. I primarily use KDE, so that seemed to be the appropriate version for me to test.
The download was of a live DVD image, which contained the installer. Downloading was simple enough. I then checked with the MD5 and SHA256 hashes. I could not find a gpg signature to check.
As preparation for booting, I copied the image to a USB. In my case, I used the command
dd_rescue linuxmint-17-kde-dvd-64bit.iso /dev/sdd
from my opensuse system.
Since getting IPv6 access, I’ve spent a little time looking into IPv6 addresses. So I thought I would share some of that on this blog.
An IPv6 address is 128 bits in length. So there won’t be a shortage anytime soon.
An address can be thought of as having three parts. There’s a prefix, typically assigned by the ISP. Then there’s a portion that can be used on a campus WAN, to distinguish different local subnets. And then there’s the local part which identifies individual computers on the LAN. The local part is often the last 64 bits of the IPv6 address.
In my case, my ISP has assigned a 60 bit prefix. My router has assigned the next 4 bits, which presumably would allow up to 16 subnets. And the last 64 bits are for the LAN portion, and are to be assigned to individual computers on the LAN. Read More…