Home Blog Page 291

Linux Hacker Board Trends in 2018 and Beyond

When I read Brian Benchoff’s recent claim in Hackaday that the maker board market was stalling, I had a sense that there might be some truth to it. The novelty of community-backed, open-spec SBCs has worn off, and there were few new boards in 2018 that seem destined to become Raspberry Pi killers. Yet, the more I researched open-spec Linux/Android maker SBCs for LinuxGizmos’ New Year’s edition SBC catalog, the more I realized that the sector was very much alive — just a bit quieter than before.

There were 19 new SBC entries since our June roundup of 116 SBCs (compared to 13 new products that appeared in that reader survey catalog since the January 2018 New Year’s hacker catalog roundup of 103 boards). Despite the removal from market of several older products in Q2 2018 and the dissolution of The Next Thing and its Chip board — and even after we eliminated several older boards with fading communities, such as the 86Duino and PCDuino8 — we ended up with 122 boards, six more than in June.

Benchoff’s speculation that fewer maker boards were sold in 2018 may well be correct, but I have seen no proof of it. If there has been a slowdown, Benchoff nailed the reason: poor documentation. Other drawbacks to the hacker board scene include buggy software and less frequently, hardware. In many cases, the documentation and images are fine, but by the time they arrive, your shiny new SBC is already halfway to obsolescence.

Many of the casual, Raspberry Pi home automation hobbyists who experimented with faster, but not always reliable Banana, Orange, and NanoPi’s and other more obscure bargain-basement SBCs in recent years have returned to the fold. And why not return to the very capable Raspberry Pi 3 Model B+ — the SBC of the year and the winner of our June reader survey — or the smaller new RPi 3 Model A+? The RPi 3B+ is only a modest improvement over the 3B, but it is close enough to the competition in price, features, and performance to shift the comparison to software and support issues. If the Raspberry Pi Foundation had been faster to transition from ARM11 to Cortex-A SoCs, the hacker board market might be considerably smaller than it is today.

Despite the atypically buggy PoE board for the RPi 3B+, which was quickly resolved with a refund and a reboot, things tend to work more smoothly in Raspberry land. Most buyers are more interested in solid community support and no-doubt software and HAT compatibility than they are in having full schematics.

Yet, there’s a second trend that is leading us toward more diversity: The maker board movement continues to merge with the commercial SBC industry. There appears to be significant growth in small manufacturing customers using open-spec boards with a variety of special features ranging from AI to voice control to Time Sensitive Networking. These technically knowledgeable buyers need solid documentation and schematics for prototyping new products but are usually less interested in other community resources. More to the point, they are tired of the high prices charged by commercial vendors, which only make sense with huge volumes.

New maker SBCs and trends in late 2018

Many of the new boards we’ve seen since June are aimed at relatively niche applications rather than trying to beat the Pi at world domination. There are new router boards such as the Banana Pi BPI-R2, as well as an increasing number of extended temperature SBCs such as the Firefly-PX3-SE. We’ve seen industrial focused newcomers such as the HummingBoard CBi (CAN bus interface) and novel sandwich-style module/carrier board combos like the Khadas Edge. Seeed has introduced a ReSpeaker v2.0 model aimed at far-field voice control applications.

The trend toward Power-over-Ethernet (PoE) continues with products like the Renegade Elite. (The RPi 3B+ may now have a PoE option, but it’s hobbled by a Gigabit Ethernet port that is limited to 300Mbps.)

We’re seeing more SBCs with built-in cellular modems or mini-PCIe and M.2 slots capable of supporting them. FriendlyElec has jumped on this trend this year with 2G, 3G, and 4G themed NanoPi IOT models.

The still fledgling x86 hacker board arena continues to grow with the Intel Gemini Lake based Odroid-H2 board, which appears to be the most powerful hacker SBC in history. The Odroid-H2 is the first hacker board to feature an Atom processor from a recently released Atom/Celeron product family.

