Language Selection

English French German Italian Portuguese Spanish

SUSE

openSUSE Tumbleweed vs leap: What is the Difference?

Filed under
SUSE

Before talking about the differences between these versions of openSUSE, let’s have a brief look at its background and features. Earlier it was known as SUSE Linux but after a software company Novell acquired SUSE Linux in February 2004, Novell decided to release SUSE Linux Professional with 100% open source products, and as an open source project, this Linux got its prefix i.e Open. Later it split from Novell and became a separate brand.

openSUSE inherits its properties from SUSE Linux Professional and the successor of the same. SUSE also offers open source-based enterprise-class OS known as SUSE Linux Enterprise Server.

openSUSE Linux community is backed by the SUSE for further research and developments. It uses the easy-to-use YaST package management system and has great advantages for a small and medium-sized enterprise server. Using YaST2 can make the configuration of the server simpler and faster. SuSE Enterprise Linux can be used for large server systems too. When it comes to Linux, everyone knows that Linux is a very secure OS, and openSUSE is not an exception. Apart from the YaST Package manager, it also supports self-developed Zypper (ZYpp) and RPM. It uses KDE5 as the default desktop environment and also provides the GNOME, MATE, LXQt, Xfce…

Now come to the main agenda of the article which is the difference between openSUSE Tumbleweed and Leap?

Read more

SUSE: Release of SUSE CaaS Platform, SUSE Enterprise Storage, SUSE Linux Enterprise 15 Service Pack 1 and More

Filed under
SUSE
  • SUSE CaaS Platform 4.0 Beta 3 is out!

    SUSE CaaS Platform 4.0 is built on top of SLE 15 SP1 and requires either the JeOS version shipped from the product repositories or a regular SLE 15 SP1 installation.
    Please note that SLE 15 SP1 is now officially out! Check out the official announcement for more information.
    Thus you should not use a SLES 15 SP1 environment with the SLE Beta Registration Code anymore. Because the SLE Beta Registration Code has expired now, but you can either use your regular SLE Registration Code or use a Trial.

  • SUSE Enterprise Storage 6 Now Available

    With the current increase in data creation, increased costs and flat to lower budgets, IT organizations are looking for ways to deploy highly scalable and resilient storage solutions that manage data growth and complexity, reduce costs and seamlessly adapt to changing demands. Today we are pleased to announce the general availability of SUSE Enterprise Storage 6, the latest release of the award-winning SUSE software-defined storage solution designed to meet the demands of the data explosion.

  • What’s New for SUSE Linux Enterprise Server for Arm 15 SP1

    Happy Birthday! It’s been 1 year since we introduced the world’s first multimodal OS supporting 64-bit Arm systems (AArch64 architecture), SUSE Linux Enterprise Server for Arm 15. Enterprise early adopters and developers of Ceph-based storage and industrial automation systems can gain faster time to market for innovative Arm-based server and Internet of Things (IoT) solutions. SUSE Linux Enterprise Server for Arm is tested with a broad set of Arm System-on-a-Chip (SoC) processors, enabling enterprise-class security and greater reliability. And with your choice of Standard or Premium Support subscriptions you can get the latest security patches and fixes, and spend less time on problem resolution as compared to maintaining your own Linux distribution.

  • Are you ready for the world’s first Multimodal Operating System

    Today, SUSE releases SUSE Linux Enterprise 15 Service Pack 1, marking the one-year anniversary since we launched the world’s first multimodal OS. SUSE Linux Enterprise 15 SP1 advances the multimodal OS model by enhancing the core tenets of common code base, modularity and community development while hardening business-critical attributes such as data security, reduced downtime and optimized workloads.

  • The future of OpenStack?

    Before we can answer these questions, let’s take a look at its past to give some context. Since its original release in 2010 as a joint venture by Rackspace and NASA, and its subsequent spin-off into a separate open source foundation in 2012, OpenStack has seen growth and hype that was almost unparalleled.
    I was fortunate enough to attend the Paris OpenStack Summit in 2014, where Mark Collier was famously driven onto stage for a keynote in one of the BMW electric sports cars. The event was huge and was packed with attendees and sponsors – almost every large technology company you can think of was there. Marketing budget had clearly been splurged in a big way on this event with lots of pizazz and fancy swag to be had from the various vendor booths.
    Cycle forward 4 years to the next OpenStack Summit I attended – Vancouver in May 2018. This was a very different affair – most of the tech behemoths were no longer sponsoring, and while there were some nice pieces of swag for attendees to take home, it was clear that marketing budgets had been reduced as the hype had decreased. There were less attendees, less expensive giveaways, but that ever-present buzz of open source collaboration that has always been a part of OpenStack was still there. Users were still sharing their stories, and developers and engineers were sharing their learnings with each other, just on a slightly smaller scale.

  • SUSE Academic Program to be present at 2019 UCISA SSG Conference

    Engaging with the community has always been important for SUSE and this is no different for our Academic Program. That is why next week, the SUSE Academic Program is excited to attend and participate in a three day event hosted by one of the most respected networks in UK education.

