Language Selection

English French German Italian Portuguese Spanish

SUSE

Fedora, Red Hat and SUSE

Filed under
Red Hat
SUSE
  • Fedora IoT becomes an edition

    The Fedora 33 release is currently scheduled for late October; as part of the process of designing this release, the deadline for system-wide change proposals was set for June 30. This release already has a substantial number of big changes in the works, so one might be forgiven for being surprised by a system-wide change proposal that appeared on August 4, which looks to be pre-approved. Not only that, but this proposal expands the small set of official Fedora "editions" by adding the relatively obscure Fedora Internet of Things Edition.

    The Fedora distribution is released in a number of forms, including a fair number of "Fedora spins" that skew the distribution toward a specific use case. The flagship Fedora products, though, are the editions, of which there are currently only two: Fedora Workstation and Fedora Server. The former is obviously aimed at desktop deployments, while the latter is meant to be useful on back-end systems. This set of editions has been stable for some time.

    There are a few "emerging editions" in the works, including Fedora CoreOS and Silverblue. Also on that list is Fedora IoT which is now poised to become the third edition to be part of the Fedora 33 release. The proposal notes that this is "largely a paperwork exercise at this point". While the remaining work may be confined to paperwork, the project may want to put some effort into documentation sooner or later; actual information about what Fedora IoT is and how to work with it is relatively hard to find.

    [...]

    One other significant difference with Fedora IoT is a relatively strong focus on the use of containers to install applications. The podman tool is provided for this purpose; it's meant to look a lot like Docker, but without the need for any background daemons. Podman comes configured to pull images from docker.io by default. Your editor attempted to use it to install a few versions of NetHack that must all surely be legitimate, but none of them consented to run correctly — thus saving your editor a considerable amount of wasted time.

    Beyond those changes, though, Fedora IoT feels much like any other Fedora system. The commands work in the same way, and the usual packages are available. This makes for a relatively rich and comfortable environment for embedded-systems work.

    One can't help wonder about the ultimate objective, though. Fedora comes with no support guarantees, a fact that is sure to give pause to any companies thinking about which operating system to install in their million-device products. If Fedora is to have any chance of being deployed in such systems, some sort of commercial support option will have to materialize. When that happens, it may well go under the name of "Red Hat IoT" or some such. Fedora itself may not make it onto all of those devices, but Fedora users will have played with the technology first and helped to make it better.

  • Open source: the pathway to innovation

    Open source technology has seen widespread adoption over the past ten to fifteen years as organisations cross-industry have caught on to its undeniable benefits.

    As the largest open source company in the world, at Red Hat, we believe in the power of open source and its ability, from both a software and cultural perspective, to push the boundaries of technological capabilities. Here’s why.

    [...]

    Open source software is by definition ‘open’, offering companies full visibility and transparency of the code – this means bugs and defects can be identified much more quickly than in proprietary software, leading to enhanced security. As Linus Torvalds, the founder of the open source operating system Linux, once said: “given enough eyeballs, all bugs are shallow”.

    Secondly, it doesn’t include many of the costs associated with proprietary software, such as licensing fees – this is a big perk for businesses, allowing them to significantly reduce operating costs. Then there is the added cost of wanting to switch to a different software provider down the line; using open source software helps to avoid the pitfall of getting locked into using an expensive proprietary vendor.

    Open source also enables companies to better customise their software. Unlike proprietary software that is developed within the four walls of the company and based on limited input, open source software is typically better tailored to the customers’ needs, as the users themselves can add their preferred features while the technology is in development.

    [...]

    Female contributors are definitely becoming more widely recognised. And even though there is still more work to be done, throughout my career I’ve encountered more women in the context of open source than in proprietary software, and I’ve witnessed more inclusive meritocracy within open source companies. Besides the fact that open thinking is an essential part of supplementing the open source, open communities, by their design, make it much easier for individuals from all backgrounds to participate, have a voice, and share their experience and skills.

    It’s been proven time and again that the more diversity you can bring to a project, the better the outcome is, as you’re benefitting from a greater variety of perspectives, ideas and experience. For this reason, I’d argue that open source is both the fastest and most inclusive way to innovate.

  • Collaboration integral to operations, Red Hat CFO says

    When the pandemic hit, CFO Laurie Krebs, with other function leaders at open-source operating system company Red Hat, created a war room to respond to customers' deferral requests and other payment concessions.

    "Our premier product is an operating system, so, [for that to] go dark is not an option for a lot of customers," Krebs said.

    Rather than create a single playbook, the team approached each request on a case-by-case basis. "To some people, cash is important," she said. "To other people, holding onto their subscription is important."

    The war room's collaborative approach, in which representatives from sales, sales operations, technical accounting and business finance weighed requests as a team, defines how the company approaches all of its policymaking, said Krebs, who took over as CFO last year after serving as vice president of global tax.

  • Want to make better decisions? Encourage disagreement

    Dissent is incredibly important to successful open decision making. When you're seeking collaboration on an important decision, you don't want to be surrounded by people who always agree with everything you say. You already know everything that you're saying and what you believe to be the best path forward. However, you also know (or should know) that your knowledge, experience, and visibility of the entire picture is limited. What you really need are perspectives from people with knowledge, experience, and visibility complementary to yours. That helps round out your perspective—people who will bring up something that you didn't think of or didn't fully comprehend its importance.

    In this article, I'll explore in more depth the importance of dissension during decision making. I'll present a compilation of ideas from a number of my colleagues (at Red Hat), which arose in an open forum discussion we had on the subject.

    [...]

    When presenting an idea and asking for opinions in a meeting, plenty more great ideas and perspectives may be left unsaid. How can we unleash the power that this potential represents?

    [...]

    Using this method can empower your group to fully explore various ways to achieve their objectives. It should present decision makers with all available perspectives and enable them to make the decision that is best for the group.

    Best of all, since they've been included in a decision making process, the entire group will feel ownership over the decision and passionately work to implement and execute it.

  • Here’s What’s .NEXT for Nutanix and SUSE

    Let’s start by stating the obvious. At SUSE, we’re passionate about advancing open source technology to provide better customer outcomes. While that ethos is at the core of SUSE’s business, the truth is that many of our partners embrace that same passion, and work with SUSE to deliver better experiences for their own customers and end users.

  • Adapting for Hybrid Cloud – Part 3 of 3: The Results

    Most enterprises today are pursuing a hybrid strategy, mixing and matching public and on-prem venues depending on each workload’s requirements. One of the issues facing enterprises with hybrid today is the difference in pricing and procurement models. For public cloud, on-demand operating expense pricing is pretty mainstream, and this on-demand access to huge capacity is one of the key drivers behind public cloud adoption, driving more rapid instantiation of resources, allowing the scaling of applications to suit changing demands, making innovation easier and simplifying entry into new markets.

  • SLES for SAP Applications 15 SP2: What’s New and What’s Next

