[Update: See update notes at the end of this post]
I still have Solus installed, although it is not something that I regularly use. Check HERE for my report on installing.
Today, I booted into Solus. And then I did a check for updates. It showed several. And one indicated a kernel update, but that was attached to a strange package name.
I applied the updates. And then I checked to see what kernel version had been installed. And there was no kernel there at all. The kernel had been deleted. Fortunately, I had a backup copy of the kernel, so I copied that into place. And then I rebooted. And the system froze on the login window. Perhaps all of the kernel modules had also been deleted, leaving a crippled system.
So it looks as if my Solus installation is now broken beyond repair.
I’m now wondering if this was a bad April fools joke. Or was this an intrusion into the Solus site to generate a faulty update?
At this stage, I am puzzled and looking for more information.
It looks as if I misunderstood the situation.
Apparently Solus had changed its naming convention for kernels. So I simply did not recognize that there was a kernel, since the new name was not even close to what I was looking for.
According to an announcement on Feb 03, opensuse 13.1 has reached the end of its normal support cycle. The evergreen support team will now take over.
For those still running 13.1, there isn’t any urgent action required. The same repos will be used by the evergreen team, so no repo changes are needed.
What does it mean?
As I understand it, this means that there will be no more bug fixes, with the exception of security problems that the evergreen team consider serious enough to warrant action.
That might not be quite right. I do have 13.1 installed on one of my systems. I’ll leave it there until I need the disk space for something else.
According to the announcement, the “systemd” update was the final update. However, I have not yet received that update. So maybe there’s a brief delay getting that out. When I receive that, I will know that it is the last regular update.
My experience with 13.1 has been that it was a pretty solid system. It should continue to be so, as long as the evergreen team continue with security updates. But it will eventually seem out-of-date compared to newer releases.
I’ve been making a practice of doing a test install of Tumbleweed every month. But it looks as if I will have to skip the install this month.
Up to now, the 20151002 snapshot is the only one released this month. And that was released at an inconvenient time for me following surgery. Tomorrow, we should see the RC (release candidate) for Leap 42.1, and I will be installing and testing that.
From what I see looking at bugzilla reports and at the OpenQA site, work on Tumbleweed continues. But the final tweaking to pass all of the OpenQA tests takes time, and at present the opensuse team is busy preparing the Leap release. I expect snapshot releases for Tumbleweed to speed up, once Leap has been released.
In an earlier post, I mentioned a change of direction for opensuse. The rolling releases (Tumbleweed) will continue. And the stable releases will be more closely tied to suse enterprise releases.
The name “Leap” has been chosen for the stable series, to suggest that it will advance by leaps rather than incrementally (as with Tumbleweed). And the first Leap version will be numbered 42.1.
There has been a lot of discussion on the factory mailing list and the project mailing list. You can browse those via the opensuse mailing list archive.
Yesterday’s discussion suggested that the first milestone (pre-release test version) will be available soon. This morning, there was an announcement that the milestone will be available real soon now.
When the milestone is released, I expect to download, install and test. And some readers of this blog might also want to get involved.
Opensuse Tumbleweed has been static since the 20150612 snapshot. But today the 20150630 snapshot was released. We are moving again.
As previously reported, the hold up was the switch to gcc5 and the need to recompile almost everything. Be prepared for a large update.
On my main Tumbleweed install, the update installed 4437 packages. That’s because I have Plasma5, Gnome, XFCE and LXDE desktops, and I also have latex installed.
The update when smoothly enough and after reboot the system continued to run well with the updates in place.
An announcement today hinted at the future direction of opensuse. There’s a tentative release date of around November 2. The planned release is code-named “42”, though that is unlikely to be the final name. One suggestion has been “opensuse Oak” to suggest something more stable than “opensuse Tumbleweed”.
There has been extensive discussion on mailing lists. I have not attempted to read all of the related mails, and I don’t automatically receive any of them.
In short, it will be a long term support release. The core of the release will be derive from SLE (the enterprise release of SuSE), supplemented by software that has been tested in Tumbleweed. The tentative plan, going forward, will be for “42” stable releases and Tumbleweed rolling releases.
My own plans are uncertain. I will be testing milestones for the “42” releases, as they become available. And I’ll also continue to test Tumbleweed snapshots. But I don’t know which I will be mainly using on my main desktop. That’s a decision for the future.
It has been around 10 days since the last update to opensuse Tumbleweed. That would have been snapshot 20150612. This is a brief note to explain the delays.
The Tumbleweed team are in the process of switching over to using gcc 5 as their compiler. This is an update from the earlier gcc 4.x. So now they want to recompile the complete opensuse distribution using gcc 5.
Apparently this is mostly done. But there are a few packages that are still not compiling properly with gcc 5. So this take time for people to look at the error messages and make whatever changes are needed.
I thought these three posts on cloud computing were worth reading:
- Should Companies Do Most of Their Computing in the Cloud? (Part 1)
- Should Companies Do Most of Their Computing in the Cloud? (Part 2)
- Should Companies Do Most of Their Computing in the Cloud? (Part 3)
For myself, I’m not doing much cloud computing at present. This blog would count as being in the cloud. And I guess most of my email is in the cloud. But that’s it. And the issue is, as those posts suggest, trust.
There was an announcement, early today, on the future of factory and Tumbleweed.
There was also a related message to the factory mailing list:
I have no inside information on this, so I’ll just describe what I see as the future direction. These changes will occur at about the time of the release of 13.2. That is to say, the changes are expected for November 4th, 2014.
- The old Tumbleweed will disappear. It has been criticized as not really a rolling release.
- The current factory will become the new Tumbleweed. This will truly be a rolling release.
- The name “Tumbleweed” will be retained, but for the new version.
- The name “factory” will continue to be used for the development project, but the rolling release based on factory will be the new Tumbleweed.
- Current factory users and current Tumbleweed users may need to tweak their repos. Details will be provided on Nov. 4th, and perhaps there will be other steps to smooth the transition.
- Presumably, future adopters of Tumbleweed (after Nov 4th) will be able to download a Tumbleweed iso and install that way.
Here are a couple of interesting links that I saw today:
I’ll add my own comments here.
The first of those links is about the number of adoptions of factory. It is good to see that the number has been growing. However, I’l suggest a bit of caution in interpreting them.
I’ll use myself as an example. When went with Tumbleweed on one of my systems, I first installed 13.1 as a clean install, then switched it to Tumbleweed. I expected to continue to update that until 13.2 is released.