Red Hat and SUSE Leftovers

Filed under
Red Hat
SUSE
  • How a service mesh helps manage distributed microservices

    A service mesh brings security, resiliency, and visibility to service communications, so developers don’t have to

  • RHEL 8: 'the foundation for digital transformation'
  • 7 infrastructure performance and scaling tools you should be using

    Sysadmins, site reliability engineers (SREs), and cloud operators all too often struggle to feel confident in their infrastructure as it scales up. Also too often, they think the only way to solve their challenges is to write a tool for in-house use. Fortunately, there are options. There are many open source tools available to test an infrastructure's performance. Here are my favorites.

  • Future of CRDs: Structural Schemas

    Authors: Stefan Schimanski (Red Hat)

    CustomResourceDefinitions were introduced roughly two years ago as the primary way to extend the Kubernetes API with custom resources. From the beginning they stored arbitrary JSON data, with the exception that kind, apiVersion and metadata had to follow the Kubernetes API conventions. In Kubernetes 1.8 CRDs gained the ability to define an optional OpenAPI v3 based validation schema.

    By the nature of OpenAPI specifications though—only describing what must be there, not what shouldn’t, and by being potentially incomplete specifications—the Kubernetes API server never knew the complete structure of CustomResource instances. As a consequence, kube-apiserver—until today—stores all JSON data received in an API request (if it validates against the OpenAPI spec). This especially includes anything that is not specified in the OpenAPI schema.

  • Redis 5 now available on Red Hat Enterprise Linux 7

    Red Hat Software Collections supply the latest, stable versions of development tools for Red Hat Enterprise Linux via two release trains per year. As part of the latest Software Collections 3.3 release, we are pleased to announce that Redis 5 is now generally available and supported on RHEL 7.

    The new Red Hat Software Collection includes Redis 5.0.3. Redis 5 is an open source in-memory data structure store, used as a database, cache and/or message broker. This version provides multiple enhancements and bug fixes over version 3.2 distributed with an earlier Red Hat Software Collections release. Most notably, the redis-trib cluster management tool has been implemented in the Redis command-line interface.

    The primary addition in Redis 5 is Streams—a new log-like data structure for storing multiple fields and string value with automatic sequencing. For detailed changes in Redis, see the upstream release notes for version 4.0 and version 5.0.

  • Mentoring new system administrators

    While this article is geared toward senior system administrators taking a more active role in the development of newer team members, those readers who are new might find interest in a different view of the world of working with newer systems administrators.

    As a system administrator who has been in the role for a long time, it’s easy to shake a proverbial cane at those newer team members who bother you with inane questions lacking the technical detail needed to provide a complete answer. It would be so easy to gruffly utter a few words to get them to go away, or point out the lack of specificity of the question in such a way as to make them feel so small that they won't talk to you again. I’ve been there, and—being frank—done exactly that.

    I was recently reading a discussion forum where there was an administrator who appeared inexperienced and, apparently, all on his or her own to figure things out. That caused me to think back to my first system administration job, and realize how thankful I am that when I started, I had someone senior who was willing to invest time in helping me become better. This better didn’t come in the form of drilling me with commands or syntax, but with a more Socratic method to help me develop skills that I use almost every day.

    When I first started with the group, whenever I hit an issue, I would go down to Chris’ office with my notepad and pencil and ask him about the problem (sometimes multiple times a day). After about a week of this, I came into his office, as usual, to ask about a system call or something. He didn’t look at me and put his hand up, signaling me to stop.

    After he finished whatever it was he was working on, he turned to me and said, “What research have you done about this question? Man pages? Google searches? -h output?”

    I said, “No, I just came down here to ask you.”

  • SUSE now member of iRODS, Sponsor of User Group Meeting

    This month, SUSE became a member of the iRODS (integrated Rule-Oriented Data System) consortium which is an open source data management software used by research organizations and government agencies worldwide.

    [...]

    iRODS UGM will host 25+ presentations from the user community and the core development team, including use case presentations, live demonstrations, and open discussions about requested iRODS features. They anticipate an audience of 150 participants representing dozens of academic, government, and commercial institutions.

