Language Selection

English French German Italian Portuguese Spanish

SUSE 10.2 alpha 1 tested

Filed under
Reviews
SUSE
-s

Well, here we go again. With hardly any break at all those poor opensuse developers, who have once again been chained to their desktops and only let loose for the occasional bathroom break, have released the next version's alpha 1. I can feel the excitement starting to mount already -albeit a just a slight tug at this point. SUSE 10.2 alpha 1 seems little more than a bug fix/update release.

I had difficulties finding the isos on too many mirrors and the ones I found offered speeds about the size of dial-up. However, I'm sure that situation has improved greatly by today. Nevertheless, this time I downloaded the torrent and gave that a go. That worked out fairly well. At times the isos came in at about 50k/sec, but at other times it came in at over close to 300. I'd say it averaged at close to 200.

We were already informed that the graphical install was broken, but I tested it anyway. It gets through the first cd, but after the reboot, it can't restart the xserver and this is where it fails. Then, I attempted a hard drive install in text mode. I didn't have much luck with that as it got as far as package selection and errors out stating it could not read the package list. As a result, I can report that the hard drive install method is broken as well. So, I ended up booting back to my everyday desktop to burn 5 cds. Upon boot I set the options for text and went through a regular cd source install. This went fairly well. The SUSE text install is a thing of beauty. If you've never seen it, you should try it at least once. I've never seen a text install mimic its graphical counterpart in such minute detail. The only problem encountered was with the package selection which I find cumbersome, yet no reflection on SUSE. I just initially installed the default KDE package selection amounting to 1.9 gigs. I figured I'd install the rest after boot as I wanted to test the software manager anyway. The install went like clockwork. The downloading of release notes did fail as predicted, but displayed the releases notes from the cd.

I then tested the update option and it too failed. I had my SUSE 10.1 final install that I attempted to upgrade and it gets through the first cd and upon reboot it can't mount or read the remaining install cds.

After boot I saw no new graphics/images whatsoever. Even the new KDE 3.5.3 was started with the old 3.5.1 splash. Now the cat is out of the bag. This release does include the new kde 3.5.3. SUSE developers had released their rpms for 3.5.3 back when KDE announced and so it was really no surprize that it was included in the alpha. I always enjoy SUSE's implementation of KDE. They add some wonderful extras and yet don't mangle it beyond recognition or functionality. My favorite addition is the menu search, which is still present.

        

SUSE released fixes for their software manager last week as well. The only trouble was, the folks suffering from the original ill effects were the ones who probably would have problems trying to install the fixes. Fortunately, the patched libzypp is included in the alpha too. Unfortunately, I wasn't able to test it extensively as there were no updates for SUSE 10.2 alpha 1. I can report that the install of about 600 packages off the cds went just fine without error and the system as well as the apps performed quite well afterwards.

        

They updated the kernel to 2.6.16.18 on May 23 and have been patching, patching, patching on it since. Vanilla kernel 2.6.16.20 was released on June 5. Many of the other major apps have seen lots of work as well. Compiz and xgl have been improved quite a bit, Beagle's been getting a lot of attention, and zen makes several appearances in the changelog as well. But the contenders for the most worked upon is tied between amarok and yast. You can find the complete Changelog since 10.1 here.

Firefox has been updated to 1.5.0.4, gcc is now 4.1.2_20060531, whereas OpenOffice and Xorg have only seen a sub-minor version jump. Apache's not been touched, whereas php and mysql have seen just a bit of work. Just about every rpm has jumped up an internal version number or two. You can read the full rpmlist here.

        

So, that's about it this time. The graphical and harddrive source installer is broken as well as the update option. It looks like fresh text install from cds is one's only option. KDE has been updated to 3.5.3 and SUSE has shipped their patched software manager in this release. There were a lot of little big fixes and enhancements, but overall, this release seems like more of a bug fix release for 10.1, if you could in fact actually do an update. Let's hope the installer is fixed before the next release.


More in Tux Machines

Docker 1.13, Containers, and DevOps

  • Introducing Docker 1.13
    Today we’re releasing Docker 1.13 with lots of new features, improvements and fixes to help Docker users with New Year’s resolutions to build more and better container apps. Docker 1.13 builds on and improves Docker swarm mode introduced in Docker 1.12 and has lots of other fixes. Read on for Docker 1.13 highlights.
  • Docker 1.13 Officially Released, Docker for AWS and Azure Ready for Production
    Docker announced today the general availability of Docker 1.13, the third major update of the open-source application container engine for GNU/Linux, macOS, and Microsoft Windows operating systems. Docker 1.13 has been in development for the past couple of months, during which it received no less than seven RC (Release Candidate) versions that implemented numerous improvements for the new Swarm Mode introduced in Docker 1.12, a few security features, as well as a new Remote API (version 1.25) and Client.
  • Distributed Fabric: A New Architecture for Container-Based Applications
    There’s a palpable sense of excitement in the application development world around container technology. Containers bring a new level of agility and speed to app development, giving developers the ability to break large monolithic apps into small, manageable microservices that can talk to one another, be more easily tested and deployed, and operate more efficiently as a full application. However, containers also demand a new architecture for the application services managing these microservices and apps, particularly in regards to service discovery — locating and consuming the services of those microservices.
  • DevOps trends emerging for 2017 and beyond
    Finally, one of the biggest trends for 2017 will not be just a focus on engaging and implementing some of these DevOps best practices into your enterprise, but a sweeping adoption of the DevOps/agile culture. This is because one of the most important – if not the absolute most key –tenets to a successful DevOps organization is culture. The enterprises that most espouse the shared responsibility, the empowered autonomous teams, the can-do attitudes, and the continuous learning environment in which DevOps thrives will see the biggest benefits.

