Webconverger, a Debian-based GNU/Linux operating system whose main design goal is to distribute a fully functional and controlled web kiosk platform, has been updated today to version 35.1.
There are many Linux kernel-based distributions out there that claim to offer a powerful web kiosk system for use in offices or Internet cafes, but Webconverger is among the most popular ones, and it is based on the almighty Debian GNU/Linux operating system.
I'm announcing the release of the 3.14.70 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
and can be browsed at the normal kernel.org git web browser:
Few would claim that the year-old fork and legal dispute between rival Arduino camps is healthy for the open source hardware community. Yet, so far, the platform remains strong, despite growing competition from open source Linux SBCs like the Raspberry Pi. In large part, this is due to the rising interest in Internet of Things (IoT) devices, which dovetails nicely with the low-power, gadget-oriented MCU-based platform.
In this article, I’ll take two different approaches to comparing VM and container security. The first approach will be more structural, or theoretical, looking at the characteristics of each from a security perspective. Then I’ll apply a more practical analysis by looking at what happens in a typical breach and how it might be affected by container and VM architectures.
NXP and Element14 unveiled a tiny “WaRP7” module for wearables and IoT that combines an i.MX7 Solo SoC with WiFi, Bluetooth, BLE, NFC, and MikroBus expansion.
Element14 has partnered with NXP on an update to the original Freescale WaRP board, which ran on the Freescale (now NXP) i.MX6 Solo SoC. The WaRP7 shares the same Wearables Reference Platform (WaRP) branding as the WaRP, and is similarly a sandwich-style COM with I/O daughter card design running Linux and Android.
The last Foss Force interview with Jeff Hoogland was in January, 2015. He had un-project-headed himself from his creation, Bodhi Linux, then decided to return. He’s still there, maintaining his Enlightment-based Ubuntu derivative. Why yet another distro? Hoogland says why quite eloquently during the interview, so there’s no need to repeat his words here. He’ll also explain the Moksha desktop and explain why it is based on E-17 instead of a more recent version. (The Wikipedia link above will teach you about the Enlightment desktop’s tangled path, which is way beyond the scope of this video intro.) Besides Bodhi Linux and being a full-time dad, he is a pro-level Magic the Gathering player, complete with active Twitch and YouTube feeds devoted to the game. A full life indeed! (We should all live so well, eh?)
The Manjaro community is proud to announce the first production-ready version of the Manjaro ARM operating system, a specially crafted Manjaro Linux flavor for ARM devices, such as the popular Raspberry Pi boards.
After having it in development for the past three months, the Manjaro ARM development team led by Dodge JCR has released the Manjaro ARM 16.05 operating system for Raspberry Pi 2 single-board computers, based, of course, on the unofficial Arch Linux for ARM project.
The lightweight and eye-candy Enlightenment desktop environment/window manager received yet another maintenance release for its current stable branch, version 0.20.8.
Enlightenment 0.20.8 arrives one day after the Enlightenment Developer Days 2016 conference for Enlightenment developers and contributors, which took place earlier this week between May 14-16, in Paris, France.
In the opening OSCON keynote this morning, the founder of Docker, Solomon Hykes, gave us a fantastic birds-eye view of lessons learned from the "firehose" while building a successful open source project. He calls this process: Incremental Revolution.
Hykes says, "The world needs the tools for mass innovation, tools that encapsulate the harder parts of technology in order to unlock creativity." Further, the growing Internet of Things (IoT), a programmable Internet, will be the ultimate tool of mass innovation, programming lots of things simultaneously or in parallel, rather than one at a time.
Docker was the flame that catalyzed innovation in application development, according to Scott Johnston, senior vice president of product management and design at Docker. However, that success was entirely unforeseen.
"I wish I could say that we had a premeditated mindset three years ago when we released Docker," Johnston said in his keynote at last month's Collaboration Summit. "But we did not." Looking back, he sees three main reasons for Docker’s success: Accessibility, Portability, and Openness.
Docker Engine 1.11 has been released, built on runC and containerd. "runC is the first implementation of the Open Containers Runtime specification and the default executor bundled with Docker Engine. Thanks to the open specification, future versions of Engine will allow you to specify different executors, thus enabling the ecosystem of alternative execution backends without any changes to Docker itself. By separating out this piece, an ecosystem partner can build their own compliant executor to the specification, and make it available to the user community at any time – without being dependent on the Engine release schedule or wait to be reviewed and merged into the codebase."