Renaming openSUSE

Filed under
SUSE

At the 2019 openSUSE Conference, the openSUSE board discussed governance options at length. There will evidently be an official statement on its conclusions in the near future, but that has not been posted as of this writing. It would appear, though, that the board chose a foundation structure over the other options. A German registered association (e. V.) would have been easier to set up than a foundation, but an association has weaker restrictions so it could potentially shift its focus away from the openSUSE mission. Joining another umbrella group seemingly lacked appeal from the beginning, as did the option of doing nothing and leaving things as they are now.

The stated purpose of the foundation is to make it easier for openSUSE to accept donations and manage its own finances — things that are hard for the project to do now. The foundation structure, in particular, allows the project to enshrine its core objectives (such as support for free software) into the DNA of the organization, making it hard to divert the foundation toward some other goal. A foundation also allows openSUSE to retain its current governing board and membership structure.

In the absence of an official statement from the board, details on the decision and the reasoning behind it can be had by watching this YouTube video of a question-and-answer session with the board at the openSUSE Conference.

One motivation for the change that wasn't highlighted in the board session, but which was an undercurrent in the discussions leading up to it, is a desire for more independence from SUSE in general driven by concerns about what the company might do in the future. Such worries are not entirely irrational, even though by all accounts SUSE management is fully supportive of openSUSE now. A company's attitude can change quickly even in the absence of external events like a change of ownership. If SUSE were to be sold yet again, the new owners could take a rather dimmer view of the openSUSE project.

Read more

OpenSUSE/SUSE: Leap 15.1 Update Experience, Btrfs in YaST, SUSECON and SUSE GSI Partner Forum

Filed under
SUSE
  • The openSUSE Leap 15.1 update experience

    My desktop is a HP Pavilion Power 580-146nd. This is a midsize PC with an AMD Ryzen 5 1400 CPU, an AMD Radeon RX 580 GPU, 16 GB of RAM, a 128 GB M.2 SSD and a 1 TB 7200rpm HDD.

    I used the same USB thumbstick. After selecting ‘Update’ from the boot menu, the whole screen went black. And then nothing happened. Since I have installed openSUSE many times before, I quickly realized that this must be a graphics issue. I used ‘nomodeset’ in the past to get around that issue. This causes the installer to go back to the most basic graphics settings but it also means I could finish the update.

    It used to be a lot easier to edit the boot options. However, this is now hidden. This post on Stack Exchange (2) gives a great explanation how to enable nomodeset, both as a one-time option and as a permanent option.

    For the permanent enablement of nomodeset I know an easier way: in YaST look for the module ‘Boot Loader’ and in the Kernel Parameters tab, you can edit the boot command. This was the route that I took to make nomodeset a permanent boot setting.

  • Getting further with Btrfs in YaST

    Since the YaST team rewrote the software stack for managing the storage devices, we have been adding and presenting new capabilities in that area regularly. That includes, among other features, the unpaired ability to format and partition all kind of devices and the possibility of creating and managing Bcache devices. Time has come to present another largely awaited feature that is just landing in openSUSE Tumbleweed: support for multi-device Btrfs file systems.

    As our usual readers surely know, Btrfs is a modern file system for Linux aimed at implementing advanced features that go beyond the scope and capabilities of traditional file systems. Such capabilities include subvolumes (separate internal file system roots), writable and read-only snapshots, efficient incremental backup and our today’s special: support for distributing a single file system over multiple block devices.

  • openSUSE's YaST Now Supports Multi-Device Btrfs Setups

    For those wanting to install openSUSE Tumbleweed on a system where a single Btrfs file-system spans multiple block devices, that's now easily possible with the latest YaST. This includes the abilities for just a simple file-system spanning multiple devices to data duplication to the various RAID levels natively supported by Btrfs.

  • An application a year to an application a week on AWS

    At the recent SUSECON conference in Nashville, Ryan Niksch from AWS discussed how shifting the focus from writing code to deploying applications to production has become more critical as business agility tops the list of customer requirements. He then introduces the benefits of Cloud Foundry in general, and SUSE Cloud Application Platform specifically, including the AWS service broker; its benefits are that it is a containerized distribution of Cloud Foundry that can very quickly and easily be deployed to AWS using a Quick Start template.

  • THE Forum exclusively for GSI Partners!

    This year’s SUSE GSI Partner Forum will feature all these – you won’t want to miss it!

