Language Selection

English French German Italian Portuguese Spanish

SUSE

OpenSUSE Leap 42.2 Beta2 OpenSUSE Leap 42.2 Beta2

Filed under
Reviews
SUSE

Leap 42.2 Beta2 is looking pretty good, except for the problems with Plasma 5 and the nouveau driver. That’s really an upstream issue (a “kde.org” issue). I hope that is fixed in time for the final release. Otherwise, I may have to give up on KDE for that box.

Read more

openSUSE Tumbleweed Is the First Linux Distro to Offer the GNOME 3.22 Desktop

Filed under
SUSE

Softpedia is being informed by openSUSE Chairman Richard Brown that the GNOME 3.22 desktop environment announced officially on September 21, 2016, is now available for installation in openSUSE Tumbleweed.

Read more

SUSE and GNOME Leftovers

Filed under
GNOME
SUSE
  • GNOME 3.22 Now Available On OpenSUSE Tumbleweed
  • GNOME 3.22 Streamlines Into Tumbleweed

    Less than 48 hours from when GNOME’s release team unveiled version 3.22 (Karlsruhe), openSUSE Tumbleweed users are getting the full upstream experience of the latest GNOME.

    Snapshot 20160921 made 3.22 available to user, but there were plenty of other snapshots during the week that brought new packages to Tumbleweed users.

    Dominique Leuenberger, a member of the openSUSE release team, wrote that there were five snapshots this week in an email to developers on the openSUSE Factory Mailing List.

    The Linux Kernel updated to 4.7.4 and VirtualBox updated a version in the 20160920 snapshot. Snapshot 20160914 updated KDE Frameworks to 5.26.0 and KDE Applications 16.08.1.

  • openSUSE Tumbleweed – Review of the Weeks 2016/38

openSUSE Leap 42.2 Linux Operating System Gets a Second Beta with KDE Plasma 5.8

Filed under
SUSE

Today, September 22, 2016, the openSUSE Project proudly announced the release and immediate availability for download of the second Beta development milestone towards the openSUSE Leap 42.2 operating system.

openSUSE Leap 42.2 Beta 2 comes with several interesting improvements and up-to-date software components, including the KDE Applications 16.08.0, KDE Frameworks 5.26.0, GStreamer 1.8.3, GTK+ 2.24.31, GTK+ 3.20.9, json-glib 1.2.2, Wireshark 2.2.0, and Xen 4.7.0_12.

Other than that, the openSUSE KDE team did a fantastic job of integrating the recently announced Beta release of the KDE Plasma 5.8 LTS desktop environment into openSUSE Leap 42.2 Beta 2 so you can get an early taste and see if there are any show stoppers that need to be addressed before the final version lands in mid-November.

Read more

Also: New Leap Beta Adds Plasma 5.8 Beta

SUSE Linux Enterprise 12 Now Includes GCC 6.2, GNU Binutils 2.26.1 & GDB 7.11.1

Filed under
SUSE

SUSE's Andreas Jaeger reports on the availability of an updated toolchain for the SUSE Linux Enterprise 12 operating system, bringing the latest tools designed for application development.

The updated toolchain included in SUSE Linux Enterprise 12 comes with some of the latest and most advanced development utilities, such as GCC (GNU Compiler Collection) 6.2, GDB (GNU Debugger) 7.11.1, and GNU Binutils 2.26.1, thus enabling app developers to use the newest technologies when creating their amazing projects.

Read more

Latest openSUSE Tumbleweed Snapshots Bring Wine 1.9.18, Glibc 2.24 & Mesa 12.0.2

Filed under
SUSE

The first snapshots for the month of September have been released for the openSUSE Tumbleweed rolling operating system, and Douglas DeMaio is here again to report on the freshly added software versions.

Read more

SUSE at Daimler and OpenSUSE Tumbleweed

Filed under
SUSE
  • Daimler AG Migrates its Mission Critical Servers to Suse Linux

    SUSE technologies are helping Daimler AG, the German automotive behemoth, to migrate a large proportion of its mission-critical servers from proprietary UNIX operating systems to 'the open and flexible Linux platform'.

  • openSUSE Tumbleweed – Review of the Weeks 2016/36

    Another week with 4 snapshots has passed, sadly some issues managed to sneak in but, as you are used to by Tumbleweed already, we managed to resolve the issues on the mailing list in no time and made sure that upcoming snapshots get the fixes asap. The snapshots published were 0901, 0905, 0907 and 0908.

Trying out openSUSE Tumbleweed

Filed under
Reviews
SUSE

While distribution-hopping is common among newcomers to Linux, longtime users tend to settle into a distribution they like and stay put thereafter. In the end, Linux distributions are more alike than different, and one's time is better spent getting real work done rather than looking for a shinier version of the operating system. Your editor, however, somehow never got that memo; that's what comes from ignoring Twitter, perhaps. So there is a new distribution on the main desktop machine; this time around it's openSUSE Tumbleweed.