Another new Intel-based board — Aaeon’s Apollo Lake based Up Core Plus — is one of several new entries since June designed for machine learning and neural network processing. These AI contenders include the Allwinner V5 based Lindenis V5 and Bitmain Sophon BM1880, which uses a novel TPU-enhanced Arm SoC of Bitmain’s own design. Khadas is selling a version of the Khadas Edge with the AI-enhanced Rockchip RK3399Pro SoC.

Among more mainstream boards, we saw a continuing shift from Allwinner SoCs to the high-end, hexa-core Rockchip RK3399. In early 2018 we saw a lot of RK3399 entries in the $110 to $150 range, but newer models are more affordable.

The new Khadas Edge, Renegade Elite, and 96Boards form-factor Rock960 all start at about $100, and others have been cheaper. FriendlyElec introduced a $65 (2GB) and up NanoPi-M4 and followed up with a compact, $45 NanoPi Neo4. The Neo4 is an impressive feat despite the limitation of only 1GB of RAM, which isn’t enough for the RK3399. Also in this range is Pine64’s $60 (2GB) and up RockPro64, which shipped earlier this year.

No single Raspberry Pi killer emerged in 2018. Yet, the collective group of RK3399 vendors appear to be acting as a counterpoint in the Pi. The RK3399 is fast and offers x86 like technologies such as PCIe, SATA, and HDMI 2.0, and it has better Linux mainline support than the still-improving Allwinner SoCs.

2019 SBC trends

So what can we expect in 2019’s board market? The Raspberry Pi Foundation has already said that it is done with the Raspberry Pi 3 line and that it will upgrade from the current 40nm process for the next model. In March 2017, a year after the launch of the original Raspberry Pi 3, Raspberry Pi Trading CEO Eben Upton told ITPro that the RPi 3 successor would be at least three years away, pegging it at March 2019 at the earliest. It would not be surprising if the Raspberry Pi 4 didn’t arrive until late 2019, or even 2020. If there’s a major recession, we will likely see fewer SBC introductions. Otherwise, however, the growth in niche applications will probably block consolidation for the time being.

With TI’s new quad-core Cortex-A53 Sitara AM65x, it might be time for a BeagleBone reboot, and we should see more NXP i.MX8M boards such as TechNexion’s new sandwich-style PICO-PI-IMX8M spin on the Wand-Pi-8M. In the x86 world, meanwhile, a community-backed SBC based on the AMD Ryzen Embedded V1000 chip may arrive, although it may not clear our $200 limit.

So far, no RISC-V based SBCs have slid under our $200 limit, but one is likely to arrive in 2019. We could even see a low-cost Google Fuchsia hacker board. Meanwhile, you can check out the new Linux supported C-SKY ISA for as little as $6 with the new C-SKY board.

Overall, we’ll see a growing focus on 5G and edge analytics. In 2019 we are likely to see at least one 5G-ready board, and many more high-end edge IoT boards with NPUs, VPUs, and smartened up GPUs. So get ready to start talking TOPS and deep learning frameworks.

Sounds like fun. Let’s go.

Linux Technology for the New Year: eBPF

eBPF is “Linux’s newest superpower,” said SAP Labs’ developer Gaurav Gupta, during a talk that he gave about using the technology for low-overhead tracing at KubeCon in Copenhagen earlier this year.

A virtual machine for the Linux kernel, eBPF could set the stage for advanced, low-overhead tracing inside the kernel itself, offering insight into I/O and file system latency, CPU usage by process, stack tracing and other metrics useful for debugging. It could also play a role in system security, potentially offering a way to thwart DDOS attacks, to monitor for intrusion detection, and even replace IPtables. It also offers a cleaner alternative to installing drivers.

“In the future, you will see a lot more eBPF programs instead of kernel modules,” said Netflix Kernel and Performance Engineer Brendan Gregg, at the All Things Open conference held in Raleigh, North Carolina in October.

Read more at The New Stack

The Top 5 Linux and Open-Source Stories of 2018

Last year was among the best of times for Linux and open-source. It was also the worst of years. The top five Linux and open-source stories tell it all.

SPECTRE/MELTDOWN

First, last January there were a lot of exhausted and angry Linux kernel developers. That’s because a fundamental chip design mistake led to Linux and all Intel-based operating systems having to deal with the Spectre and Meltdown major security problems.