Red Hat and SUSE Leftovers

Filed under
Red Hat
SUSE
  • Are DevOps certifications valuable? 10 pros and cons
  • Kubernetes 1.15: Enabling the Workloads

    The last mile for any enterprise IT system is the application. In order to enable those applications to function properly, an entire ecosystem of services, APIs, databases and edge servers must exist. As Carl Sagan once said, “If you wish to make an apple pie from scratch, you must first invent the universe.”

    To create that IT universe, however, we must have control over its elements. In the Kubernetes universe, the individual solar systems and planets are now Operators, and the fundamental laws of that universe have solidified to the point where civilizations can grow and take root.

    Discarding the metaphor, we can see this in the introduction of Object Count Quota Support For Custom Resources. In English, this enables administrators to count and limit the number of Kubernetes resources across the broader ecosystem in a given cluster. This means services like Knative, Istio, and even Operators like the CrunchyData PostgreSQL Operator, the MongoDB Operator or the Redis Operator can be controlled via quota using the same mechanisms that standard Kubernetes resources have enjoyed for many releases.

    That’s great for developers, who can now be limited by certain expectations. It would not benefit the cluster for a bad bit of code to create 30 new PostgreSQL clusters because someone forgot to add a “;” at the end of a line. Call them “guardrails” that protect against unbounded object growth in your etcd database.

  • Red Hat named HPE’s Partner of the Year at HPE Discover 2019

    For more than 19 years, Red Hat has collaborated with HPE to develop, deliver and support trusted solutions that can create value and fuel transformation for customers. Our work together has grown over these nearly two decades and our solutions now include Linux, containers and telecommunications technologies, to name just a few. As a testament to our collaboration, HPE has named Red Hat the Technology Partner of the Year 2019 for Hybrid Cloud Solutions.

  • Demystifying Containers – Part II: Container Runtimes

    This series of blog posts and corresponding talks aims to provide you with a pragmatic view on containers from a historic perspective. Together we will discover modern cloud architectures layer by layer, which means we will start at the Linux Kernel level and end up at writing our own secure cloud native applications.
    Simple examples paired with the historic background will guide you from the beginning with a minimal Linux environment up to crafting secure containers, which fit perfectly into todays’ and futures’ orchestration world. In the end it should be much easier to understand how features within the Linux kernel, container tools, runtimes, software defined networks and orchestration software like Kubernetes are designed and how they work under the hood.

  • Edge > Core > Cloud: Transform the Way You Want

    For more than 25 years, SUSE has been very successful in delivering enterprise-grade Linux to our customers. And as IT infrastructure has shifted and evolved, so have we. For instance, we enabled and supported the move to software-defined data centers as virtualization and containerization technologies became more prevalent and data growth demanded a new approach.

  • SUSE OpenStack Cloud Technology Preview Takes Flight

    We are pleased to announce that as of today we are making a technology preview of a containerized version of SUSE OpenStack Cloud available that will demonstrate a future direction for our product. The lifecycle management for this technology preview is based on an upstream OpenStack project called Airship, which SUSE has been using and contributing to for some time. This follows our open / open policy of upstream first and community involvement.