Most rational users simply want a desktop system that works, is secure, and, hopefully, isn't too badly out of date. Tumbleweed is not intended for those users; instead, it is good for people who like to be on the leading edge with current versions of everything and who are not afraid of occasional breakage. It's for users who like an occasional surprise from their operating system. That sounds like just the sort of distribution your editor actively seeks out.

More to the point, Tumbleweed is a rolling distribution; rather than make regular releases that are months or years apart, the Tumbleweed developers update packages individually as new releases come out upstream. Unlike development distributions like Rawhide, Tumbleweed does not contain pre-release software. By waiting to ship a release until it has been declared stable upstream, Tumbleweed should be able to avoid the worst unpleasant surprises while keeping up with what the development community is doing.

Read more

HP Enterprise Names SUSE (Not Red Hat) Preferred Linux Partner

Filed under
SUSE

Hewlett Packard Enterprise (HPE) is playing favorites in the Linux market, selecting SUSE rather than Red Hat and Canonical Ubuntu as the company’s preferred Linux distribution partner. The move, in theory, could potentially trigger a ripple effect across corporate data centers worldwide — especially for customers that are deploying OpenStack private clouds.

Read more

Mageia and OpenSUSE Updates

Filed under
MDV
SUSE
  • Dandifying Mageia – Adding the DNF stack to Mageia

    There’s a lot of good things coming to Mageia 6: KDE Plasma 5 desktop, updates to other desktop environments, many new games, and a fresh coat of paint with a new visual style. However, there’s quite a lot of under-the-hood improvements in Mageia, too!

    Among the many less-than-visible improvements across the board is a brand new dependency resolver: DNF. DNF (Dandified Yum) is a next generation dependency resolver and high-level package management tool with an interesting history. DNF traces its ancestry to two projects: Fedora’s Yum (Yellowdog Updater, Modified) and openSUSE’s SAT Solver (libsolv). DNF was forked from Yum several years ago in order to rewrite it to use the SAT Solver library from openSUSE (which is used in their own tool, Zypper). Another goal of the fork was to massively restructure the codebase so that a sane API would be available for both extending DNF (via plugins and hooks) and building applications on top of it (such as graphical frontends and system lifecycle automation frameworks).

  • Mageia To Offer DNF, But Will Keep Using URPMI By Default

    The RPM-based Mageia Linux distribution has decided to offer Fedora's DNF forked version of Yum in their next major release.

    While Mageia 6 will be offering dnf, it's not going to be the default but will just be present on the system for those wanting to use it. The urpmi command and Mageia's existing software management tools will remain the defaults for the "foreseeable future."

  • openSUSE Tumbleweed Now Based on Linux Kernel 4.7.2, VirtualBox 5.1.4 Lands Too

    The openSUSE Project, through Douglas DeMaio, is glad to inform the openSUSE Tumbleweed community about the new package updates and improvements incorporated in the snapshots released during the week that passed.

    Now that some of you are probably attempting to install the first Beta ISOs of the upcoming openSUSE Leap 42.2 operating system, which promises to offer a strong, secure, and very stable GNU/Linux distributions to pragmatic and conservative users, those who use the openSUSE Tumbleweed rolling release are enjoying the latest software releases and technologies.

  • Akonadi/KMail issues on Tumbleweed?
Syndicate content

More in Tux Machines

KDE: Linux and Qt in Automotive, KDE Discover, Plasma5 18.01 in Slackware

  • Linux and Qt in Automotive? Let’s meet up!
    For anyone around the Gothenburg area on Feb 1st, you are most welcome to the Automotive MeetUp held at the Pelagicore and Luxoft offices. There will be talks about Qt/QML, our embedded Linux platform PELUX and some ramblings about open source in automotive by yours truly ;-)
  • What about AppImage?
    I see a lot of people asking about state of AppImage support in Discover. It’s non-existent, because AppImage does not require centralized software management interfaces like Discover and GNOME Software (or a command-line package manager). AppImage bundles are totally self-contained, and come straight from the developer with zero middlemen, and can be managed on the filesystem using your file manager This should sound awfully familiar to former Mac users (like myself), because Mac App bundles are totally self-contained, come straight from the developer with zero middlemen, and are managed using the Finder file manager.
  • What’s new for January? Plasma5 18.01, and more
    When I sat down to write a new post I noticed that I had not written a single post since the previous Plasma 5 announcement. Well, I guess the past month was a busy one. Also I bought a new e-reader (the Kobo Aura H2O 2nd edition) to replace my ageing Sony PRS-T1. That made me spend a lot of time just reading books and enjoying a proper back-lit E-ink screen. What I read? The War of the Flowers by Tad Williams, A Shadow all of Light by Fred Chappell, Persepolis Rising and several of the short stories (Drive, The Butcher of Anderson Station, The Churn and Strange Dogs) by James SA Corey and finally Red Sister by Mark Lawrence. All very much worth your time.