Kernel Space/Linux

  • Optimizing Linux for Slow Computers
    It’s interesting, to consider what constitutes a power user of an operating system. For most people in the wider world a power user is someone who knows their way around Windows and Microsoft Office a lot, and can help them get their print jobs to come out right. For those of us in our community, and in particular Linux users though it’s a more difficult thing to nail down. If you’re a LibreOffice power user like your Windows counterpart, you’ve only really scratched the surface. Even if you’ve made your Raspberry Pi do all sorts of tricks in Python from the command line, or spent a career shepherding websites onto virtual Linux machines loaded with Apache and MySQL, are you then a power user compared to the person who knows their way around the system at the lower level and has an understanding of the kernel? Probably not. It’s like climbing a mountain with false summits, there are so many layers to power usership. So while some of you readers will be au fait with your OS at its very lowest level, most of us will be somewhere intermediate. We’ll know our way around our OS in terms of the things we do with it, and while those things might be quite advanced we’ll rely on our distribution packager to take care of the vast majority of the hard work.
  • Long-Term Maintenance, or How to (Mis-)Manage Embedded Systems for 10+ Years
    In this presentation, kernel hacker Jan Lübbe will explain why apparently reasonable approaches to long-term maintenance fail and how to establish a sustainable workflow instead.
  • Linux 4.9 Is the Next Long-Term Supported Kernel Branch, Says Greg Kroah-Hartman
    Linux kernel maintainer Greg Kroah-Hartman confirmed today, January 19, 2017, in a short message, on his Google+ page, that the Linux 4.9 branch is now marked as "longterm," or as some of you know as LTS (Long-Term Support). The story behind Linux kernel 4.9 becoming the next long-term supported series dates from way before it's launch last month, on December 11, when Linus Torvalds officially announced the new branch. It all started back on August 12, 2016, when Greg Kroah-Hartman dropped a quick Google+ post to say "4.9 == next LTS kernel."
  • Maintainers Don't Scale
    First let’s look at how the kernel community works, and how a change gets merged into Linus Torvalds’ repository. Changes are submitted as patches to mailing list, then get some review and eventually get applied by a maintainer to that maintainer’s git tree. Each maintainer then sends pull request, often directly to Linus. With a few big subsystems (networking, graphics and ARM-SoC are the major ones) there’s a second or third level of sub-maintainers in. 80% of the patches get merged this way, only 20% are committed by a maintainer directly. Most maintainers are just that, a single person, and often responsible for a bunch of different areas in the kernel with corresponding different git branches and repositories. To my knowledge there are only three subsystems that have embraced group maintainership models of different kinds: TIP (x86 and core kernel), ARM-SoC and the graphics subsystem (DRM).

Graphics in Linux

  • RADV Vulkan Driver Has Geometry Shader Support For Testing
    David Airlie has published a set of 31 patches for testing that provide initial support for geometry shaders within the RADV Radeon Vulkan driver. While RadeonSI has long supported geometry shaders, it's been a bigger work item bringing it to this open-source Radeon Vulkan driver within Mesa. The patches are enough for Vulkan geometry shaders to get working on RADV, but Airlie explains that the support isn't gold: "This is a first pass at geometry shader support on radv, all the code should be here in reviewable pieces, it seems to mostly pass CTS tests but triggers some llvm 3.9 bugs around kill, and there might still be a GPU hang in here, but this should still be a good place to start reviewing."
  • libinput 1.6.0
    This release fixes the slow touchpad acceleration on touchpads with less than 1000dpi, a missing call to normalized the deltas was the source of the issue.
  • Libinput 1.6 Released With New Touchpad Acceleration
    Libinput 1.6.0 was announced a short time ago on wayland-devel.
  • Mesa 17 Gets a First Release Candidate, Final Planned for Early February 2017
    Collabora's Emil Velikov announced today, January 19, 2017, the availability of the first of many Release Candidate (RC) development versions of the upcoming and highly anticipated Mesa 17.0.0 3D Graphics Library. Mesa 17 is shaping up to be a huge milestone that should dramatically improve the performance of the bundled open-source graphics drivers for Intel, AMD Radeon, Nvidia graphics cards on a Linux-based operating system. Just the other day it enabled OpenGL 4.5 support for Intel Haswell GPUs, which is already a big achievement.

Android Leftovers

  • Donald Trump has surrendered his Android phone
    Donald Trump has given up his beloved Android phone ahead of today’s inauguration, the Associated Press reports, though it is unclear what type of device he will use in the White House. According to The New York Times, Trump is now using a more secure, encrypted handset that was approved by the Secret Service. He also has a different phone number, the Times reports, citing people close to the president-elect. Trump doesn’t use email, but he does use his Android phone to tweet. He’s also been very accessible throughout the presidential campaign and transition, taking calls from reporters, politicians, and world leaders. Malcolm Turnbull, the prime minister of Australia, called Trump to congratulate him on his electoral victory after getting his cellphone number from professional golfer Greg Norman.
  • Best affordable Android smartphones you can buy [January 2017]
    There are new smartphones hitting the market constantly, but which is the best to pick up when you’re trying to save a buck or two? We’ve seen some great launches this summer and we’re only expecting more over the coming months, but for now, let’s go over the best affordable Android smartphones you can go pick up today…
  • A list of every Samsung phone getting Android 7.0 Nougat this year
  • WatchMaker to support Gear S2 & Gear S3, 1000s of watchfaces incoming
    WatchMaker, a popular Android and Android Wear watchface platform, has some good news for our readers. They are currently in the process of expanding their supported platforms and will be targeting Tizen and its latest wearable smartwatches, the Samsung Gear S2 and Gear S3.