Tumbleweed Rises from Rebuilt Packages

Filed under
SUSE

With “literally all 15,000” packages being rebuilt in snapshot 20200826, openSUSE Tumbleweed roared back from a stability rating of 36 in the rebuild snapshot to a 95 rating in snapshot 20200901, according to the snapshot reviewer.

Each snapshot progressively increased in stability this week.

Snapshot 20200901 brought ImageMagick 7.0.10.28, which provided a patch for correct colospace and fixed paths for conversion of Photoshop EPS files. VirtualBox 6.1.13 arrived in the snapshot and updated the sources to run with versions above the 5.8 Linux Kernel with no modifications needed to the kernel. The library for rendering Postscript documents, libspectre 0.2.9, now requires Ghostscript 9.24 and fixed memory leaks and crashes to the program caused by malformed documents. One major version update to the game freecell-solver was made in the snapshot; version 6.0.1 had some code cleanup, minor bug fixes and the addition of a compile time option. openSUSE’s snapper package updated to 0.8.13 and fixed the Logical Volume Manager setup for volume groups and logical volumes with one character-long names. Other notable packages updated in the snapshot were xapian-core 1.4.17, openldap2 2.4.52 and qalculate 3.12.1.

Trending at a 87 rating, snapshot 20200831, brought less than a handful of updates. The packages updated in the snapshot were bind 9.16.6, libverto 0.3.1, permissions 1550_20200826, and suse-module-tools 15.3.4. The bind package, which implements the Domain Name System (DNS) protocols for the Internet, fixed several Common Vulnerabilities and Exposure including one that made it possible to trigger an assertion failure by sending a specially crafted large TCP DNS message.