SUSE: SLE 12 Service Pack 5 Beta 1 and More

Filed under
SUSE
  • SUSE Linux Enterprise 12 Service Pack 5 Beta 1
  • A demo based introduction to SUSE Cloud Application Platform

    At the recent SUSECON conference in Nashville, Peter Andersson and Peter Lunderbye from SUSE demonstrated SUSE Cloud Application Platform, including pushing your first app, buildpacks: what are they and how they can be utilised, scaling and how easy the platform makes it, and how to improve resiliency and availability of your app.
    SUSE has posted all recorded talks from SUSECON on YouTube. Check them out if you want to learn more about what SUSE has to offer. We’re not just Linux anymore! I’ll be posting more SUSE Cloud Application Platform talks here over the coming days.

  • Enabling Discoveries with AI and HPC (and the Rise of Helium)

    This week I am attending the International Supercomputing conference in Frankfurt, and I am in awe of the scientists and researchers that are here and their ability to dig in and understand super complex problems in very specialized areas.  While I am humbled by the world-changing work represented at a conference like this, I am also honored to be playing a small part in their success.  With the next iteration of SUSE Linux Enterprise High Performance Computing 15 SP1, we’ve expanded and refreshed our bundle of popular HPC tools and libraries that we make available along with every subscription to our SLE HPC operating system.

New node.js LTS, GNU Debugger, libvirt Updates Arrive in Tumbleweed Snapshots

Filed under
SUSE

One of those key packages was an update of the GNU Debugger, gdb 8.3, which was released in the 20190607 snapshot. The debugger enabled ada tests on ppc64le and riscv64; multitarget builds for riscv64 were also enabled. The snapshot also added unit test for Logical Volume Manager (LVM) over Modular Disk (MD) with the update of libstorage-ng 4.1.127. Several patches and bug fixes were applied with the update of libvirt 5.4.0, which also made an improvement to avoided unnecessary static linking that results in both the disk and memory footprint being reduced. Libvirt also introduced support for the md-clear CPUID bit. The python-libvirt-python 5.4.0 package added all new Application Programming Interfaces (APIs) and constants in libvirt 5.4.0. Text editor vim 8.1.1467 had multiple fixes, but the Tumbleweed snapshot introduced some new bugs and is currently trending at an 86 rating, according to the snapshot reviewer.

The two previous snapshots recorded an exceptional stable rating of 98 according to the snapshot reviewer.

Snapshot 20190606 updated just two packages. The nodejs10 package put out a new upstream Long-Term-Support (LTS) version with nodejs10 10.16.0, which upgraded upgrade openssl sources to 1.1.1b and libuv to 1.28.0. The other package update in the snapshot was xfdesktop 4.12.5; the package for the Xfce 4 Desktop Environment fixed icon sizes in settings, reset the desktop icon order and fixed a timer leak.

Read more

Red Hat and SUSE: Openshift, RHEL and Cloudwashing