Linus Torvalds, Linux’s master developer, added, that with the “security issues kept under wraps, we couldn’t do our usual open methods. This made fixing the bugs much more painful than it should be.”

IBM BUYS RED HAT

I didn’t see this coming. IBM made the biggest software company acquisition of all time when it paid $34 billion for Red Hat. This deal wasn’t about Linux. It was about IBM wanting Red Hat’s cloud, container, and Kubernetes expertise.

Read more at ZDNet

Confused Deputies Strike Back

A few weeks back Kubernetes had its first really severe security issue, CVE-2018-1002105. For some background on this, and how it was discovered, I recommend Darren Shepherd’s blog post, he discovered it via some side effects and initially it did not appear to be a security issue just an error handling issue. Of course we know well that many error handling issues can be escalated, but why was this one so bad?

To summarize the problem, there is an API server proxy component, that clients can use to talk to other API endpoints. As the postmortem document says

  • Kubernetes API server proxy components still use http/1.1 upgrade-based connection tunneling, which does not distinguish between request data sent by the apiserver while establishing the backend connection, and data sent by the requesting user

  • High and low-privilege API requests to aggregated API servers are proxied via the same component with the same high-permission transport credentials

Well, this security issue is actually well known enough to have its own name, it is the confused deputy problem, originally written about by Norm Hardy in 1988 although referring to an original example from the 1970s. The essence of the problem is that there are three parties involved, a user, a proxy or deputy type component and an object or service that needs to be accessed, or a similar set of endpoints. 

Read more at CloudAtomic

2019 and the Strength of Open Source

Now that the various challenges and successes of 2018 are behind us, let’s look back at some of the year’s highlights and see what’s in store for 2019 here on Linux.com.

Wins for 2018

2018 saw amazing growth for open source generally and for The Linux Foundation specifically, with huge tech acquisitions and widespread industry adoption stemming from more than 20 years of steady open source development and innovation.

At The Linux Foundation, this growth was reflected in the formation of many new projects, such as:

It was also reflected in record-breaking events, such as the sold-out KubeCon + CloudNativeCon; in the unprecedented number of new members joining The Linux Foundation last year; and in training milestones, such as surpassing the one million mark for the number of people enrolled in Linux Foundation training and certification courses on edX.  

This interest in learning and training was seen on Linux.com as well, where tutorials were consistently the most popular articles on the website. For 2019, our goal is to feed that interest with articles that educate and inform and that provide a firm foundation from which to explore the array of tools, projects, and opportunities within the open source ecosystem. You can look forward to previews of the best Linux distributions, in-depth command-line tutorials, information on LF training courses, ebooks, and webinars, highlights from industry-leading events, and much more.  

A word for 2019

I read an essay by Melinda Gates in which she said that, rather than making a list of resolutions, she picks a word for the year and uses to that word to inform her goals and shape her actions.

When pressed to choose a word for 2019, I choose strength. In doing so, I think about the various projects, teams, and individuals I work with and how we are more effective when we collaborate, learn from, and advocate for one another. I think about advances in terms of inclusion and acceptance and how diversity and civility can strengthen our community. I think about the opportunities we have to improve open source practices, expand them into new areas, and apply them to create solutions to new and existing problems. 

Open source is a powerful catalyst; its strength lies in the bonds formed through open development and shared knowledge which combine to make a stronger and more resilient whole. Let’s carry that strength into 2019 and become stronger together.

Assessing Progress in Automation Technologies

To assess the state of adoption of machine learning (ML) and AI, we recently conducted a survey that garnered more than 11,000 respondents. As I pointed out in previous posts, we learned many companies are still in the early stages of deploying machine learning:

machine learning adoption

Companies cite “lack of data” and “lack of skilled people” as the main factors holding back adoption. In many instances, “lack of data” is literally the state of affairs: companies have yet to collect and store the data needed to train the ML models they desire. The “skills gap” is real and persistent.

Read more at O’Reilly

Tech Ethics New Year’s Resolution: Don’t Build Software You Will Regret

