Language Selection

English French German Italian Portuguese Spanish

Devices With GNU/Linux

Filed under
GNU
Linux
Hardware
  • [Older] Wind River Four-Step Procedure to Secure Linux-Based Systems

    The world is increasingly interconnected and a result of this is the exposure to security vulnerabilities has dramatically increased as well. The intricacies of maintaining today's Linux-based platforms make it very challenging for developers to cover every potential entry point. In 2019 there was an average of more than 45 CVEs logged per day. How does a development organization keep up with that? In order to stay on top of this, developers must increasingly spend more time and effort integrating common vulnerabilities and exposure (CVE) patches into their solutions, at the cost of spending time developing their applications

    Security attacks come in many forms and use various entry points. Each attack type comes in several flavors, as there is usually more than one way that they can be configured or camouflaged based on the experience, resources, and determination of the hacker. While some threats are more prevalent than others, a developer needs to protect against all vulnerabilities. The following chart shows the increase in CVEs over the last 6 years, and how many of those CVEs actually impact any given distribution.

  • 4K Digital Signage Player Drives up to 4x 4K Displays with AMD Ryzen Embedded V1000 SoC

    We’ve covered plenty of AMD Ryzen Embedded V1000 SBC‘s, as well as some mini PC‘s, but the processor’s multimedia capabilities make it an ideal candidate for advanced digital signage players capable of driving multiple 4K displays.

    Axiomtek leveraged those capabilities in DSP600-211 4K digital signage player that offers four HDMI ports driving up to four 4K displays, as well as dual Gigabit Ethernet.

  • 3.5-inch Whiskey Lake SBC has mini-PCIe and dual M.2

    Aaeon’s 3.5-inch “GENE-WHU6” SBC runs on an 8th Gen Whiskey Lake CPU with up to 32GB RAM, 4x USB 3.2 Gen 2 ports, 2x GbE, and 2x M.2 slots, starting at under $1K.

    Over the last few days, Aaeon’s 8th Gen Whiskey Lake based PICO-WHU4 Pico-ITX board, which we covered in February, has received a lot of attention from the tech press, with the inevitable comparisons to the Raspberry Pi 4. Although a commercial Intel-based board is a world away from an Arm-based maker board like the Pi in terms of community support and price on the one hand and CPU power on the other, the 100 x 72mm Pico-ITX form factor is as close as the x86 world comes to the compact, 87 x 56mm Raspberry Pi footprint.

  • Five years of Raspberry Pi clusters

More in Tux Machines

today's howtos

Open Usage Commons

  • Introducing the Open Usage Commons

    Open source maintainers don’t often spend time thinking about their project’s trademarks, and with good reason: between code contribution, documentation, crafting the technical direction, and creating a healthy contributor community, there’s plenty to do without spending time considering how your project’s name or logo will be used. But trademarks – whether a name, logo, or badge – are an extension of a project’s decision to be open source. Just as your project’s open source license demonstrates that your codebase is for free and fair use, an open source project trademark policy in keeping with the Open Source Definition gives everyone – upstream contributors and downstream consumers – comfort that they are using your project’s marks in a fair and accurate way.

  • Open Usage Commons Is Google-Backed Organization For Helping With Open-Source Project Trademarks

    Open Usage Commons is a new organization announced today that is backed by Google for helping open-source projects in managing their trademarks. Open Usage Commons was started by Google in conjunction with academia, independent contributors, and others for helping to assert and manage project identities through trademark management and conformance testing.

  • The "Open Usage Commons" launches

    Google has announced the creation of the Open Usage Commons, which is intended to help open-source projects manage their trademarks.

  • Announcing a new kind of open source organization

    Google has deep roots in open source. We're proud of our 20 years of contributions and community collaboration. The scale and tenure of Google’s open source participation has taught us what works well, what doesn’t, and where the corner cases are that challenge projects.

Android Leftovers

GNOME, Linux, Qt and Git Programming

  • Philip Withnall: URI parsing and building in GLib

    Marc-André Lureau has landed GUri support in GLib, and it’ll be available in GLib 2.65.1 (due out in the next few days). GUri is a new API for parsing and building URIs, roughly equivalent to SoupURI already provided by libsoup — but since URIs are so pervasive, and used even if you’re not actually doing HTTP conversations, it makes sense to have a structured representation for them in GLib.

  • Sandboxing in Linux with zero lines of code

    Modern Linux operating systems provide many tools to run code more securely. There are namespaces (the basic building blocks for containers), Linux Security Modules, Integrity Measurement Architecture etc. In this post we will review Linux seccomp and learn how to sandbox any (even a proprietary) application without writing a single line of code.

  • Mario Sanchez Prada: ​Chromium now migrated to the new C++ Mojo types

    At the end of the last year I wrote a long blog post summarizing the main work I was involved with as part of Igalia’s Chromium team. In it I mentioned that a big chunk of my time was spent working on the migration to the new C++ Mojo types across the entire codebase of Chromium, in the context of the Onion Soup 2.0 project. For those of you who don’t know what Mojo is about, there is extensive information about it in Chromium’s documentation, but for the sake of this post, let’s simplify things and say that Mojo is a modern replacement to Chromium’s legacy IPC APIs which enables a better, simpler and more direct way of communication among all of Chromium’s different processes.

  • 6 best practices for teams using Git

    Everyone should follow standard conventions for branch naming, tagging, and coding. Every organization has standards or best practices, and many recommendations are freely available on the internet. What's important is to pick a suitable convention early on and follow it as a team. Also, different team members will have different levels of expertise with Git. You should create and maintain a basic set of instructions for performing common Git operations that follow the project's conventions.

  • Qt for MCUs 1.3 released

    Qt for MCUs 1.3 is now available in the Qt installer. Download it to get the latest improvements and create stunning GUIs with the newly available timeline animation system. Since the initial release of Qt for MCUs 1.0 back in December last year, we've been hard at work to bring new features to MCUs with the 1.1 and 1.2 releases. Efforts haven't slowed down and it's already time to bring you another batch of improvements. Besides the new features, One of the goals has been to make Qt Quick Ultralite a true subset of Qt Quick and align their QML APIs to ensure both code and skills can be reused from traditional Qt platforms to microcontrollers. With Qt for MCUs 1.3, QML code written for Qt Quick Ultralite is now source-compatible with Qt 5.15 LTS.