Read more

Between Ubuntu 20.04 and openSUSE Leap 15.2 Releases

Filed under
SUSE
Ubuntu

This year 2020 is amazing as two big European computer operating systems come out. They are Ubuntu and openSUSE more precisely version Focal Fossa and Leap 15.2. They are ranked number 4th and 13th on Distrowatch.com.This article sums up these two for everyone to quickly download or purchase a computer with them.

The leading operating system for PCs, IoT devices, servers and the cloud.

The makers' choice for sysadmins, developers and desktop users.

Read more

GeckoLinux releases Pantheon and Budgie editions

Filed under
OS
Linux
News
Software
SUSE

The GeckoLinux project is pleased to announce the addition of the Pantheon and Budgie desktop environments to its lineup. Both desktop environments are offered with the choice of an openSUSE Leap 15.2 or openSUSE Tumbleweed base system, plus multimedia support from the Packman repository.

Read more

SUSE/OpenSUSE: Ritchie-CLI, Extensible Linux System Calls and 'Cloud' Hype

Filed under
SUSE

  • Ritchie-CLI for openSUSE

    Ritchie is an open source tool developed from ZUP Company that allows you to create, store and share automations securely. It also optimizes repetitive commands so you have more programming autonomy. As a member of the openSUSE community, I make the packages available to all openSUSE users.

    How does Ritchie work?

    In a general context, the common process for executing a project is to create a whole previous infrastructure, defining a language in the system that will be programmed, downloading dependencies and defining the rules that should be used for the project.

  • Canonical + SUSE Engineers Call For More Extensible Linux System Calls Moving Forward

    Aleksa Sarai of SUSE and Christian Brauner of Canonical presented at last week's Linux Plumbers Conference with a call for more extensible system calls moving forward in aiming to enhance the Linux user-space API.

    The talk was a collection of recommendations -- some of which are already common in the introduction of new system calls -- and new recommendations compared to the traditional "trial and error" approach the kernel has seen to some extent with system calls of the past.

  • Adapting for Hybrid Cloud – Part 2 of 3: The SUSE Solution

    SUSE delivers capabilities for you to combine multiple cloud platforms, including converged container and virtual infrastructure, into a single entity; one that consolidates access to resources and is controlled in a single management environment. The outcome: you gain all the benefits of cloud solutions while maintaining total control and consistency of execution.

Element | Matrix Chat Client on openSUSE

Filed under
SUSE
HowTos

All the kids have been talking about the wonders of Matrix as the future of decentralized, secure communication. I have known about it, seen bridges being used in the openSUSE discord and Telegram rooms. Most of my experience has not been great, generally there were significant delays. I have used a few clients, Riot.im on a web client, which I didn’t care for and I also used Quaternion a Qt based client but I have had issues with the encrypted messages bit. I found the user experience to be rather… lack-luster at best. Mostly, I found the whole thing quite confusing. Accessing new rooms wasn’t self-evident, understanding what Matrix is and isn’t was confusing and I therefore found it frustrating to use. My experience, has been that I really preferred Telegram for communication.

Read more

Announcing the SUSE Linux for Raspberry Pi LinkedIn group

Filed under
Linux
SUSE

We have supported SUSE Linux on various models of Raspberry Pi systems since 2018. Although we have seen a variety of use cases for SUSE Linux on Raspberry Pi devices, we really did not have a good forum for people to share technical information for using SUSE Linux on the Raspberry Pi.