GNU/Linux: Live Patching, Gravity of Kubernetes, Welcome to 2018

  • How Live Patching Has Improved Xen Virtualization
    The open-source Xen virtualization hypervisor is widely deployed by enterprises and cloud providers alike, which benefit from the continuous innovation that the project delivers. In a video interview with ServerWatch, Lars Kurth, Chairman of the Xen Project Advisory Board and Director, Open Source Solutions at Citrix, details some of the recent additions to Xen and how they are helping move the project forward.
  • The Gravity of Kubernetes
    Most new internet businesses started in the foreseeable future will leverage Kubernetes (whether they realize it or not). Many old applications are migrating to Kubernetes too. Before Kubernetes, there was no standardization around a specific distributed systems platform. Just like Linux became the standard server-side operating system for a single node, Kubernetes has become the standard way to orchestrate all of the nodes in your application. With Kubernetes, distributed systems tools can have network effects. Every time someone builds a new tool for Kubernetes, it makes all the other tools better. And it further cements Kubernetes as the standard.
  • Welcome to 2018
    The image of the technology industry as a whole suffered in 2017, and that process is likely to continue this year as well. That should lead to an increased level of introspection that will certainly affect the free-software community. Many of us got into free software to, among other things, make the world a better place. It is not at all clear that all of our activities are doing that, or what we should do to change that situation. Expect a lively conversation on how our projects should be run and what they should be trying to achieve. Some of that introspection will certainly carry into projects related to machine learning and similar topics. There will be more interesting AI-related free software in 2018, but it may not all be beneficial. How well will the world be served, for example, by a highly capable, free facial-recognition system and associated global database? Our community will be no more effective than anybody else at limiting progress of potentially freedom-reducing technologies, but we should try harder to ensure that our technologies promote and support freedom to the greatest extent possible. Our 2017 predictions missed the fact that an increasing number of security problems are being found at the hardware level. We'll not make the same mistake in 2018. Much of what we think of as "hardware" has a great deal of software built into it — highly proprietary software that runs at the highest privilege levels and which is not subject to third-party review. Of course that software has bugs and security issues of its own; it couldn't really be any other way. We will see more of those issues in 2018, and many of them are likely to prove difficult to fix.

Linux Kernel Development

  • New Sound Drivers Coming In Linux 4.16 Kernel
    Due to longtime SUSE developer Takashi Iwai going on holiday the next few weeks, he has already sent in the sound driver feature updates targeting the upcoming Linux 4.16 kernel cycle. The sound subsystem in Linux 4.16 sees continued changes to the ASoC code, clean-ups to the existing drivers, and a number of new drivers.
  • Varlink: a protocol for IPC
    One of the motivations behind projects like kdbus and bus1, both of which have fallen short of mainline inclusion, is to have an interprocess communication (IPC) mechanism available early in the boot process. The D-Bus IPC mechanism has a daemon that cannot be started until filesystems are mounted and the like, but what if the early boot process wants to perform IPC? A new project, varlink, was recently announced; it aims to provide IPC from early boot onward, though it does not really address the longtime D-Bus performance complaints that also served as motivation for kdbus and bus1. The announcement came from Harald Hoyer, but he credited Kay Sievers and Lars Karlitski with much of the work. At its core, varlink is simply a JSON-based protocol that can be used to exchange messages over any connection-oriented transport. No kernel "special sauce" (such as kdbus or bus1) is needed to support it as TCP or Unix-domain sockets will provide the necessary functionality. The messages can be used as a kind of remote procedure call (RPC) using an API defined in an interface file.
  • Statistics for the 4.15 kernel
    The 4.15 kernel is likely to require a relatively long development cycle as a result of the post-rc5 merge of the kernel page-table isolation patches. That said, it should be in something close to its final form, modulo some inevitable bug fixes. The development statistics for this kernel release look fairly normal, but they do reveal an unexpectedly busy cycle overall. This development cycle was supposed to be relatively calm after the anticipated rush to get work into the 4.14 long-term-support release. But, while 4.14 ended up with 13,452 non-merge changesets at release, 4.15-rc6 already has 14,226, making it one of the busiest releases in the kernel project's history. Only 4.9 (16,214 changesets) and 4.12 (14,570) brought in more work, and 4.15 may exceed 4.12 by the time it is finished. So far, 1,707 developers have contributed to this kernel; they added 725,000 lines of code while removing 407,000, for a net growth of 318,000 lines of code.
  • A new kernel polling interface
    Polling a set of file descriptors to see which ones can perform I/O without blocking is a useful thing to do — so useful that the kernel provides three different system calls (select(), poll(), and epoll_wait() — plus some variants) to perform it. But sometimes three is not enough; there is now a proposal circulating for a fourth kernel polling interface. As is usually the case, the motivation for this change is performance. On January 4, Christoph Hellwig posted a new polling API based on the asynchronous I/O (AIO) mechanism. This may come as a surprise to some, since AIO is not the most loved of kernel interfaces and it tends not to get a lot of attention. AIO allows for the submission of I/O operations without waiting for their completion; that waiting can be done at some other time if need be. The kernel has had AIO support since the 2.5 days, but it has always been somewhat incomplete. Direct file I/O (the original use case) works well, as does network I/O. Many other types of I/O are not supported for asynchronous use, though; attempts to use the AIO interface with them will yield synchronous behavior. In a sense, polling is a natural addition to AIO; the whole point of polling is usually to avoid waiting for operations to complete.

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.