Filed under
Red Hat
SUSE
  • Using Kubernetes Operators to Manage Let’s Encrypt SSL/TLS Certificates for Red Hat OpenShift Dedicated
  • No Downtime Upgrade for Red Hat Data Grid on Openshift

    In a blog post I wrote on the Red Hat Developer’s Blog, I wrote about multiple layers of security available while deploying Red Hat Data Grid on Red Hat Openshift. Another challenging problem I see for customer is performing a no downtime upgrade for Red Hat Data Grid images (published on Red Hat Container Catalog). That’s what we’re going to tackle in this post.

    If you’re new to it, Red Hat Data Grid is an in-memory, distributed, NoSQL datastore solution. With it, your applications can access, process, and analyze data at in-memory speed designed to deliver a superior user experience compared to traditional data stores like relational databases. In-memory Data Grids have a variety of use cases in today’s environments, such as fast data access for low-latency apps, storing objects (NoSQL) in a datastore, achieving linear scalability with data distribution/partitioning, and data high-availability across geographies.

  • World domination with cgroups in RHEL 8: welcome cgroups v2!

    One of the great things about open source development is that features can be designed and implemented organically and grow and change as needed. However, a drawback is that this methodology can sometimes lead to a hot mess and uncomfortable technical debt.

    In the case of cgroups v1, as the maintainer Tejun Heo admits, "design followed implementation," "different decisions were taken for different controllers," and "sometimes too much flexibility causes a hindrance."

    In short, not all of the controllers behave in the same manner and it is also completely possible to get yourself into very strange situations if you don’t carefully engineer your group hierarchy. Therefore, cgroups v2 was developed to simplify and standardize some of this.

    Let’s take a look at how the two versions are different. I’m going to show two different diagrams - controllers are in yellow blocks and cgroup directories have a grey background.

  • Cloud Strategies in Frankfurt
  • Are We Ready to Ditch the Data Center? [Ed: Perpetuating the myth that when you outsource all business functions to the Pentagon through its partners the servers just vanish and cease to exist]

    Over the past few decades, organizations have come to rely on their own data centers to run business applications, network their users together and for data storage. Initially, these data centers were largely hardware-centric.In the early days, a mainframe and terminals were the order of the day, before we moved onto the RISC/UNIX era, followed more recently by the server sprawl period of commodity X86 servers.
    But now, the whole concept of an organization-owned data center is going through a radical change. It started with virtualization, which separated the direct relationship between application software and the underlying hardware infrastructure. This helped improve server utilization, efficiency, and provisioning speed. The next step towards an even greater level of abstraction is the move to a software-defined infrastructure (SDI), including compute, storage and networking.

Review: openSUSE Leap 15.1

Filed under
Reviews
SUSE

openSUSE is one of those distros I have always been interested in but which I had never used for more than a few hours. Recently the project released Leap 15.1, which was a good enough reason to give the distro a proper spin.

The distro hardly needs an introduction. It is a community project sponsored by SUSE, one of the larger commercial Linux vendors. openSUSE maintains two distros: Tumbleweed is a rolling release distro and upstream to SUSE Linux Enterprise (SLE). Leap is a stable (non-rolling) distro that is downstream to SLE. A new version of Leap is released roughly once a year, and each version is supported for 18 months. The Leap 15.x series as a whole is supported for three years.

openSUSE is probably best known for the Btrfs file system, Snapper and YaST. As Leap 15.1 is a relatively small, conservative upgrade from 15.0 I will mainly focus on these features. I will also have a look at where things may be heading.

Read more

Syndicate content

More in Tux Machines

AMD Releases Firmware Update To Address SEV Vulnerability

A new security vulnerability has been made public over AMD's Secure Encrypted Virtualization (SEV) having insecure cryptographic implementations. Fortunately, this AMD SEV issue is addressed by a firmware update. CVE-2019-9836 has been made pulic as the AMD Secure Processor / Secure Encrypted Virtualization having an insecure cryptographic implementation. Read more