To address this limitation, I have created a LinkedIn group to foster sharing of technical information about using SUSE Linux on Raspberry Pi and other Single Board Computers (SBC) based on Arm processors. This new group can be found at https://cutt.ly/rpisuse

Read more

Stasiek Michalski wins the race for the openSUSE Board

Filed under
SUSE

The openSUSE Ad-hoc Board Election is now concluded.

Stasiek Michalski has been elected to join the openSUSE Board. The complete result is as follows:

Stasiek Michalski — 160 votes
Pierre Böckmann — 70 votes
234 out of 510 eligible members have cast their vote in this election. We recorded 4 blank votes.

Read more

OpenSUSE/Tumbleweed Updates and SUSE 'Cloudwashing'

Filed under
SUSE
  • Alpha Prototype Jump is Available, Tumbleweed gets systemd, curl Updates

    The prototype project openSUSE Jump is now available for Alpha phase testing. Jump is an interim name given to the experimental distribution in the Open Build Service as developers have been trying to synchronize SUSE Linux Enterprise binaries for openSUSE Leap. The efforts are trying to bring the codes of Leap and SLE closer together, which was previously mentioned in an article titled New Prototype Builds Bringing Leap, SLE Closer Will be Available Soon.

    The past week produced three openSUSE Tumbleweed snapshots.

    The snapshots brought some interesting packages including one used by NASA and one package fixed a ancient bug. A full rebuild of Tumbleweed was done with Build20200825, but the build doesn’t appear good enough to be released in a snapshot.

  • openSUSE Tumbleweed – Review of the week 2020/35

    This week we have published a few snapshots less than normal. To ‘compensate’, the next one will be huge to download though. On August 25, I merged the change for libexecdir == /usr/libexec and since then I’m fighting to QA after effects to get you a snapshot out that won’t break in all corners. There will likely be some rough patches here and there though.

  • Live Patching And SUSE Lifecycle Manager On SLES For SAP On-Demand In The Public Cloud
  • Adapting for Hybrid Cloud – Part 1 of 3: The Market

SUSE: Kubernetes 1.19.0 and SUSE Digital Partner Summit

Filed under
SUSE

  • What’s new in Kubernetes 1.19

    Thanks to Sascha Grunert for the technical content of this post. In addition to being a member of the Containers Squad of the SUSE CaaS Platform team, Sascha is Technical Lead in the Kubernetes Release Engineering Subproject, which is part of SIG Release. He participated in many Kubernetes release cycles from different roles and is thrilled to give you an update about the next version.
    SUSE congratulates the Kubernetes Project on another evolution of the most popular container orchestration and management platform, which forms the basis of our SUSE CaaS Platform. You can expect to see Kubernetes 1.19 supported in a future SUSE release.

    [...]

    Two Common Vulnerabilities and Exposures (CVE) will be fixed in Kubernetes v1.19.0.
    The first one is CVE-2020-8559, which allows a privilege escalation from a node inside the cluster. This means if it is possible to intercept certain requests to the Kubelet, then an attacker could send a redirect response that may be followed by a client request using the credentials from the original request. This can lead to compromise of other nodes inside the cluster.

    The other fixed vulnerability is CVE-2020-8557. This CVE allows a Denial of Service (DoS) via a mounted /etc/hosts file inside a container. If a container writes a huge set of data to the /etc/hosts file, then it could fill the storage space of the node and cause the node to fail. Root cause for this issue was that the kubelet does not evict this part of the ephemeral storage.

  •        

  • SUSE plots edgier Kubernetes with Linux behind the wheel

    SUSE has had a busy year, with a switch of CEO, the ditching of OpenStack, and the buy of Kubernetes darling Rancher Labs.

    The Register spoke to the veteran Linux flinger's president of Engineering and Innovation, Thomas Di Giacomo, and CTO and openSUSE chair Gerald Pfeifer, about cars, Kubernetes, open source and life free from the clutches of its previous owner.

    Last month's Rancher Labs slurp highlighted the freedom SUSE now enjoys after it was jettisoned from Micro Focus in 2018.

  • The Dog days of Summer means we are that much closer to SUSE Digital Partner Summit

    Two weeks – we’ll be firmly in September with kids in some form of school AND the SUSE Digital Partner Summit beginning its first day (hint: register!). As mentioned in an earlier post day, 1 features a keynote from Melissa Di Donato and Paul Devlin and the announcement of the SUSE One Partner Program and why the program is evolving to the specializations of INNOVATE, BUILD, SELL, MANAGE, SERVICE and TRAIN to be covered by Rachel Cassidy. Rachel will be joined by Julie Baldwin as they discuss how one of our partners have found ways to stay relevant in a cloud-first world.