At The New Stack, we talk a lot about avoiding technical debt, but what about the ethical debt? Let’s begin by attempting to define just what ethical technical delivery even is. Black Pepper Software’s Sam Warner at the Good Tech Conf — a conference which focused on technology for social good — simplified this great university philosophy topic, saying ethical software:

  • causes no negative social impact
  • doesn’t make the world worse to live in

At Coed Ethics, another conference dedicated to tech ethics that The New Stack covered earlier this year, Doteveryone’s Sam Brown echoed Warner, saying “Responsible technology considers the social impact it creates and seeks to understand and minimalize its potential unintended consequences.” Doteveryone as an organization is dedicated to supporting responsible technology as a key business driver for positive and inclusive growth, innovation, and trust in technology.

But should those of us building the future’s code feel obligated to contribute something toward social good? Warner argues we should go even further than that and contribute to work that benefits the most amount of people in a significant way.

So, if this is our objective, where do we begin?

Read more at The New Stack

EU Offers Bug Bounties For 14 Open Source Projects

As the bug bounty programs begin to roll out in January, security experts worry that the programs miss the mark on truly securing open source projects.

The European Commission in January is funding 14 bug bounty programs in hopes of sniffing out vulnerabilities in the free open source projects that EU institutions rely on.

The bug bounty programs span 14 open source software projects and offers a total of almost $1 million for all bounties combined.  The bug bounty programs have varying rewards, start and end dates, and platforms. The first bug bounty programs – for Filezilla, Apache Kafka, Notepad++, PuTTy, and VLC Media Player – begin next week on Jan. 7.

The initiative stems back to the Free and Open Source Software Audit project (FOSSA), first created by European Parliament member Julia Reda.

Read more at ThreatPost

 

8 Tips to Help Non-Techies Move to Linux

While bringing them to the Linux side of the computing world, I learned a few things about helping non-techies move to Linux. If someone asks you to help them make the jump to Linux, these eight tips can help you.

1. Be honest about Linux.

Linux is great. It’s not perfect, though. It can be perplexing and sometimes frustrating for new users. It’s best to prepare the person you’re helping with a short pep talk.

What should you talk about? Briefly explain what Linux is and how it differs from other operating systems. Explain what you can and can’t do with it. Let them know some of the pain points they might encounter when using Linux daily.

If you take a bit of time to ease them into Linux and open source, the switch won’t be as jarring.

2. It’s not about you.

It’s easy to fall into what I call the power user fallacy: the idea that everyone uses technology the same way you do. That’s rarely, if ever, the case.

Read more at OpenSource.com

A Tour of elementary OS, Perhaps the Linux World’s Best Hope for the Mainstream

elementary OS began life over a decade ago as a set of icons. (Yes, seriously.) If ever there was a group of developers who started at the bottom and worked their way up to the top, it’s Daniel Foré and the rest of today’s elementary OS team. From a set of icons designed to improve the look of Ubuntu’s then GNOME 2 desktop, the elementary project expanded to include some custom apps, including a fork of the default GNOME files app, Nautilus, called nautilus-elementary. As with most open source projects, the borrowing went both ways: Ubuntu’s Humanity theme was a fork of elementary OS’s icon set.

Over the years, the elementary project continued to grow and encompassed ever more apps and ever more customizations for the desktop. Eventually, things got to the point where it became more and more cumbersome for users to install everything. But there was enough momentum behind the project that Foré decided the logical thing to do was for the group to create their own distribution. The project took Ubuntu as a base and began layering in their custom apps, and the highly refined look and feel of elementary OS was born.

elementary OS 5 Juno

For a bit of logistics, elementary OS Juno should be version .5, following the previous release, .4 or Loki. However, since .5 implies incomplete and elementary OS is more or less complete (in terms of stability certainly) ,the project is calling this release elementary OS 5.

Whatever the version number may be, one thing is for sure: there’s ton of new stuff in Juno. Enough features, in fact, that the release notes, written by elementary OS’s Cassidy James Blaede, are an impressive John Sircusa-style essay of some 8,000 words. If you want to know everything that’s new, Blaede’s notes are worth a read. If you want to know what it’s like to actually use all that stuff, read on.

Read more at Ars Technica