today's howtos and programming bits

  • How to get the latest Wine on Linux Mint 19
  • How to Install KDE Plasma in Arch Linux (Guide)
  • 0 bytes left

    Around 2003–2004, a friend and I wrote a softsynth that was used in a 64 kB intro. Now, 14 years later, cTrix and Pselodux picked it up and made a really cool 32 kB tune with it! Who would have thought.

  • A month full of learning with Gnome-GSoC

    In this month I was able to work with Libgit2-glib where Albfan mentored me on how to port functions from Libgit2 to Libgit2-glib. Libgit2-glib now has functionality to compare two-buffers. This feature I think can now benefit other projects also which requires diff from buffers, for example Builder for it’s diff-view and gedit.

  • Google Developers Are Looking At Creating A New libc For LLVM

    As part of Google's consolidating their different toolchains around LLVM, they are exploring the possibility of writing a new C library "libc" implementation.  Google is looking to develop a new C standard library within LLVM that will better suit their use-cases and likely others within the community too. 

  • How We Made Conda Faster in 4.7

    We’ve witnessed a lot of community grumbling about Conda’s speed, and we’ve experienced it ourselves. Thanks to a contract from NASA via the SBIR program, we’ve been able to dedicate a lot of time recently to optimizing Conda.  We’d like to take this opportunity to discuss what we did, and what we think is left to do.

  • TensorFlow CPU optimizations in Anaconda

    By Stan Seibert, Anaconda, Inc. & Nathan Greeneltch, Intel Corporation TensorFlow is one of the most commonly used frameworks for large-scale machine learning, especially deep learning (we’ll call it “DL” for short). This popular framework has been increasingly used to solve a variety of complex research, business and social problems. Since 2016, Intel and Google have worked together to optimize TensorFlow for DL training and inference speed performance on CPUs. The Anaconda Distribution has included this CPU-optimized TensorFlow as the default for the past several TensorFlow releases. Performance optimizations for CPUs are provided by both software-layer graph optimizations and hardware-specific code paths. In particular, the software-layer graph optimizations use the Intel Math Kernel Library for Deep Neural Networks (Intel MKL-DNN), an open source performance library for DL applications on Intel architecture. Hardware specific code paths are further accelerated with advanced x86 processor instruction set, specifically, Intel Advanced Vector Extensions 512 (Intel AVX-512) and new instructions found in the Intel Deep Learning Boost (Intel DL Boost) feature on 2nd generation Intel Xeon Scalable processors. Let’s take a closer look at both optimization approaches and how to get these accelerations from Anaconda.

  • PyCoder’s Weekly: Issue #374 (June 25, 2019)

VIdeo/Audio: Linux in the Ham Shack, How to install OpenMandriva Lx 4.0 and "Debian Package of the Day"

  • LHS Episode #290: Where the Wild Things Are

    Welcome to Episode 290 of Linux in the Ham Shack. In this short format show, the hosts discuss the recent ARRL Field Day, LIDs getting theirs, vandalism in Oregon, a Canonical flip-flop, satellite reception with SDR and much more. Thank you for tuning in and we hope you have a wonderful week.

  • How to install OpenMandriva Lx 4.0

    In this video, I am going to show how to Install OpenMandriva Lx 4.0.

  • Jonathan Carter: PeerTube and LBRY

    I have many problems with YouTube, who doesn’t these days, right? I’m not going to go into all the nitty gritty of it in this post, but here’s a video from a LBRY advocate that does a good job of summarizing some of the issues by using clips from YouTube creators: I have a channel on YouTube for which I have lots of plans for. I started making videos last year and created 59 episodes for Debian Package of the Day. I’m proud that I got so far because I tend to lose interest in things after I figure out how it works or how to do it. I suppose some people have assumed that my video channel is dead because I haven’t uploaded recently, but I’ve just been really busy and in recent weeks, also a bit tired as a result. Things should pick up again soon.