Syndicate content

More in Tux Machines

Septor 2020.5

Tor Browser is fully installed (10.0.2) System upgrade from Debian Buster repos as of October 21, 2020 Update Linux Kernel to 5.9.0-1 Update Thunderbird to 78.3.1-2 Update Tor to 0.4.4.5 Update Youtube-dl to 2020.09.20 Read more

Incremental backup with Butterfly Backup

This article explains how to make incremental or differential backups, with a catalog available to restore (or export) at the point you want, with Butterfly Backup. Read more

Regressions in GNU/Linux Evolution

  • When "progress" is backwards

    Lately I see many developments in the linux FOSS world that sell themselves as progress, but are actually hugely annoying and counter-productive. Counter-productive to a point where they actually cause major regressions, costs, and as in the case of GTK+3 ruin user experience and the possibility that we'll ever enjoy "The year of the Linux desktop". [...] We live in an era where in the FOSS world one constantly has to relearn things, switch to new, supposedly "better", but more bloated solutions, and is generally left with the impression that someone is pulling the rug from below one's feet. Many of the key changes in this area have been rammed through by a small set of decision makers, often closely related to Red Hat/Gnome/freedesktop.org. We're buying this "progress" at a high cost, and one can't avoid asking oneself whether there's more to the story than meets the eye. Never forget, Red Hat and Microsoft (TM) are partners and might even have the same shareholders.

  • When "progress" is backwards

Graphics: Vulkan, Intel and AMD

  • NVIDIA Ships Vulkan Driver Beta With Fragment Shading Rate Control - Phoronix

    This week's Vulkan 1.2.158 spec release brought the fragment shading rate extension to control the rate at which fragments are shaded on a per-draw, per-primitive, or per-region basis. This can be useful similar to OpenGL and Direct3D support for helping to allow different, less important areas of the screen be shaded less than areas requiring greater detail/focus. NVIDIA on Tuesday released the 455.26.02 Linux driver (and 457.00 version for Windows) that adds this fragment shading rate extension.

  • Intel Begins Adding Alder Lake Graphics Support To Their Linux Driver - Phoronix

    Intel has begun adding support for Alderlake-S to their open-source Linux kernel graphics driver. An initial set of 18 patches amounting to just around 300 lines of new kernel code was sent out today for beginning the hardware enablement work on Alderlake-S from the graphics side. Yes, it's only a few hundred lines of new driver code due to Alder Lake leveraging the existing Gen12/Tigerlake support. The Alder Lake driver patches similarly re-use some of the same workarounds and changes as set for the 14nm Rocket Lake processors with Gen12 graphics coming out in Q1.

  • AMD Linux Driver Preparing For A Navi "Blockchain" Graphics Card - Phoronix

    While all eyes are on the AMD Radeon RX 6000 "Big Navi" graphics cards set to be announced next week, it also looks like AMD is preparing for a Navi 1x "Blockchain" graphics card offering given the latest work in their open-source Linux driver. Patches posted today provide support for a new Navi graphics card referred to as the "navi10 blockchain SKU." The Navi 10 part has a device ID of 0x731E. From the AMDGPU Linux kernel driver perspective, the only difference from the existing Navi 10 GPU support is these patches disable the Display Core Next (DCN) and Video Core Next (VCN) support with this new SKU not having any display support.