Games: Steam Summer Sale, Last Moon, Ubuntu-Valve-Canonical Faceoff

  • Steam Summer Sale 2019 is live, here’s what to look out for Linux fans

    Another year, another massive sale is now live on Steam. Let’s take a look at what Valve are doing this year and what you should be looking out for. This time around, Valve aren’t doing any special trading cards. They’re trying something a little different! You will be entering the "Steam Grand Prix" by joining a team (go team Hare!), earning points for rewards and having a shot at winning some free games in the process. Sounds like a good bit of fun, the specific-game challenges are a nice touch.

  • Last Moon, a 2D action-RPG with a gorgeous vibrant style will be coming to Linux next year

    Sköll Studio managed to capture my attention recently, with some early footage of their action-RPG 'Last Moon' popping up in my feed and it looks gorgeous. Taking inspiration from classics like Legend of Zelda: A link to the past, Secret of Mana, Chrono Trigger and a ton more you can see it quite clearly. Last Moon takes in place in a once peaceful kingdom, where an ancient and powerful mage put a curse on the moon, as Lunar Knight you need to stop all this insanity and bring back peace.

  • Ubuntu Takes A U-Turn with 32-Bit Support

    Canonical will continue to support legacy applications and libraries. Canonical, the maker of the world’s most popular Linux-based distribution Ubuntu, has revived support for 32-bit libraries after feedback from WINE, Ubuntu Studio and Steam communities. Last week Canonical announced that its engineering teams decided that Ubuntu should not continue to carry i386 forward as an architecture. “Consequently, i386 will not be included as an architecture for the 19.10 release, and we will shortly begin the process of disabling it for the eoan series across Ubuntu infrastructure,” wrote Will Cooke, Director of Ubuntu Desktop at Canonical.

  • Steam and Ubuntu clash over 32-bit libs

    It has been a tumultuous week for gaming on Linux. Last Tuesday afternoon, Canonical's Steve Langasek announced that 32-bit libs would be frozen (kept as-is, with no new builds or updates) as of this October's interim 19.10 release, codenamed "Eoan Ermine." Langasek was pretty clear that this did not mean abandoning support for running 32-bit applications, however.

  • Linux gamers take note: Steam won’t support the next version of Ubuntu

    Valve has announced that from the next version of Ubuntu (19.10), it will no longer support Steam on Ubuntu, the most popular flavor of Linux, due to the distro dropping support for 32-bit packages, This all kicked off when Canonical, developer of Ubuntu, announced that it was seemingly completely dropping support for 32-bit in Ubuntu 19.10. However, following a major outcry, a further clarification (or indeed, change of heart) came from the firm stating that there will actually be limited support for 32-bit going forward (although updates for 32-bit libraries will no longer be delivered, effectively leaving them in a frozen state).

  • Valve killing Steam Support for some Ubuntu users

    A few years ago the announcement that Steam would begin supporting Linux was a big deal: it meant that anyone who preferred to rock an open-source operating system over Mac OS or Windows 10 would have instant buy-it-and-play-it access to a large catalog of game titles that would have otherwise taken a whole lot of tweaking to get up and running or wouldn't have worked for them at all. For some, at least, the party may be coming to an end.

  • Steam is dropping support for Ubuntu, but not Linux entirely

    The availability of Steam on Linux has been a boom for gaming on the platform, especially with the recent addition of the Steam Play compatibility layer for running Windows-only games. Valve has always recommended that gamers run Ubuntu Linux, the most popular desktop Linux distribution, but that's now changing.

  • Canonical (sort of) backtracks: Ubuntu will continue to support (some) 32-bit software

    A few days after announcing it would effectively drop support for 32-bit software in future versions of the Ubuntu operating system, Canonical has decided to “change our plan and build selected 32-bit i386 packages.” The company’s original decision sparked some backlash when it became clear that some existing apps and games would no longer run on Ubuntu 19.10 if the change were to proceed as planned. Valve, for example, announced it would continue to support older versions of Ubuntu, allowing users to continue running its popular Steam game client. But moving forward, the company said it would be focusing its Steam for Linux efforts on a different GNU/Linux distribution.

  • Just kidding? Ubuntu 32-bit moving forward, no word yet from Valve

    Due in part to the feedback given to the group over the weekend and because of their connections with Valve, Canonical did an about-face today. They’ve suggested that feedback from gamers, Ubuntu Studio, and the WINE community led them to change their plan and will “build selected 32-bit i386 packages for Ubuntu 19.10 and 20.04 LTS. Whether this will change Valve’s future with Ubuntu Steam, we’ll see.

  • Canonical backtracks on 32-bit Ubuntu cull, but warns that on your head be it

    CANONICAL HAS CONFIRMED a U-Turn on the controversial decision to drop 32-bit support for Ubuntu users later this year. The company has faced criticism from users who aren't happy with the plan to make Ubuntu purely 64-bit, which culminated at the weekend with Steam announcing it would pull support for Ubuntu. Many Steam games were never made in 64-bit and it would, therefore, devalue the offer. However, Canonical confirmed on Monday that following feedback from the community, it was clear that there is still a demand, and indeed a need for 32-bit binaries, and as such, it will provide "selected" builds for both Ubuntu 19.10 and the forthcoming Ubuntu 20.04. Canonical's announcement spoke of the highly passionate arguments from those who are in favour of maintaining both versions, thus forcing the team to take notice. However, it has made it clear that it's doing so under the weight of expectation, not because it agrees. "There is a real risk to anybody who is running a body of software that gets little testing. The facts are that most 32-bit x86 packages are hardly used at all," the firm said.